Privacy

No subscriber records, by design

A state 911 surcharge return is arithmetic over counts: how many lines, at what rate, for what period. It needs no subscriber names, no telephone numbers, no addresses, and no service records — and this product has nowhere to put them. There is no subscriber-level table in the schema, and importing a billing export writes only the aggregate counts you confirm. That is an architectural boundary rather than a promise about how we behave.

What we store

Your account’s email address, used to sign you in by magic link and to send deadline reminders. Your provider profile — the business details a state form asks for, such as the entity name, address, and federal tax identifier that get printed on your own return. Which states you have registered, with the account number and filing frequency the agency assigned you. The aggregate line counts you enter or import and confirm, each with a record of who entered it, when, and how it arrived. The filings you produce, frozen with their computation and provenance. And your subscription state, which comes from Stripe. If you use “Fill from your documents,” each value read from a PDF is stored as a proposal with its page number and, where the page has a text layer, the one printed line it came from, whether or not you accept it, together with your decision. If you fill a period’s line counts from a billing PDF, each proposed count is stored with its page number, the row label and the column header it was read from, both while it waits for you to accept it and after you accept or discard it. That page, row and column stay with an accepted count and with any filing made from it.

What we do not store, and do not log

Card numbers never reach our servers; Stripe handles them. Session tokens, magic-link URLs, and your line-count values are excluded from application logs and from error reports by a shared scrubbing step rather than by per-page care, and error reports are sent without request bodies. Uploaded import files are parsed for the columns you map and are not retained as a subscriber list. Uploaded PDFs are read and then discarded; we do not keep the file.

The optional column-mapping model

When you import a billing export, VoIP Remit can propose which column is which. That proposal is generated by a language model operated by Anthropic, and it is a mapping of column headings — you confirm every proposed mapping before any value is written. If no model key is configured, the feature degrades to manual column assignment and the rest of the import works unchanged.

Reading your documents

On your provider profile you can upload a PDF, such as an FCC Form 499-A, a W-9 or a state registration letter, so VoIP Remit can propose your profile details and registration details (an agency account number, filing frequency and registration date). A registration detail is never assigned to a state from the document: you pick the state it belongs to when you accept it. On the import page you can upload a billing PDF for one open filing period, so VoIP Remit can propose that period’s line counts. In both cases the whole document is sent to Anthropic, whose language model reads it for us, and the PDF is then discarded. Each proposed value shows the page it came from, with the printed line, or for a count the row and column, and nothing changes in your profile, registrations or counts until you accept it. A scanned PDF gives no counts. Upload pages with aggregate totals only; do not upload subscriber lists. If no model key is configured, document reading is unavailable and every field and count can be entered by hand.

Who processes data for us

Supabase hosts the database, authentication, and file storage. Cloudflare hosts and serves the application. Stripe processes payments and holds your billing details. Postmark sends transactional email, including magic links and deadline reminders. Sentry receives error reports, scrubbed as described above. Anthropic processes column headings when the optional mapping feature is used, and the whole document when you upload a PDF to fill your profile, your registrations or a period’s line counts. Each is a processor acting on our instructions.

Access, retention, and export

One account is one provider entity, and the database enforces that boundary on every read rather than relying on the application to remember it. Your filing archive is retained because it is a record you may need for years — several states require five — and export stays available to you whether or not your subscription is active. Ask us to delete your account and we will, subject to any records we are required to keep; export first, because deletion is not reversible.

Cookies

A session cookie keeps you signed in. There is no advertising cookie, no third-party analytics tag, and no cross-site tracking on this site; the public pages you are reading set no cookie at all.

If there is a breach

If a breach affects your private information and you live in New York, we will notify you as New York General Business Law § 899-aa (the SHIELD Act) requires — in the most expedient time possible and without unreasonable delay, and no later than 30 days after the breach is discovered, unless a law-enforcement agency determines that notice would impede a criminal investigation. Wherever you live, we will also notify you as other state and federal breach-notification law requires.

Contact

Privacy questions go to Lyra Ventures LLC at the address shown at the top of this page. The terms of service cover the rest of the relationship.