Controller and contact
FactNot, operated by Factnot LLC, is responsible for the product account, workspace, and privacy-rights workflows it operates. Privacy requests can be submitted from /privacy/request or sent to privacy@factnot.com.
- Logged-in requests are treated as verified from the active session.
- Logged-out requests require email verification before review.
- Administrative actions on privacy requests are audit logged.
Data categories and use
FactNot processes account details, profile settings, workspace content, messages, uploads, activity and security logs, newsletter state, AI prompts/outputs, search indexes, embeddings, and support or admin records to provide, secure, troubleshoot, and improve the service.
- The lawful basis depends on the context, including contract performance, legitimate interests, consent, and legal obligations.
- Account export is available as JSON with a manifest; exported payloads are not stored in logs.
- Account deletion is scheduled with a 7 day grace period and then anonymizes the user row while revoking credentials.
- Shared workspace content may be retained with deleted-user or anonymized attribution where needed for collaborators, publication state, legal, safety, backup, or audit reasons.
- Private uploads, PDFs, source bodies, notes, and workspace records are not public by default, but users control sharing and publication settings.
EU/EEA and UK privacy rights
Depending on your location and the context of processing, you may have rights to access, correct, delete, export, restrict, object to, or withdraw consent for certain personal data.
- You can use Settings for available account export and deletion controls.
- You can submit a privacy request from /privacy/request or email privacy@factnot.com.
- Some requests may be limited by account security, public/shared content, collaborator rights, backups, legal obligations, abuse prevention, or records needed to complete the beta service.
AI processing
AI-assisted features may send selected workspace content, prompts, source text, excerpts, metadata, and derived records to configured model, embedding, search, and infrastructure providers so FactNot can produce summaries, extractions, answers, verification signals, and search results.
- Do not use AI features on sensitive material unless you are comfortable with that processing.
- AI output can be wrong and should be reviewed against reliable sources.
- Exact provider, retention, training, region, and subprocessor claims are tracked in the current vendor inventory.
Save to FactNot browser extension
When you choose Save in the Save to FactNot Chrome extension, the extension sends FactNot only the selected public page URL and destination library ID for that save. FactNot then fetches the public page or PDF on its servers and stores the result privately in the selected workspace destination.
- The page title and hostname preview stay in the popup and are not sent as separate fields.
- The extension does not capture page DOM, rendered or paywalled content, notes, tags, highlights, or an offline queue.
- OAuth access and refresh tokens and pending PKCE state are held in Chrome session storage. Only the last selected library ID is kept in Chrome local storage.
- Extension telemetry records aggregate outcome and latency data without article URLs or bearer tokens.
Current beta service providers
FactNot uses third-party service providers to run the beta, store private uploads, send transactional email, protect signup and authentication surfaces, route AI requests, and manage the factnot.com domain.
- Hosting and database: Fly.io Machines and Fly Postgres.
- Private upload/object storage: Tigris Data.
- Transactional email and contact mail routing: Resend and Namescheap Private Email.
- AI routing: OpenRouter routing DeepSeek and other configured model providers.
- Signup and abuse prevention: Cloudflare Turnstile.
- Domain registration and DNS: Namescheap.
Retention and transfers
Retention follows the internal retention schedule in docs/privacy/retention-schedule.md. Search indexes and embeddings follow source deletion. Deleted data may remain in encrypted backups until backup expiry and must be erased again if restored.
- Vendor, DPA, subprocessor, and international-transfer evidence is tracked in docs/privacy/vendor-inventory.md.
- Do not rely on vendor security pages alone for controller obligations.
- This policy should be reviewed whenever hosting, vendor, AI, analytics, or backup behavior changes.