PRIVACY NOTICE
What the current product collects and why.
Updated October 18, 2026
This notice describes how FilingSift handles information across its website, free and paid accounts, APIs, billing, and support communications.
Information you provide
A sales, support, or contact request may include your name, work email, company, workflow, coverage needs, purchase timing, submission source, and follow-up status. Account records may include an email, display name, organization, membership role, API-key metadata, plan, usage, and account audit events. An enterprise-control request may include requested controls, identity-provider category, estimated seat range, target quarter, support-window preference, and a bounded note. A consented pilot record may include an organization-scoped pilot label, anonymous analyst-role category, anonymous issuer alias, paired task duration, evidence and fact audit counts, optional SEC filing provenance and evidence text, decision relevance, bounded notes, and retained session timestamps used to derive return use. Support email contains whatever you choose to send. Do not submit credentials, security reports, audit artifacts, material nonpublic information, confidential filings, personal financial data, or sensitive personal information.
Product and technical information
FilingSift records account email, display name, organization, a one-way password digest, hashed browser-session, API-key, email-verification, and password-reset tokens, bounded API usage, response size, query cost, key prefix and status, security fingerprints derived with a secret HMAC, authentication failures, and account changes. Production browser sessions use a Secure, HttpOnly, SameSite=Lax cookie; browser JavaScript cannot read the raw session token. Session or local browser storage contains only a non-secret signed-in marker and the server-issued expiration time. Standard browser sessions expire after 12 hours; choosing “Keep me signed in” extends the server session to seven days. Sign-out clears the cookie and both marker locations and revokes the server session. Cookie-free first-party analytics stores an allowlisted event name, page path, bounded properties, and event timestamps. It does not store an advertising identifier or IP address. Infrastructure and security logs may process an IP address, user agent, request path, status, timing, and timestamps; application logs are designed not to record query strings, authorization headers, passwords, session tokens, API keys, or request bodies.
Companies House public-register information
If the Companies House research feature is activated, authenticated users may request an exact company’s officers and persons with significant control. FilingSift returns only names, legal roles or control descriptions, and appointment, notification, resignation or cessation dates; corporate-controller records may also include provider-reported registration details. The server discards addresses, birth dates, nationality, occupation, identity-verification data, and person identifiers. Interactive results may remain in a process-local cache for up to five minutes and may be exported by the requesting user. Saved company links and alerts do not retain officer or control-person records. Public-register availability does not make FilingSift the source of those records or remove applicable privacy rights and responsibilities.
How information is used
We use information to respond to requests, provide and secure account access, qualify enterprise-control demand, operate and measure consented private pilots, manage subscriptions, enforce limits, troubleshoot, measure product use, maintain provenance and audit trails, support customer workflows, prevent abuse, and comply with law. FilingSift does not sell personal information or use third-party advertising cookies.
Service providers and disclosures
Current operations use Amazon Web Services for hosting, storage, and transactional account email through Amazon SES; Google Workspace for business and support email; Stripe for hosted Checkout and Customer Portal billing; and Cloudflare Turnstile for automated abuse protection on account and contact forms. Turnstile processes browser, network, device, challenge, hostname, and action signals needed to distinguish legitimate requests from automated abuse; FilingSift does not send the contents of those forms to Turnstile. Those providers process information under their applicable terms. Stripe processes payment information in its hosted interfaces. FilingSift retains billing identifiers, subscription state, invoice metadata, and billing-event records needed to manage access and reconcile payments. We may disclose information when you direct us, to protect rights and security, in a business transaction subject to appropriate safeguards, or when legally required.
Retention
Current targets are 90 days for first-party analytics, 24 months for sales and contact requests, 30 days for application and security logs, 30 days after the last attempt for authentication-failure records, 30 days after expiry for hashed verification and reset tokens, and 365 days for account audit events and Checkout/webhook operational records. Enterprise-control requests form an append-only organization procurement record and remain until the organization is deleted or a legal, security, or contractual requirement controls retention. Consented pilot records are append-only in the application and remain for the pilot or evaluation term plus the agreed follow-up, deletion, and legal-record period; no automatic pilot expiration currently runs. Deleting an individual account anonymizes it and does not erase the organization's pilot evidence. A verified organization-level deletion request is handled through an approved administrative retention process, subject to legal, security, and contractual obligations. Structured public filing facts, selected evidence passages, parsed tables, comparisons, and provenance are retained product records; reprocessing may replace current filing records. Raw downloaded SEC documents are discarded after processing. Financial records are retained according to applicable accounting, legal, and contractual requirements. Encrypted logical backups currently use a 35-day retention target; RDS automated backups retain 14 days. Legal holds, security incidents, and applicable law may require longer retention.
Security
FilingSift uses scrypt password hashing, hashed expiring browser sessions, hashed single-use account-action tokens, hashed API keys, Cloudflare Turnstile abuse protection, access controls, TLS, bounded requests, audit records, and separation between application roles. No system is perfectly secure. Please report a suspected security issue using the security contact process.
Your choices and deletion
You may request access, correction, or deletion of information you submitted, or opt out of product communications, by emailing support@filingsift.com. We will verify the request and may retain information required for security, legal, fraud-prevention, or recordkeeping purposes. Rights vary by location.
Children, international use, and changes
FilingSift is a business service not directed to children under 16. Current infrastructure is operated in the United States; users outside the United States understand that information may be processed there. We will update this notice as practices change and identify the current version by its effective date.
Contact
Privacy questions and requests may be sent to support@filingsift.com. FilingSift reviews this notice against current production practices and updates it when those practices change.