Filecrux is in beta. The product may change as we learn from readers.

Filecrux

Privacy Policy

Effective 31 August 2026.

This policy explains what Filecrux collects and why. Filecrux is operated by Crescera Systems LLC, 754 S Val Vista Dr #103, Gilbert, AZ 85296. Send privacy or deletion questions to support@filecrux.com.

Information you give us

We keep your email and account details. We keep messages you send to support and records of how you use the reports.

Older records may still hold things the current product no longer uses. That includes a saved list of companies, a company request from the wait list, and billing details from when Filecrux charged for a subscription.

Payment information

Filecrux does not take payments today. When it did, Stripe handled every card entry and Filecrux never stored a full card number.

Stripe still holds the invoices, charges, and refunds from that time. Filecrux still keeps the Stripe customer and subscription IDs, subscription status, price, billing-period end, and whether the subscription was set to cancel. We keep those records so we can answer a question about an old charge.

Sign-in, logs, and analytics

We use a first-party sign-in cookie to keep you signed in. Our host receives normal request data, such as IP address, time, page, browser details, and errors.

We use PostHog to learn how people use Filecrux. It records page views and actions such as clicks. Replay is turned on for public pages. It can record pages you visit, mouse movement, clicks, scrolling, and browser console messages. It can keep recording if you move from a public page to a signed-in page without reloading. Text typed into normal form fields is masked by our current settings.

On public pages we ask PostHog to track you without a cookie. If you move from a public page to a signed-in page without reloading, that setting can stay in place until you reload. On signed-in pages, PostHog stores an ID in your browser, including a cookie. Signed-in events can be connected to your Filecrux user ID and email. Filecrux removes its session cookie and authorization header before browser analytics are sent to PostHog.

Why we use information

We use information to run and secure accounts, send sign-in links, publish reports, answer support, measure the service, stop abuse, fix errors, and keep payment and service records from the time Filecrux charged.

Who helps us

Amazon Web Services hosts Filecrux, its database, files, service email, and logs. Google Workspace receives support email. Stripe holds the payment records. PostHog handles product analytics. Anthropic tools help staff write reports from public SEC filing material. Telegram and PagerDuty receive operations alerts. The U.S. SEC provides public filing data.

We do not sell personal information for money.

How long we keep information

We keep information while we need it to run Filecrux, keep payment and security records, solve disputes, and follow the law. Different records last for different times. Backups, logs, Stripe records, support mail, and public filing records may last longer than an active account.

Your choices

You may email support@filecrux.com to ask a privacy or deletion question. We will review the request and tell you what we can remove and what we must keep. Filecrux does not offer self-serve account deletion today. We do not promise that every linked record can be deleted or give a set deletion time.

If Filecrux charged you in the past, you can open your account and reach your Stripe billing history from there.

We may change this policy when Filecrux or the law changes. We will show the new effective date on this page.

Privacy Policy — Filecrux