1. Information collected

Nixie Studio currently processes a limited set of data needed to operate the platform and its collaboration features:

• Account and identity data such as your user ID, display name, avatar, email address, and login provider details supplied through supported authentication flows.
• Workspace, project, and collaboration data such as workspace names, project names, editor content, save revisions, collaborator roles, invites, comments, and realtime presence signals.
• Safety moderation inputs such as public profile display names, profile avatars, project chat messages, and certain project asset names or uploaded images when they are checked for abuse, harmful content, or policy violations.
• Technical and diagnostics data such as browser information, app version, request metadata, and error details needed to operate, secure, and troubleshoot the service.
• Local browser data such as editor settings, drafts, clipboard payloads, and recent workspace or project references stored on your device.

2. How the data is used

Data is used to authenticate users, load and save projects, keep collaboration sessions in sync, recover local drafts, enforce role-based access, improve stability, and protect the service from abuse or operational issues.

Nixie Studio also uses automated safety checks on certain user-submitted text and images to detect content that may violate product rules or create abuse, safety, or operational risks.

Nixie Studio does not currently use optional third-party analytics tracking on these routes.

3. Current service providers

• Supabase is used for authentication, database storage, and related account or project data services.
• OpenAI is used to process certain text and image submissions through its moderation API so Nixie Studio can help detect unsafe or disallowed content before it is accepted.
• OAuth identity providers such as Google or Discord may be used as sign-in providers depending on the account method you choose.
• Hosting and infrastructure providers may process technical request data needed to deliver the service securely and reliably.

4. Sharing and disclosure

Your workspace and project data is shared with collaborators you intentionally invite or otherwise grant access to inside the product.

Outside of that collaboration context, data is only shared with service providers needed to operate the app or when disclosure is required to protect the service, users, or comply with legal obligations.

When automated safety moderation runs, the submitted text or image being checked is sent to OpenAI for moderation processing. That can include a display name, avatar image, chat message, project asset filename, project asset display name, project folder name, or a reduced image derived from an uploaded project asset.

5. Retention

Stored account, workspace, and project data is retained for as long as it is reasonably needed to operate the service, maintain collaboration state, respond to support issues, or protect the service.

Safety moderation requests are processed when submitted content is checked. Operational logs may retain limited request and error details needed to monitor service health, enforce policy decisions, and troubleshoot moderation failures.

Local browser data remains on your device until it is replaced, cleared by the app, or removed by you through browser storage controls.

6. Your choices

You can review current browser-storage details.

You can also clear browser-local data through your browser settings or stop using the service if you no longer want new data to be processed.

7. Policy updates

This policy may be updated from time to time to reflect operational, technical, or legal changes.

The date at the top of this page indicates the latest revision.