What we collect, and why.

Tinctloom operates a manufacturing platform for indie beauty brands. This policy explains what data we collect, why we collect it, how long we hold it, and the rights you can exercise. It covers the formula generation tool, the ingredient directory, and the accounts and payment features we are preparing to launch.

We try to keep the policy readable. If anything below is unclear, write to us.

When you use the formula generator, we receive the free-text brief you submit (product type, sensory targets, ingredient constraints) and the formula the platform returns. Briefs and completions are routed through the Polsia AI proxy on our behalf; we do not send them to any external model provider directly.

When you browse the ingredient directory, we receive standard request metadata (timestamp, requested path, anonymized browser fingerprint sufficient for rate limiting) for security and analytics.

When accounts launch, we will collect the email, name, and password (hashed) you provide at signup, plus session metadata needed to keep you signed in and to recover lost access.

When paid plans launch, we will collect billing metadata handled by Stripe as our payment processor. We do not store full card numbers; Stripe returns a tokenized payment method reference that we keep against your workspace.

We rely on three GDPR-grade bases across the service: consent (for marketing emails and optional analytics), legitimate interests (for security, abuse prevention, and product diagnostics), and contract performance (to deliver the formula generation, ingredient directory, and — once available — account and billing features you have signed up for). Where a feature requires a different basis we will surface that at the point of collection.

Formula briefs and completions: retained for up to 24 months so you can revisit prior iterations; deletable on request sooner.

Account profile and workspace data: retained for the life of the account and for 90 days after closure, then permanently deleted from primary storage and rotated out of backups within a further 90 days.

Billing records: retained for the period required by tax and accounting law (typically seven years from the last transaction).

Security and abuse logs: retained for up to 12 months in identifiable form; aggregated thereafter.

Today: Polsia (the AI proxy that routes formula generation requests), Render (application hosting), and our transactional email provider.

When the relevant feature launches: Stripe for payment processing and Better Auth for credential storage and sessions. The list above is updated as those features ship.

A current processor list, including sub-processor location and the lawful transfer mechanism (typically the EU Standard Contractual Clauses), is available on request.

You can request access to the personal data we hold about you, ask us to correct inaccurate records, request deletion, restrict or object to particular processing, or receive a portable copy of the data you provided. We respond to verified requests within 30 days at no charge; complex requests may take up to 60 days with status updates.

To exercise any of these rights, contact us at the address below. We may need to verify your identity before acting on the request (for example, by confirming control of the email address on file).

We use a minimal set of cookies: a session cookie to keep you signed in once accounts launch, a preference cookie for theme and locale, and a short-lived analytics cookie to count unique visitors. We do not use third-party advertising cookies and we do not sell data.

You can clear cookies in your browser at any time; clearing the session cookie will sign you out.

Tinctloom is a business tool for adult founders and operators. The service is not directed at children under 16, and we do not knowingly collect personal data from anyone in that age group. If you believe we have collected data from a minor in error, write to us and we will delete it.

Data may be processed in the United States, the European Economic Area, or other locations where our subprocessors operate. Where personal data moves across borders we rely on Standard Contractual Clauses or the successor EU–US Data Privacy Framework, and we apply additional safeguards (encryption in transit and at rest, access controls, audit logging) for sensitive fields.

We update this policy when we add a feature that changes what we collect, swap a processor, or change a retention window. The "Last updated" date at the bottom of the page reflects the current version; material changes are also announced in-app and by email once accounts launch.

Prior versions are archived and available on request.

Questions, complaints, or data-request letters: reach us at the address below. We answer; we do not delegate privacy requests to a faceless queue. [email protected].