neu.seq

Privacy Policy

Last updated: 23 September 2026

neu.seq ("we", "us", "our") operates the website neuseq.com and the application neu.daw at daw.neuseq.com (collectively, the "Service"). This Privacy Policy explains how we collect, use, and protect your personal data.

1. Data Controller

The data controller responsible for your personal data is:

Tim Petri
Switzerland
Email: info@neuseq.com

2. Data We Collect

Account Information

When you sign in using Google OAuth through our authentication provider Clerk, we collect the following information from your Google account:

  • Name
  • Email address
  • Profile picture

Project Data

When you use the application, you may create and store the following data:

  • Audio files you upload or record
  • MIDI data you create
  • Project settings and track configurations

Usage Data

If you accept the Analytics category in our cookie banner, we measure how the site and the application are used with Umami, a cookieless analytics service. Umami records a pageview each time you open a page -- the page visited, the referrer, and coarse browser, device, and country information derived from your request. The page address is masked before it is sent, so a project page is recorded as a masked route rather than the page address -- /project/* for a project and /s/* for a shared link -- and no project or share identifier reaches Umami. Your request also carries your IP address, which Umami uses to derive the country and to count unique visitors; the analytics pipeline keeps no record of it, though our server logs record it separately as described under Technical Data below. Umami sets no cookies and builds no cross-site profile of you.

The application additionally sends a named event when you use a feature -- for example creating, loading, or saving a project, importing a file, exporting a mixdown, adding, duplicating, or merging a track, splitting a clip, starting an AI generation, separating stems, or creating a share link. Some of these events carry a short value describing the choice you made, such as the AI provider or stem separation model used, the export format, or whether an imported file was audio or MIDI, or a count of the items the action involved, such as how many tracks and notes a merge covered.

The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time through "Manage cookies" in the footer, which stops further collection.

Error Reports

If you accept the Analytics category, the application also sends automatic error reports to Better Stack when something crashes or fails. A report is rebuilt from a fixed allowlist before it is sent and contains:

  • The error message and the stack trace from our own code
  • Which screen you were on -- the address is reduced to a known page name, with any identifiers, query string, and fragment removed
  • Your browser and operating system version
  • Identifiers of the project or track involved, so the report can be acted on
  • Technical context naming which part of the application failed -- such as the module, component, or action involved -- together with the build version and environment of the application

The legal basis is your consent (Art. 6(1)(a) GDPR); withdrawing it stops automatic reports from the application immediately. Two paths do not depend on that choice. Errors raised by our own API servers are recorded by Better Stack whatever you chose in the banner. And you can send a single report by hand from the diagnostics window -- pressing that button is your consent for that one report. Any note you write is sent exactly as you type it, so please do not put personal data in it.

Technical Data

Our servers automatically collect certain technical information, including:

  • Browser type and version
  • Operating system
  • IP address (via server logs, and in requests reaching the third-party services listed in section 5)

3. How We Use Your Data

We use your personal data for the following purposes:

  • To provide and maintain the Service
  • To authenticate your identity and manage your account
  • To sync your projects across devices via cloud storage
  • To generate AI music based on your inputs and prompts
  • To improve and develop the Service
  • To measure how the Service is used, where you have consented to analytics
  • To detect, diagnose, and fix faults, where you have consented to automatic error reports

4. Data Storage and Security

Local Storage

Your project data is stored locally in your browser using IndexedDB. This allows you to access your projects offline without relying on a network connection.

Cloud Storage

When cloud sync is enabled, your project data is also stored on Cloudflare Workers infrastructure. This enables project synchronization across devices and keeps a copy in the cloud for sync.

Security Measures

We implement appropriate technical measures to protect your data, including:

  • HTTPS encryption for all data in transit
  • Secure authentication via Clerk
  • Access controls on cloud-stored data

5. Third-Party Services

We use the following third-party services that may process your data:

Clerk (clerk.com)

Our authentication provider. Clerk processes your Google OAuth data (name, email, profile picture) to manage sign-in and account sessions. See Clerk's Privacy Policy.

Cloudflare Workers (cloudflare.com)

Our application hosting and data storage provider. Cloudflare processes requests to our service and may collect technical data such as IP addresses. See Cloudflare's Privacy Policy.

AI Music Providers (Suno, Stability AI, Udio)

When you use AI music generation features, your text prompts and, where applicable, audio data are sent to these third-party AI providers for processing. Each provider has its own data handling practices. See their respective privacy policies:

  • Suno Privacy Policy
  • Stability AI Privacy Policy
  • Udio Privacy Policy

Umami (umami.is)

Our analytics provider, loaded only after you accept the Analytics category. Umami is cookieless and builds no cross-site profile of you, but it receives the page addresses, feature events, and IP address described in section 2. See Umami's Privacy Policy.

Better Stack (betterstack.com)

Our error tracking and logging provider. Better Stack receives the error reports described in section 2: automatic reports from the application after you accept the Analytics category, a report you send by hand, and errors raised by our own API servers regardless of your banner choice. See Better Stack's Privacy Policy.

Google Fonts

We use Google Fonts for font loading. Google may collect technical data such as your IP address when fonts are requested. See Google's Privacy Policy.

6. International Data Transfers

Your data may be transferred to and processed in countries outside Switzerland and the European Economic Area (EEA), particularly the United States, through our third-party service providers. These transfers are protected by appropriate safeguards, including Standard Contractual Clauses approved by the European Commission.

7. Cookies and Local Storage

We use minimal cookies that are required for authentication, managed by Clerk. These cookies are essential for the service to function and cannot be disabled.

We also use browser localStorage and IndexedDB for storing your application preferences and project data locally on your device. This data does not leave your browser unless cloud sync is enabled.

We do not use tracking cookies or third-party advertising cookies, and we do not track you across other websites. Our analytics provider Umami is cookieless, and your choice in the cookie banner is itself stored in an essential cookie, neudaw_consent, so that we can honor it. It holds only your consent categories and is kept for six months. You can change that choice at any time through "Manage cookies" in the footer.

8. Your Rights Under GDPR

If you are located in the European Union or Switzerland, you have the following rights regarding your personal data:

  • Right to access -- You can request a copy of the personal data we hold about you.
  • Right to rectification -- You can request correction of any inaccurate personal data.
  • Right to erasure -- You can request deletion of your personal data ("right to be forgotten"). If you are signed in, you can erase your data yourself with "Erase my data…" in the account menu. Your sign-in identity, held by Clerk, is deleted on request to info@neuseq.com.
  • Right to restriction of processing -- You can request that we limit how we use your data.
  • Right to data portability -- You can request your data in a structured, commonly used format.
  • Right to object -- You can object to certain types of data processing.
  • Right to withdraw consent -- Where processing is based on consent, you can withdraw it at any time.
  • Right to lodge a complaint -- You have the right to lodge a complaint with a supervisory authority, such as the Swiss Federal Data Protection and Information Commissioner (FDPIC).

To exercise any of these rights, please contact us at info@neuseq.com.

9. Data Retention

We retain your data as follows:

  • Account data: Your name, email address and profile picture are held by Clerk for as long as your account exists. They are deleted when you ask us to delete your account by email.
  • Project data: Retained until you delete it. Deleting a project removes its cloud copy -- its files, name, content and cached responses. What remains is a deletion record holding only the project identifier, your account identifier and the deletion time, kept so that an out-of-date device cannot re-create the project, plus internal bookkeeping records (identifiers, storage states and timestamps, with no names or content).
  • Erase my data: Removes your cloud projects and their files, your shared links, temporary uploads, connected-service tokens, and everything the device you use keeps for your account. Once started, the cloud part finishes even if you close the app. What remains is an erasure record (your account identifier, timestamps and the status of each storage system) and the project deletion records described above.
  • Other devices: Copies stored locally on your other devices stay there until you erase your data on that device or clear its browser data.
  • Analytics data: Held in our Umami account for as long as we operate the site. We do not currently apply a fixed deletion schedule to it.
  • Error reports: Held by Better Stack for no longer than 90 days, and no longer than is needed for the purposes above.
  • Backup copies: Deleted database records can persist in our database's point-in-time recovery history for up to 30 days. Stored files and connected-service tokens have no backup copies, so their deletion is final. A deleted token can remain readable for a short time while the deletion propagates.

10. Children's Privacy

Our Service is not intended for use by children under the age of 16. We do not knowingly collect personal data from children under 16. If we become aware that we have collected personal data from a child under 16, we will take steps to delete that data promptly.

11. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or for legal, operational, or regulatory reasons. When we make changes, we will update the "Last updated" date at the top of this page. We encourage you to review this policy periodically.

12. Contact

If you have any questions about this Privacy Policy or our data practices, please contact us:

Tim Petri
Switzerland
Email: info@neuseq.com

neu.seq
Privacy Policy Terms of Service Imprint Contact

© 2026 neu.seq

We use cookies to analyze traffic and improve your experience. You can choose which cookies to allow.

Cookie Preferences

Choose which cookies you want to allow. Essential cookies are always active as they are needed for the website to function.

Essential Always Active

Required for the website to function. Stores your cookie consent preferences.

Analytics

Help us understand how visitors use the site. We use Umami (privacy-focused, cookieless analytics) and Better Stack (automatic error reports) to improve the experience. Umami data is anonymous; an automatic error report carries which screen you were on — never the full page address — plus your browser and operating system and the technical details of the failure, which can include the id of the project involved.