1. Controller and contact
The controller for the processing described in this notice is:
RoxArt, Switzerland
For normal contact, privacy questions or requests to access, correct or delete personal data, use the contact form and choose “Privacy & data rights”. We do not publish a direct email address on this website.
2. Normal website access, hosting and security
When you open the site, technical data is necessarily processed to deliver pages and keep the service secure. This can include IP address, date and time, requested URL, response status, referring page, browser, device and operating-system information, and security or abuse signals.
The site is delivered using OpenAI Sites infrastructure and Cloudflare hosting and content-delivery services. Those providers may process requests, network identifiers, diagnostic information and security logs to host, route, protect and operate the site. We use these records for availability, fault diagnosis, security, rate limiting and abuse prevention - not to build advertising profiles.
Necessary technologies may include first-party storage for privacy choices and short-lived security controls. Our consent preference stores only the selected category choice, consent version, and minimal save and expiry timestamps. It expires after 180 days, or sooner if you clear browser storage. A material consent-version change prompts you again.
If you choose a partner referral link, a first-party cookie with a random referral reference and a non-identifying active marker lasts up to 30 days. We record the partner, landing section, first and most recent touch, optional campaign labels, and interactions such as page views, story or giveaway submissions and buy-route clicks. The referral record links submissions or giveaway entries to the partner for private reporting. No partner receives your story, entry or wallet identity through this system. We do not fingerprint referral visitors. A separate one-way hash of the request IP and hour limits automated referral-link traffic; it expires within two hours and is never linked to a visitor record. Referral records and events can remain in the private campaign history after the cookie expires. Clearing cookies stops future attribution on that browser; contact us to request removal of applicable records.
3. Google Analytics 4
We use Google Analytics 4 (“GA4”), provided by Google, to understand how visitors use and interact with the production website - for example page and session activity, approximate location, referring source, browser, device, operating system and other technical or interaction data. GA4 may use analytics identifiers and first-party cookies or similar browser storage, including the _ga client identifier.
Analytics is optional and off by default. No GA4 script is initialized and no Analytics request is sent unless you affirmatively permit Analytics in the consent interface. Advertising consent remains denied. We measure visits to public pages and these launch interactions: trading-link clicks, successful contract copying, starting and successfully submitting a story, outbound Telegram, Instagram and X clicks, and referral interaction event names. Partner codes and referral identifiers are not sent to GA4. Event fields use fixed page names and button placements. We do not send contact-form contents, names, email addresses, story text, uploaded images, wallet addresses or submission references to Analytics. Private Studio pages are excluded, and our page events omit URL query strings and fragments. Our integration disables Google Signals and advertising personalisation. No advertising consent is requested.
Google Analytics data is retained according to our Analytics property settings. Aggregated reporting may persist beyond the retention period for individual user and event data. You can contact us for details about the current retention settings. Google processes Analytics data under its applicable terms and may process data internationally, including in countries whose data-protection rules differ from those in Switzerland, the EU/EEA or the UK.
You may refuse Analytics on the first banner or withdraw it at any time through . Withdrawal stops future Analytics collection on this site; it does not retroactively erase data already processed. You may also request assistance through contact. Read more in Google’s data-collection description, retention information and Privacy Policy.
4. Form security and Google reCAPTCHA
The contact, story and community-giveback entry forms use Google reCAPTCHA v3, together with hidden spam fields and request limits, to prevent automated abuse. reCAPTCHA loads only when you try to send a protected form; it is necessary for that requested form submission and is separate from optional Google Analytics.
When reCAPTCHA runs, Google may receive the reCAPTCHA token, IP address, browser and device information, referring page, interaction and security signals, and may set or read technologies required for the service. The server sends the short-lived token to Google for verification and checks the returned score, action, timestamp and hostname. Tokens expire quickly and are intended for one use. Google processes this information under its Privacy Policy and Terms.
5. Contact form and privacy requests
The contact form processes request type, name, email address, subject, message, the privacy-notice acknowledgement, security data and a non-sensitive reference ID. We use this information to receive, route, answer and document your request; to exercise or defend legal rights where necessary; and to prevent abuse. The acknowledgement checkbox records that this notice was provided. It is not relied on as optional marketing consent.
Contact content is delivered server-side through our transactional email provider, Resend. The private destination address, routing and provider credentials are not sent to your browser. We keep contact requests separate from story submissions. Anti-abuse records contain only limited pseudonymous fingerprints, message hashes, status and timestamps - not the message body.
Depending on the request, processing may be necessary to take steps at your request, to communicate with you, to comply with legal obligations, or for legitimate interests such as operating the project, responding to enquiries and protecting the site.
6. Story submissions and images
If you use the story inbox, we process the story, selected category, optional nickname, optional uploaded image, optional public Solana wallet address, permission version, submission reference, timestamps and limited anti-abuse data. The wallet address is stored with your submission ID and any later Story Wall version for possible future community airdrop planning; providing it does not guarantee an airdrop. It is visible to authorised operators in the private Studio and is not shown on the public Story Wall. Do not include real names, private details, passwords, wallet seed phrases or other secrets.
Submissions are stored separately from contact requests and are visible only through the private CTRLZ Studio and restricted operational systems. Stories are not automatically published. Submission also does not automatically trigger image, video or other media generation.
A queued workflow may perform automated text-only triage of a story to classify it, assess creative fit and prepare a review summary or storyboard proposal. The original and any output remain subject to private human review. Selection, adaptation, media generation and publication are separate operator decisions. Uploaded images are stored for private review but are not sent into the automatic text-only triage step.
We process the submitted material to review and administer the story inbox and, where you granted the stated permission, to consider and create adaptations. The form records the exact permission version shown when you submit. Submission does not guarantee selection, payment or publication.
8. Retention
- Consent preferences remain on your device for up to 180 days unless cleared earlier or replaced by a new version.
- Contact-form anti-abuse and duplicate-suppression records are designed to expire after 24 hours. Contact emails are normally retained for up to 12 months after the matter is closed, and longer only where reasonably needed for an ongoing request, legal obligation or claim.
- Security, hosting and diagnostic logs are retained according to operational need and the relevant provider settings, then deleted or aggregated.
- Story submissions and uploaded images are retained while they remain relevant for private editorial review, permission records and any approved adaptation, and are periodically reviewed for deletion or anonymisation when no longer needed.
- GA4 user- and event-level data follows the retention settings of our Analytics property; aggregated reporting may persist beyond that period.
Specific legal, security, backup or dispute requirements may justify a different period. We avoid keeping personal data merely because it might be useful someday.
9. Your choices and rights
Depending on the law that applies to you, you may have rights to request access, correction, deletion, restriction, objection, portability or information about processing; to withdraw consent for future optional processing; and to complain to a competent data-protection authority. These rights can be subject to legal limits and identity verification.
To exercise a right, use the contact form and choose “Privacy & data rights”. Give enough information to identify the relevant interaction, but do not send unnecessary identity documents or secrets. Analytics consent can be withdrawn immediately through as easily as it was granted.
10. Jupiter swap and external trading
The Jupiter Plugin loads only if you open the embedded swap. Jupiter and your connected wallet handle the swap; we do not receive your seed phrase or private key. When you open Jupiter or StonkFun, those services receive your request and apply their privacy practices. The CTRLZ site records outbound buy-link interactions for referred visitors, but does not claim to verify or profile completed wallet transactions.
11. External social links
The website uses ordinary outbound links to Instagram, X and Telegram. It does not embed social feeds, platform SDKs, tracking pixels or third-party social widgets. When you follow an external link, that provider receives your request and applies its own terms and privacy practices. Links open in a new tab with security protections and reduced referrer information where practical.
12. Children and minors
CTRLZ is not designed to collect personal data from young children. Minors should not submit stories, images, contact details or information about other people without appropriate guidance and, where required, permission from a parent or guardian. If you believe a child provided personal data inappropriately, use the contact form.
13. Changes to this notice
We may update this notice when the website, providers or legal requirements change. The version and date above identify the current text. A material change to optional purposes also causes the consent interface to ask again.