Privacy Policy

Controller under Art. 4 No. 7 GDPR is the natural person:

Nico Brinkschröder

TokenIgnite

Gütersloher Str. 46

33161 Hövelhof

Germany

Email: contact@tokenignite.live

No company (GmbH/UG or similar) has been formed. No data protection officer has been appointed (Art. 37 GDPR does not require one for this operation).

TokenIgnite is a developer and design tool for local or closed-staging runtimes. The live token sync path writes and reads design-token state via Google Firebase Realtime Database (RTDB) without routing those live updates through REST server endpoints. The website, authentication, workspace coordination, waitlist, export/preview helpers, and similar flows use the TokenIgnite backend and Firebase Authentication / Firestore.

This notice covers personal and account-related data as well as technical processing required to operate those services. Design tokens themselves are design-system values (CSS custom properties and related metadata), not account passwords; they may still be associated with a TokenIgnite file and authenticated editors.

Depending on how you use TokenIgnite, the following categories may be processed:

The website and related clients use the following storage mechanisms:

The public website is hosted on Vercel (Vercel Inc., USA). Credentialed browser calls for session, email auth, and workspace routes go to same-origin /api/backend/* on the website host; Next.js proxies them to the TokenIgnite server and rewrites the ti_session Set-Cookie onto the website origin (SameSite=Lax). OAuth/Figma sign-in starts as a top-level navigation to the server; successful OAuth may mint a short-lived Firestore auth handoff that the website exchanges so the session cookie is set on the website origin.

Storage access on your device (TDDDG / ePrivacy): the locale cookie and the authenticated session / short-lived OAuth cookies are necessary for the service you request or for a function you expressly use (language choice; sign-in). They are set on that basis. Optional marketing cookies are not used.

Production website builds on Vercel may load Vercel Web Analytics. According to Vercel’s product documentation, Web Analytics does not set cookies and does not store identifiers in localStorage; it derives a daily-rotating request hash and may process technical signals such as pages visited, referrer, and device/browser/geo-derived information. Legal basis: legitimate interest in understanding aggregate Public Beta website usage and keeping the service operable (Art. 6 para. 1 lit. f GDPR). You may object by emailing contact@tokenignite.live.

Server and edge logs on Vercel may include IP addresses, user agent, timestamps, and requested URLs as part of ordinary hosting and security.

The TokenIgnite API/backend runs on Railway (Railway Corp., USA) and uses Google Firebase services operated by Google (including Google Ireland Limited / Google LLC as applicable): Firebase Authentication, Cloud Firestore (account, workspace, waitlist, handoff, usage/telemetry metadata), and Firebase Realtime Database (live design-token state, file meta, runtimeClients, capacity flag, related presence data).

Legal bases: performance of a contract / steps prior to contract for account and sync services you request (Art. 6 para. 1 lit. b GDPR); legitimate interest for security, capacity control, abuse prevention, and operational metrics (Art. 6 para. 1 lit. f GDPR); consent for waitlist signup (Art. 6 para. 1 lit. a GDPR).

These providers act as processors for TokenIgnite under Art. 28 GDPR on the basis of their published data-processing terms (for Firebase: Google’s Firebase Data Processing and Security Terms, including Standard Contractual Clauses / EU-US Data Privacy Framework mechanisms for restricted transfers as offered by Google). Vercel and Railway likewise provide published processor terms for their hosting platforms. International transfers to the United States or other third countries may occur as part of those services.

You may create or sign in with email/password or OAuth providers implemented by the product (Google and Figma; GitHub OAuth exists in the backend and may be enabled). Account profiles stored in Firestore typically include email, display name, avatar URL, provider, timestamps, and related membership links. Workspace/file records include ownership (ownerUid / historical createdBy), members, and file metadata.

Device login for the Figma plugin or SDK/CLI creates a short-lived server session; after you confirm on the website, the client receives credentials needed to operate (for example an ID token and stream configuration). Plugin/CLI clients may poll until authorized or until the session expires (about 10 minutes).

You can delete your account via the product account-deletion flow (DELETE /workspace/account). That flow revokes/deletes Firebase Authentication account(s) first, then removes or transfers owned files/workspaces and deletes the users/{uid} profile document as implemented. Some operational records (for example sparse usage aggregates or historical telemetry events, and waitlist entries) may not be fully erased by the automated account deletion path; contact contact@tokenignite.live to request further erasure where applicable.

The TokenIgnite Figma plugin runs inside Figma’s plugin environment. It stores file-binding and session configuration in Figma pluginData/clientStorage (see section 3). For authentication and workspace actions it contacts the TokenIgnite backend (for example device-login, file create/join, tokens-ready / ops coordination). In run mode, authenticated token updates are written directly to Firebase RTDB for the bound file; SDK/CLI clients subscribe to the same stream.

Figma Inc. acts as the platform that hosts the plugin and may process data according to Figma’s own terms and privacy policy when you use Figma. TokenIgnite receives only what the plugin/backend integration sends as described here (account linkage, file binding, design-token sync payload, optional telemetry).

Optional plugin product telemetry (allowlisted events with user id and optional file/plan metadata) may be written in production unless disabled by an operator kill-switch. It is not part of the live token write loop.

Developers install the published npm package tokenignite to run browser live sync (runTokenIgnite / initTokenIgnite) or the CLI (tokenignite run / export helpers). Bootstrap typically calls GET /files/stream-config on the TokenIgnite server (one-shot configuration such as stream/database URL and capacity flags). Live token apply uses a direct RTDB subscription; clients may register a runtimeClients heartbeat (technical last-seen / source / version, no email).

Unless you separately authenticate (for example device login), the SDK/CLI live path does not send your account email to the server as part of token streaming. Design-token values for the configured file id are read from RTDB and applied as CSS custom properties in the local/closed-staging runtime.

npm, Inc. distributes the package registry artifact; npm is not used as TokenIgnite’s primary personal-data processor for end-user accounts.

When you join a waitlist, TokenIgnite processes your email address, selected role/list, consent timestamp, source, and double-opt-in confirmation metadata based on your consent (Art. 6 para. 1 lit. a GDPR). Confirmation email is sent via SMTP configured for the website (WAITLIST_SMTP_*). Consent may be withdrawn by emailing contact@tokenignite.live. There is no automated self-service waitlist deletion endpoint in the product; deletion is handled on request.

IP addresses may be used transiently for in-memory rate limiting of waitlist submissions and are not stored as fields on the waitlist document.

In production, the backend/website may send operational notification emails to TokenIgnite mailboxes (for example signup, regularly active user, first tokens-ready file, waitlist confirmation notify, and internal ops radar). These messages support operating Public Beta and are not marketing newsletters to end users. Legal basis: legitimate interest in running and securing the service (Art. 6 para. 1 lit. f GDPR).

Sparse production usage metrics and plugin telemetry help capacity planning and product operations. They can be disabled by operator kill-switches. They are intentionally kept off the live token write hotpath.

Personal data may be disclosed to the following categories of recipients who process data on our behalf or as independent platforms you choose to use:

TokenIgnite retains personal data only as long as needed for the purposes described, subject to legal retention duties:

If the GDPR applies, you have the right of access, rectification, erasure, restriction of processing, data portability, and to object to processing based on legitimate interests, as well as the right to withdraw consent where processing is based on consent (Arts. 15–21 GDPR). You also have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR), for example the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW) for controllers in North Rhine-Westphalia.

To exercise these rights, email contact@tokenignite.live. The operator may need to verify your identity before fulfilling a request.

TokenIgnite is intended for professionals and is not aimed at children under 13. TokenIgnite does not knowingly collect personal data from children under 13. If you are a parent or guardian and believe that a child has shared information with the service, please contact the operator at contact@tokenignite.live.

TokenIgnite does not sell personal information or share it for cross-context behavioral advertising as those terms are commonly understood under the California CCPA/CPRA. Requests under US state privacy laws can be sent to contact@tokenignite.live.

This notice may be updated when the product or processors change. The “As of” date at the bottom will be revised. Material changes for registered users may also be communicated in-product or by email when appropriate.