This Privacy Policy explains how Filter8 ("Filter8", "we", "us") handles information in connection with the filter8() API, websites, and dashboards (the "Service"). It should be read together with our Terms of Service.
1. Our Role: Controller vs. Processor
For account and billing information, Filter8 acts as a data controller. For text and end-user content you submit to be filtered ("Submitted Text"), Filter8 acts as a data processor on your behalf — you determine why and how it is processed, and you are the controller.
2. Information We Collect
Account information — name, email, organization, and authentication data you provide when creating an account.
Billing information — plan, payment method (handled by our payment processor), and transaction records. We store a token, not your full card details.
Usage data — API request counts, characters processed, timestamps, rating and action distributions, per-evasion-class fire rates, error rates, and other operational metrics keyed to your account and keys.
Submitted Text — the text you send to be filtered. See Section 3.
3. Submitted Text
The core /v1/filter path is stateless: Submitted Text is processed in memory to produce a verdict and is not persisted after the response is returned. We do not use Submitted Text to train models.
If you enable the optional conversation layer (for detecting abuse split across messages), a limited recent window of Submitted Text is retained to perform that analysis, subject to the retention and erasure controls in Section 6.
4. How We Use Information
We use account, billing, and usage data to operate, secure, meter, and bill the Service; to provide support; to detect abuse and anomalies (for example, a leaked key spiking usage); and to improve the Service using de-identified, aggregated metrics. We use Submitted Text only to provide the filtering result you requested.
5. Logging (Privacy-Safe by Design)
Our structured request logs record the offsets of detected spans — where a match occurred — never the matched substring itself, and never the raw Submitted Text or any detected PII. Metric labels are cardinality-bounded and contain no content. This is a deliberate architectural property, not a configuration setting.
6. Retention & Erasure
Account and billing records are retained while your account is open and as needed to meet legal and financial obligations after closure. Aggregated, de-identified metrics may be retained indefinitely.
Conversation-layer data is retained only for a bounded window, with shorter caps for minor-rated content, and is encrypted at rest. You can delete it on demand through the erasure API by conversation, speaker, or message; deletions clean cross-references eagerly.
8. Security
We use industry-standard measures including encryption in transit (TLS) and at rest (AES-GCM for the conversation store), hashed key secrets, tenant isolation on every data path, and least-privilege access scopes. No method of transmission or storage is perfectly secure; we cannot guarantee absolute security.
9. Children
The Service is intended for use by businesses, not for direct use by children. Where you use the Service to filter content involving minors, you are responsible for obtaining any required consents. We support stricter thresholds and shorter retention for minor-rated content to help you meet COPPA and GDPR-K obligations, but compliance for your platform remains your responsibility as controller.
10. Your Rights
Depending on your jurisdiction, you may have rights to access, correct, delete, or port your personal information, and to object to or restrict certain processing. Account holders can manage much of their data in the dashboard; for other requests, contact us. Where Filter8 acts as a processor for Submitted Text, we will assist the controller in responding to end-user requests.
11. International Transfers & Residency
The managed Service runs in our primary region by default. Where information is transferred across borders, we rely on appropriate safeguards such as standard contractual clauses.
12. Changes to This Policy
We may update this Policy from time to time. We will post the updated version with a new "Last updated" date and, for material changes, provide reasonable notice. Your continued use after changes take effect constitutes acknowledgment.
13. Contact
Privacy questions or requests: [email protected].