Cookies are small text files that a website places on your computer, phone, or other device when you visit it. Your browser stores these files and sends them back to the originating website on subsequent visits, allowing the site to recognise your device and recall certain information about your previous interactions — for example, that you have already seen the cookie consent banner, or that your browser session is in progress.
Cookies are not executable programs. They cannot carry viruses, install software, or perform any action beyond storing a limited amount of text data. At their core, they are key-value pairs that give stateful behaviour to what would otherwise be a stateless HTTP environment.
In addition to cookies, websites may use related technologies such as web beacons, pixel tags, and browser local storage. Where we use any of these technologies alongside cookies, this policy covers them too. For simplicity, all such mechanisms are referred to collectively as "cookies" throughout this document, unless a distinction is relevant.
The use of cookies by websites operating within the European Union is governed by the ePrivacy Directive (2002/58/EC, as amended) and the General Data Protection Regulation (GDPR — Regulation (EU) 2016/679), both implemented in Dutch law. Where cookies involve processing of personal data, the GDPR applies in full. This Cookie Policy is written to satisfy our disclosure obligations under both instruments and should be read alongside our Privacy Policy, which covers all personal data processing in broader detail.
ERC20Token.app uses cookies for a narrow, well-defined set of purposes directly related to the operation of our service. We do not use cookies to build advertising profiles, to track you across third-party websites, or to sell data to data brokers. Our cookie use falls into three categories: keeping the token deployment workflow functional, measuring how visitors use the site in aggregate, and remembering your cookie consent preference so that we do not ask you to choose again on every visit.
Where cookies involve the processing of personal data — specifically analytics cookies that can be correlated with an IP address or browser fingerprint — we seek your prior consent before setting them, in accordance with Article 6(1)(a) GDPR. Strictly necessary cookies do not require consent because they are essential to deliver the service you have explicitly requested; the legal basis for those is Article 6(1)(b) (performance of a contract) or Article 6(1)(f) (our legitimate interest in maintaining a functioning, secure platform).
When you use our platform to create erc20 token contracts on the Ethereum Mainnet, the PHPSESSID session cookie is indispensable: it maintains the state of your submission across the multi-step deployment workflow. Without it, data you enter on one step cannot be carried forward to the next, and the service cannot function.
Analytics cookies help us answer practical questions: which token configuration options are most frequently selected, on what device types people typically access the creator form, and whether changes we make to the interface improve or worsen the user experience. We review analytics data in aggregated form only; we do not examine individual user journeys.
The table below lists every cookie that ERC20Token.app sets or allows to be set on your device, including cookies placed by third-party services integrated into our platform. If you observe a cookie on our site that does not appear in this table, please contact us using the details in Section 8 so we can investigate and update our disclosure if necessary.
| Cookie Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
| PHPSESSID | ERC20Token.app | Standard PHP session identifier. Maintains the server-side session that tracks your progress through the token creation form, preserves temporary form state between steps, and associates your browser with any session data stored on our server during your visit. Without this cookie the deployment workflow cannot function. | Session (deleted when the browser tab is closed or after 24 hours of inactivity at the latest) | Strictly Necessary |
| cc_cookie_accept | ERC20Token.app | Records your cookie consent preference — whether you have accepted or declined optional (analytics) cookies via the consent banner displayed on your first visit. Prevents the consent banner from reappearing on subsequent visits until your preference expires or you explicitly withdraw consent. | 1 year | Preference |
| _ga | Google LLC (Google Analytics) | Primary Google Analytics tracking cookie. Contains a randomly generated client identifier (in the form GA1.1.xxxxxxxxxx.xxxxxxxxxx) that distinguishes unique visitors and browser sessions. Used to calculate visitor counts, session durations, and campaign attribution data for our analytics reports. IP anonymisation is enabled on our Google Analytics property. | 2 years | Analytics |
| _ga_XXXXXXXX | Google LLC (Google Analytics) | Google Analytics 4 container-specific cookie. Stores and updates a unique value for each page visit and is used to maintain session state within a single GA4 measurement property. The "XXXXXXXX" portion of the name corresponds to the GA4 measurement ID configured on this website. Works in conjunction with _ga to provide session-level analytics signals. | 1 day | Analytics |
| _gid | Google LLC (Google Analytics) | Distinguishes users within a 24-hour window for Google Analytics reporting. Stores and updates a unique value for each page visit, enabling the service to differentiate individual visits made on the same day. Complements the longer-lived _ga cookie by providing a shorter-horizon session signal, used primarily for daily unique-visitor calculations. | 24 hours | Analytics |
Cookie durations listed above reflect the maximum lifetime of each cookie as set. Session cookies are removed by your browser automatically when your browsing session ends. Persistent cookies remain on your device until their expiry date or until you delete them manually. Clearing your browser's cookie store will remove all cookies irrespective of their scheduled expiry.
A first-party cookie is set by the website you are actively visiting — in this case, ERC20Token.app. A third-party cookie is set by a different domain, typically a service embedded in or called by our site. Third-party cookies are governed by the privacy policies of the organisations that set them, not by this policy.
The only third-party cookies currently set on ERC20Token.app are those placed by Google Analytics, a web analytics service operated by Google LLC (1600 Amphitheatre Parkway, Mountain View, CA 94043, USA). These cookies — _ga, _ga_XXXXXXXX, and _gid — are described in full in the table in Section 3 above.
Google Analytics may transfer data to servers in the United States. ERC20Token.app has enabled IP anonymisation in our Analytics configuration, meaning your IP address is truncated before being stored or processed by Google. Google LLC participates in the EU-US Data Privacy Framework, which provides an adequacy basis for such international transfers under GDPR Article 45. For full information on how Google handles Analytics data, refer to Google's privacy policy at policies.google.com/privacy.
We do not embed social-media widgets, third-party advertising scripts, or any other external content that would result in additional third-party cookies being set without your knowledge. If we integrate further third-party services in the future that introduce new cookies, we will update this policy and the table in Section 3 before those cookies are set.
For a full account of all third-party service integrations — including those that do not involve cookies but do involve data transmission, such as our Ethereum node provider and Etherscan — please refer to our Privacy Policy.
You have several practical options for controlling which cookies are placed on your device. The right method depends on how much granularity you need.
Browser-level cookie controls
Every major browser lets you view, delete, and block cookies through its settings interface. Blocking all cookies will cause many websites — including parts of ERC20Token.app — to stop working correctly (see Section 6 for details). Blocking only third-party cookies, a setting available in most browsers, will prevent analytics cookies from being set while leaving the core service intact. Step-by-step guidance for the most common browsers:
- Google ChromeSettings → Privacy and security → Third-party cookies, or navigate directly to
chrome://settings/cookies - Mozilla FirefoxSettings → Privacy & Security → Cookies and Site Data. Firefox's Enhanced Tracking Protection set to "Strict" blocks most analytics cookies by default without any additional configuration.
- Apple SafariPreferences (or Settings) → Privacy → Manage Website Data. Safari blocks cross-site tracking cookies by default on all platforms.
- Microsoft EdgeSettings → Cookies and site permissions → Cookies and site data
- OperaSettings → Privacy & security → Cookies
For a comprehensive, browser-neutral guide to managing cookies across all platforms, visit allaboutcookies.org.
Opting out of Google Analytics specifically
If you want to prevent Google Analytics from collecting data about your visits across all websites that use it — not just ERC20Token.app — Google provides a dedicated browser add-on for this purpose:
- Google Analytics Opt-out Browser Add-onavailable at tools.google.com/dlpage/gaoptout. Once installed, it instructs the Google Analytics JavaScript library not to send visit information to Google, regardless of which website you are viewing.
Alternatively, browser extensions such as uBlock Origin or Privacy Badger block analytics tracking scripts from loading entirely, which prevents Google Analytics from running on any page where those extensions are active.
Withdrawing consent via our consent banner
If you previously accepted analytics cookies via our consent banner and wish to withdraw that acceptance, delete the cc_cookie_accept cookie from your browser's cookie store for the ERC20Token.app domain, then reload the page. The consent banner will reappear and allow you to revise your preference. Withdrawing consent does not affect the lawfulness of any analytics processing that took place before withdrawal.
The PHPSESSID cookie is classified as strictly necessary because the ERC20 token deployment service cannot function without it. When you create an erc20 token using our platform, the process spans multiple steps: entering token parameters, connecting your wallet, confirming the fee transaction, and receiving deployment confirmation along with the Etherscan verification link. The PHP session cookie is the mechanism that keeps these steps coherent on the server side between each HTTP request.
Without PHPSESSID, every request your browser sends to our server would be treated as a completely new, unrelated interaction. The server would have no way to know that the wallet address confirmed in step two belongs to the same user who entered the token name and symbol in step one. The entire workflow would immediately break down. Disabling session cookies in your browser will therefore prevent you from using the token creation form.
The ePrivacy Directive — and its implementation in Dutch law — explicitly exempts strictly necessary cookies from the prior consent requirement. We do not display a consent request before setting PHPSESSID, nor are we legally required to. You cannot opt out of this cookie while continuing to use our service.
The cc_cookie_accept preference cookie is also set without prior consent. This is technically necessary because a cookie that can only be placed after a consent interaction has been completed would be circular and non-functional — the banner would reappear on every page load regardless of your choice. The cookie stores only a single Boolean preference value; it contains no personally identifiable information beyond that binary choice.
No other cookies are set without your consent. Analytics cookies are activated only if you accept them via the consent banner, or if you have previously done so and your cc_cookie_accept cookie reflects that prior acceptance. If you land on the site with the cc_cookie_accept cookie absent or set to a declined value, no analytics scripts will load.
We may revise this Cookie Policy from time to time. Reasons for an update might include the introduction of a new third-party service that places cookies, a change to the duration or stated purpose of an existing cookie, an amendment to applicable EU or Dutch law, or a change in the architecture of our service that alters how session state is managed.
When changes are made, we will update the "Last updated" date at the top of this page. If a change is material — for example, if we were to introduce a new category of analytics or advertising cookie — we will reset the consent banner so that all visitors are presented with the updated choice before any new non-essential cookies are set.
We encourage you to review this page periodically. For information about how your personal data is handled more broadly, including any updates to that processing, refer to our Privacy Policy. For the contractual terms governing your use of the platform, see our Terms of Service.
Your continued use of ERC20Token.app for creating erc20 token contracts on Ethereum after an updated policy has been published constitutes acceptance of any changes relating to strictly necessary or preference cookies. Where changes affect non-essential cookies, we will obtain fresh consent before setting them.
If you have questions about this Cookie Policy, want to understand more about a specific cookie we set, or wish to exercise any right under the GDPR in connection with data processed through cookies, please contact us using the details below. We aim to respond to all enquiries within 5 business days.
- Company name:ERC20Token.app
- Registered address:Singelpassage 9, 9401 JB Assen, Drenthe, Netherlands
- Telephone:0592 331 011
When contacting us about a cookie-related data subject request, please include the name of the cookie in question and, where relevant, the approximate date and time of your visit, so we can locate the correct records and respond accurately.
If you believe we are not handling cookie-related data in compliance with applicable law, you have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens), Hoge Nieuwstraat 8, 2514 EL The Hague, Netherlands (autoriteitpersoonsgegevens.nl), or with the supervisory authority in your country of residence within the EEA.