Sonicursion privacy notice
Updated November 15, 2026 · Notice version 2026-11-15-v2
This notice explains how personal information is handled when you visit sonicursion.com, join the waitlist, answer our product and pricing questions, or contact us about your information. It covers the website and waitlist as they operate today. It does not describe a future paid account, purchase, or installed-app feature that is not yet part of this service.
In brief: we use your email to manage your requested waitlist updates and your voluntary answers to help decide what to build. Optional visitor analytics is currently off. You can unsubscribe and request access to or deletion of your waitlist information. The operator and privacy contact are identified in Responsible party; you do not need to read the whole notice to contact us.
1. Scope and sources of information
Most waitlist information comes directly from you: the address you enter, the choices you make, and the comments you submit. Our systems also create records of submissions, consent, email confirmation and delivery, requests to manage information, and security checks. Our hosting and email providers return technical results, such as whether a verification succeeded or a message bounced.
Browsing the public site does not require joining the waitlist. Joining is voluntary. An email address and an affirmative request to receive waitlist emails are needed for that subscription; platform, interest and pricing answers are optional. Leaving an optional answer blank does not prevent you from joining. Product and pricing questions are research, not an order, payment authorization, subscription contract or promise of availability.
2. Information we collect
Waitlist and feedback
We store your email address, waitlist status, signup and confirmation times, and a record of the consent statement and its version. When you choose to answer, we also store your preferred platform, what interests you about the project, your reaction to the proposed pricing, and any suggested price or comments about what would make the product worthwhile. These answers can be associated with your signup so we can understand feedback in context.
Separate submissions from the same address can retain separate feedback and consent records. Going back through the form does not itself erase information already submitted. We do not treat a repeated submission as permission to override an existing unsubscribe or suppression record. If an answer needs correction or removal, use the contact and rights options below.
Operational records
The application creates random identifiers for submissions and related actions. It stores confirmation, unsubscribe and privacy-request token hashes; delivery states and provider message identifiers; and records needed to make retries safe and prevent duplicate processing. Messages waiting to be sent contain the information needed for delivery in an encrypted queue. A hashed token is used to verify a link without storing that link's raw secret in the corresponding token record.
For application rate limits, we derive a keyed value from the connecting IP address and the day instead of saving the raw address in the rate-limit record. This is a security measure, not a claim that the resulting record is anonymous. Cloudflare receives connection and browser information while hosting the site and carrying out bot checks. Email providers also receive technical delivery information necessary to send messages.
3. Purposes and lawful bases
We use signup information to operate the waitlist, confirm control of an address, send requested launch and early-access updates, and respect changes to your preferences. We use voluntary product and pricing answers to assess interest and prioritize development. Technical records help deliver messages, diagnose failures, enforce limits, prevent abuse, and carry out access or deletion requests.
Where EU or UK data-protection law applies, our stated bases are:
- Consent: requested waitlist communications and the voluntary feedback you submit for product research. Your email choice is affirmative; the consent box is not preselected.
- Legitimate interests: running and securing the service, preventing fraudulent submissions, delivering requested administrative messages, and maintaining necessary records of opt-outs. Those interests are limited by your rights and reasonable expectations.
- Legal obligations: processing necessary to comply with applicable requirements, including responding to valid rights requests or binding legal demands.
We do not sell waitlist information, create third-party advertising audiences from it, or use the signup as consent to unrelated campaigns. If a proposed future use falls outside the purposes described here, we will assess the appropriate basis and provide the required information or seek a new choice before using data that way. This notice is an explanation of processing, not a blanket permission for any future business use.
4. Email choices and confirmation
Submitting the form records your request to join. A confirmation email helps verify that you control the address. Pending and confirmed subscriptions are recorded separately. Delivery may be blocked by an invalid address, provider failure, spam filtering, a prior opt-out, or our abuse limits. A successful form response is not a guarantee that a message reached your inbox.
Use the unsubscribe link to stop waitlist updates. Withdrawal does not undo processing that was lawful before it, and it does not necessarily delete every administrative record. We retain a limited suppression record to avoid sending further unwanted mail. A delivery complaint or permanent bounce may also cause suppression. We do not automatically lift that protection just because the same address is submitted again.
5. Analytics, browser storage and external links
Optional first-party usage analytics and PostHog are disabled. We do not run session replay. A visit therefore does not currently create an application analytics record of page views, button clicks or form abandonment. This does not affect the saving of a form you intentionally submit, nor the hosting provider's operational request counts and security records.
We do not upload unfinished email addresses or written feedback as an abandonment-analysis feature. The form may retain values in the current page while you move backward and forward. Necessary storage or preferences may also support the interface. Keeping an answer visible in your browser is different from submitting it to our server; once you submit, the waitlist retention and rights provisions apply.
If optional analytics is enabled later, we will update this notice and request opt-in before collecting optional usage events. The existing design separates email consent from analytics consent and is intended to measure limited events rather than written answers. That description of a possible future feature does not mean it is collecting now or that your present email consent activates it.
Administrative access uses authentication and session mechanisms to protect the private management interface; ordinary visitors do not receive an administrator session. Links to social networks or other sites take you to separately operated services. Their privacy terms apply after you follow those links. A link does not give those services permission through us to receive your waitlist answers.
6. Service providers and disclosures
Cloudflare provides website hosting and delivery, the waitlist database, media storage, bot protection through Turnstile, and protection for administrative access. Requests necessarily pass through its network. Turnstile can process IP address, browser and connection signals to distinguish automated abuse from legitimate use. Cloudflare describes additional processing for its bot-detection service in its Turnstile Privacy Addendum.
Resend delivers confirmation and privacy-management emails. It receives the recipient address and message content needed to send them, and processes delivery, bounce and complaint information. We use those results to retry delivery when appropriate, stop unwanted mail, and handle requests. Provider account, security or legal records may be processed under the provider's own terms as well as its role in delivering our service.
Authorized administration can access submitted waitlist information to operate the project and review feedback. We do not make submissions a public directory. We may disclose relevant information where a binding legal requirement applies or where necessary to establish or defend legal claims, subject to applicable law. A future business transfer is addressed separately below; it is not an unrestricted sale of the list.
7. International processing
The waitlist database is hosted in the United States. Cloudflare operates a global delivery network, and Resend states that customer data is stored in the United States. Information may therefore be processed outside the country where you live, including in countries whose privacy protections differ from those in your jurisdiction.
The applicable provider agreements describe mechanisms for restricted international transfers, including European Commission standard contractual clauses and UK transfer provisions where relevant. You can contact us for information about the safeguards applicable to our processing and how to obtain a copy, subject to appropriate redaction of confidential material. See Cloudflare’s data-processing terms and Resend’s data-processing terms. Provider terms alone are not a promise that every transfer risk is eliminated.
8. Retention and deletion
Retention depends on the record's purpose. The configured application cleanup periods are:
- Unconfirmed memberships: 30 days from creation, with linked records removed through scheduled cleanup.
- Submitted platform, interest and pricing answers: 365 days from the submission. Feedback is removed and relevant answer fields are cleared; technical submission and consent records can remain.
- Optional analytics events: no collection at present. The configured cleanup period is 30 days if later enabled with notice and opt-in.
- Completed, failed or cancelled mail queue records, webhook receipts and application admin-audit records: cleanup after 30 days. Expiring action tokens, rate-limit records and admin sessions are cleaned up separately.
- Confirmed or unsubscribed membership and consent evidence: retained as needed to operate the list, demonstrate choices and respect opt-outs; reviewed at least annually and when the waitlist closes.
- Suppression records: a minimal keyed email hash can remain after deletion to prevent unwanted contact. Its continued need is reviewed annually and while the opt-out must be respected.
Cleanup is periodic and processed in batches, so reaching a retention date does not mean every copy disappears at that exact instant. A justified legal obligation, dispute or security investigation can require limited records to be kept longer, with use restricted to that purpose. A general possibility of future business value is not a reason to keep all answers indefinitely.
Providers manage their own recovery and operational systems. Resend publishes 30-day email/log retention for its standard plans; its account-deletion and backup schedules are separate. Cloudflare D1 Free provides recovery history of up to seven days. A request to delete an application record does not instantly erase provider backups. We handle provider-side requests where applicable and respect deletion and suppression choices if data is restored.
9. Security and automated processing
Our application uses authenticated administrative access, restricted management routes, request validation and rate limits. Delivery payloads are encrypted while queued, and action tokens are checked using stored hashes. These measures reduce risk; no website, email system or storage arrangement can guarantee absolute security. Contact us if you believe your information or an access link has been exposed.
Automated checks can reject suspicious requests, delay repeated attempts or suppress an address after a delivery complaint. They protect the service and do not make employment, credit or similarly significant decisions about you. We do not use the waitlist to produce automated eligibility scores or advertising profiles. If a security check prevents a legitimate request, the privacy contact remains available.
10. Responsible party
Sonicursion is operated by James Thornton, who is responsible for the personal information described in this notice and acts as the controller where that term applies. “We,” “us” and “our” refer to this operation, not to an unspecified corporate group.
For privacy questions, requests, corrections or concerns, email admin@sonicursion.com. Please identify the service and the action you need help with, and use the address associated with your signup when possible. You can also start an email-verified request through Email & data preferences. You do not need a paid account or an active subscription to make a privacy request.
11. Your rights and how to use them
Depending on the law that applies, you may request access to personal information, correction of inaccuracies, deletion, restriction of particular processing, or a portable copy of information you provided. You may withdraw consent and may object to processing based on legitimate interests, including direct marketing. These rights have conditions and exceptions; they do not require us to disclose another person's information or ignore an applicable retention obligation.
The email-verified management flow provides access, export and deletion options for waitlist records associated with your address. Contact us for correction, restriction, an objection, or a request the automated flow cannot resolve. The available self-service options do not limit your statutory rights. If you only want to stop updates, unsubscribe; if you want records removed as well, request deletion.
To protect your information, we may ask for proportionate evidence that you control the relevant address or are authorized to act for the person concerned. We do not routinely need a government ID for a waitlist request. If an email link cannot establish ownership, explain the issue so we can consider an appropriate alternative. Never send your account password.
We respond within the applicable legal time limit. Under the GDPR, requests are generally addressed within one month; a permitted extension for complexity or multiple requests may add up to two months, with notice and reasons. Other jurisdictions can have different deadlines. Requests are ordinarily free; any lawful refusal, limitation or permitted fee will be explained, together with available complaint or review routes.
Deletion may remove feedback while leaving limited suppression or consent evidence where justified. Unsubscribing does not require erasing the evidence that you opted out. Withdrawing consent does not invalidate earlier lawful processing, and we will not silently substitute withdrawn marketing consent with another basis simply to keep sending the same updates.
12. Regional rights and complaints
People in the EEA or UK can raise concerns with the relevant data-protection authority, including an authority where they live or work or where an alleged infringement occurred. See the EEA supervisory authorities and the UK Information Commissioner's Office. Contacting us first may help resolve a problem but is not a prerequisite to a regulatory complaint.
Residents of other countries or US states may have additional rights where their laws apply to this service, such as requesting information about disclosures, authorizing another person to make a request, or appealing a denied request. Contact the privacy address and identify the request; we will assess it under the applicable requirements. This notice does not assert that every regional privacy statute applies to this small project merely because the website is accessible internationally.
We do not sell personal information or share it for cross-context behavioral advertising. We do not charge for access to a privacy request mechanism or make a request conditional on joining the waitlist. If you disagree with our handling of a request, reply asking for a review and explain the concern; this does not displace any independent regulator or court remedy available to you.
13. Children and sensitive information
The waitlist is for people able to provide their own valid consent under applicable law. It is not designed to collect children's profiles or sensitive information. We do not ask for a date of birth, health details, religious or political beliefs, financial account details, or identity documents in the signup form.
If you believe a child has submitted information without the authorization required by law, contact us so we can assess and remove it where appropriate. Please do not provide additional sensitive details to establish the concern unless they are necessary and specifically requested. Free-text fields are for product feedback, not private records about you or other people.
14. Business changes and future uses
If the project is incorporated, transferred to a company or sold, relevant information may transfer to the new operator so it can continue Sonicursion and administer the waitlist. Due diligence, if needed, should be limited to information relevant to the transaction and subject to appropriate confidentiality and legal safeguards.
A business transfer does not cancel your preferences, expand the purposes of your consent or permit unrelated marketing. We will communicate a new operator's identity and material changes as required. Further consent or another valid basis may be necessary for new uses. Any future account, payment or installed-app processing will need an appropriate explanation when it is introduced rather than relying on this waitlist notice alone.
15. Changes to this notice
We will update the date and version when this notice changes. Material changes will receive additional notice or a fresh consent request where required, before the relevant new processing begins. A wording update does not by itself change the consent you previously gave. You can contact us for information about the version associated with your signup.