Privacy Policy

1. Who operates Aderic

Aderic is operated by Firefly Tech Oy, Finland. Contact: support@aderic.io. We are the controller for account administration, security and our operation of the service. Business customers may separately determine the purposes of their own use of public discussions.

2. Information we process

We process your account name, email and sign-in records; organization settings and approved business information; the identifiers and username of connected Threads profiles; encrypted access tokens and expiry dates; public post text, available discussion context, timestamps and links returned by the official Threads API; AI assessments, suggestions, drafts, approvals and publication records.

We do not request Threads passwords. Connecting a profile grants the specific permissions displayed by Meta. Public keyword discovery depends on Meta approval; the test mode does not provide unrestricted access to other users’ content.

3. Purposes and legal bases

We use account information to perform our service agreement and maintain secure access. We process necessary public discussion data and operational records for legitimate interests in helping authorized businesses understand and respond to relevant conversations, subject to users’ rights and reasonable expectations. Where consent is legally required, we obtain it separately. Meta authorization is a platform permission, not a replacement for a lawful basis under data-protection law.

AI relevance scores are suggestions supported by source quotations. We do not infer wealth or sensitive characteristics, and do not use these scores for decisions about employment, housing, credit, insurance or similar eligibility.

4. AI processing

Necessary discussion text and approved business facts are sent through Vercel AI Gateway to OpenAI using GPT-6 Luna. Routing is restricted to OpenAI, without Azure or Bedrock fallback. Direct identifiers, usernames, links and credentials are excluded from the AI payload; detected contact details and URLs in text are redacted. Redaction is a minimization measure, not a guarantee of complete anonymization.

We do not train or fine-tune models on Threads data. Requests disable prompt training in Gateway routing and set store:false. These controls do not establish zero retention across every infrastructure or security system. AI output is unapproved until an operator reviews it; publication requires separate exact-text approval and an explicit action.

5. Providers and international processing

• Vercel: application hosting, server execution, infrastructure logs and AI Gateway.
• OpenAI: analysis of necessary text and generation of response suggestions.
• Supabase: hosted PostgreSQL for application records and authentication storage. Aderic uses Better Auth, not Supabase Auth.
• Resend (Plus Five Five, Inc.): delivery of sign-in emails. Threads discussion text and access tokens are not included in sign-in emails.

If you choose Google or GitHub sign-in, that identity provider processes the authorization under its own policies. Meta processes Threads authorization and API activity under its terms. Better Auth is software running in our service, not an additional hosted identity provider.

Historical payment records from the previous product may still be reconciled with Dodo Payments. This accounting does not enable new campaigns or send Threads discussion data to the payment provider.

Providers and their subprocessors may process information in the EEA, the United States and other countries, including for support and security. Aderic does not promise US-only processing. International transfers are subject to applicable data-protection requirements; contact us for information about applicable arrangements and safeguards. Provider information: Vercel, OpenAI, Supabase, Resend.

6. Storage, security and retention

Records are separated by organization and access is checked on the server. Threads tokens are encrypted at the application level using AES-GCM and are not returned to browser code. Tokens are removed on local disconnection or workspace deletion; expired tokens are removed by scheduled maintenance.

Scheduled maintenance removes discussion snapshots, associated drafts and AI results after 30 days without an update, and activity records after 90 days. Unresolved publication attempts may be retained pending reconciliation so the service cannot accidentally repeat an uncertain send. Organization settings and sign-in account information remain while the account is active or until deletion is requested. Deletion-request identifiers and status may be retained for accountability; completed requests are detached from the account after 90 days.

Provider backups and security logs have separate retention schedules. We do not intentionally put access tokens or full discussion text in application diagnostic logs. No separate advertising or third-party product analytics SDK is embedded in the new product.

7. Your choices and rights

You can disconnect Threads, revoke access in Threads Website permissions, delete your workspace’s stored platform data, or submit an account-deletion request at Data deletion. Removing local data does not delete posts already published on Threads.

Depending on applicable law, you may request access, correction, erasure, restriction or portability, and object to processing based on legitimate interests. Where processing is based on consent, you may withdraw it. We may need to verify identity and assess legal retention exceptions. We respond within applicable statutory periods, ordinarily one month under GDPR, with extensions where the law permits. You may complain to the Finnish Data Protection Ombudsman or another competent supervisory authority.

8. Historical accounts and changes

The current product focuses on Threads conversations. Existing account, contractual, billing and historical service records are not automatically erased or repurposed for a new purpose merely because the interface changes. We assess material changes and any required notices separately. No legacy mailbox or construction data is automatically imported into AI discussion analysis.

Material updates will be communicated where required. Contact support@aderic.io with privacy questions.