Legal
Privacy Policy
Last updated 13 September 2026
Who controls your data
Armillary Sphere LLC, a Texas limited liability company, trading as Proofwire, at Austin, Texas 78735, United States. For anything in this notice, write to hello@armillaryspherellc.com.
What we collect, and why
We collect only what the service needs. There is no advertising network on this site and we do not sell data.
| What | When | Why |
|---|---|---|
| Name, email, company, website | At checkout | To identify the order, contact you about it, and tell an outlet who is announcing |
| Your press release and media contact | After payment | It is the thing we distribute. It is written to be published |
| The name of whoever authorised the release | After payment | Networks require a named, accountable contact |
| Order and payment records | At checkout | Accounting, and answering questions about an order later |
| Published URLs and check results | After distribution | The report you bought |
| A sign-in token tied to your email | When you sign in | Access to your own orders |
We never see your full card number. Stripe collects your card details directly. With the payment result, the amount and its own reference, Stripe sends us the name on the card, your email, and your billing country and postcode (a full billing address only if Stripe asks you for one). If a payment is refunded, it also sends the payment method's details: for a card, its brand, last four digits, expiry and fingerprint; for a bank debit, the bank name, routing or sort code, last four digits and fingerprint; for another method, such as a wallet, the details that method returns, for example your Cash App $cashtag and buyer ID. A fingerprint is Stripe's code for recognising the same card or account again, not the number itself. If a payment is disputed, it sends the card brand and the dispute itself. We keep these payment records.
Your release is intended for publication
Everything in the release itself — company, contact name, contact email, the copy — is written to be published on third-party websites. Once an outlet publishes it, that page is theirs. We cannot remove it, and neither can the network. Please do not put anything in a release you would not want permanently public.
Who else processes it
| Processor | What they get | For |
|---|---|---|
| Stripe | Your name, email, company, website and payment details | Taking payment |
| Our distribution partners | The release and its contact details | Distributing it |
| Resend | Your email address and message content | Sending transactional email |
| Supabase | Order and account records | Hosting the database |
| Vercel | Whatever a request carries, plus server logs | Hosting and serving the site |
| Inngest | Order and job references, never your release or contact details | Scheduling the work behind an order |
| Ahrefs | An outlet's domain name, on its own | Looking up a domain rating |
We also fetch published pages to check them. Those requests identify us honestly by user agent, honour each site's robots.txt, and carry no information about you.
How long we keep it
We do not run a deletion schedule, and this notice does not promise one. Records are kept for as long as they are useful for answering a question about an order and for as long as our accounting obligations require, and they are removed when you ask and we are able.
One thing here IS enforced by the software rather than by intention, and it is stated as a fact about the code rather than as a policy:
- Sign-in tokens — 15 minutes, and once only. Consumed on first use. The signed-in session it creates lasts 24 hours, after which you request a new link.
Everything else — your order, the payment records Stripe sends us, the release you sent us, the report, and any message you have written to us — persists until it is deleted on request. A report you have shared stays reachable at its link for as long as the record exists. If that matters to you, ask us to remove it and we will.
Your rights
You can ask us to give you a copy of your data, correct it, delete it, or stop using it. Write to hello@armillaryspherellc.com and we will respond within one month.
Two honest limits. We cannot delete a release an outlet has already published — that page belongs to the publisher. And we cannot delete records we are required to keep for accounting.
If you are in the UK or EU, you can complain to your data protection authority. If you are in California, we do not sell or share personal information as those terms are defined in the CCPA, and we will not discriminate against you for exercising your rights.
Cookies
We use no advertising or tracking cookies. The only cookie set is the one that keeps you signed in after you use a sign-in link. It is strictly necessary, and there is nothing to opt out of.
Security
Sign-in links are single-use, expire in fifteen minutes, and are stored as hashes rather than as tokens. There are no passwords to lose. Traffic is encrypted in transit.
No system is perfect. If we discover a breach affecting your data, we will tell you and the relevant authority as the law requires.
Changes
When this notice changes, the new version is published on this page and the date at the top of it changes. That dated version is the notice, and it is the one that applies from the day it appears.
If a change materially affects how we use data you have already given us — a new processor that can see your release, or a new use for something you have already sent us — we will email the address on your order. That is the only mail this notice commits us to. A wording fix, a clarification, or a change that affects only orders placed afterwards is published here and not emailed.