Privacy policy

Who is responsible

FilingWire is operated from Quebec, Canada. The operator is the controller of any personal information described below and can be reached at hello@filingwire.io.

What the website collects

The site sets no advertising cookies and runs no third-party analytics scripts. Requests are logged by our hosting provider with the requested URL, the IP address, the user agent and a timestamp, under that provider's own retention. We do not build profiles from them.

The ticker lookup validates what you type before it queries anything, and the symbol is used to answer that one request. It is not stored against you, and a value that is not a ticker shape is never queried, stored or reflected back.

The email brief

If you subscribe to the brief we store your email address, the cadence you chose, a short referral tag naming the page or campaign you came from, and the timestamps for signing up and confirming. Nothing else. We use it to send that brief. We do not sell it, rent it, or pass it to a third party for their own use.

Every issue carries an unsubscribe link, and one opt-out covers every message we send, not only the brief. Unsubscribing keeps the address on a suppression list rather than deleting the row, and that is deliberate: the suppression list is what the outreach queue checks before it drafts anything, so deleting the record would quietly make you contactable again. Ask us and we will delete it outright.

API keys and billing

Subscriptions are sold through RapidAPI, which handles the account, the payment and the key. We receive usage counts and the tier associated with a key, not your card details.

RapidAPI processes your account data under its own privacy policy, which is worth reading if you subscribe.

Personal data inside the data itself

The Funding API contains no personal data. Every field is read from the Form D, and the related-persons section is not extracted.

The Risk API is different, and we will not pretend otherwise. Its structured fields are business level, but the short summary is written from the filing text and can name an executive where the filing does, for example on a departure disclosed under Item 5.02. That information is already public in a document published by the SEC. It is still personal data, and if you process it you carry your own obligations for it.

We keep it because redacting it would remove the most useful part of the most requested event type, and because pointing at what a public filing already says is more honest than quietly hoping you do not notice.

How long things are kept

Server logs, under the hosting provider's retention. Brief subscriptions, until you unsubscribe, after which the address stays on the suppression list described above unless you ask us to remove it. Filing records are public data and are kept indefinitely, because a corpus you cannot look backwards in is not much use.

Your rights

You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted, by writing to hello@filingwire.io. Where the request concerns information reproduced from a public SEC filing, we will explain what we can and cannot remove, since we do not control the source document.

Changes

Material changes are announced to brief subscribers and to active API subscribers, and the effective date at the top of this page changes with them.