Privacy policy.
What we collect. What we never do.
Summary in one paragraph.
CyberSygn collects the smallest amount of information needed to make signing work. Detection runs in your browser; the PDF never leaves your device during that step. When you invite remote signers, we store the PDF encrypted in Cloudflare KV for thirty days. We use Resend to send transactional emails, Stripe to process payments, and Cloudflare to host everything. We do not use cookies for tracking, we do not sell your data, we do not run ad networks, we do not share contact lists with anyone, and we do not train AI models on your contracts.
1. What we collect.
Account data. Name, email, password hash (if you create a paid account), and a stable sender ID we generate in your browser localStorage. Used to identify you in the dashboard and tie documents to your account.
Document data. Uploaded PDFs and Word documents when you invite remote signers. Stored encrypted at rest in Cloudflare KV with a thirty-day TTL, then auto-deleted unless you download them. Detection itself runs in your browser; the document does not leave your device during detection.
Signer data. Names and email addresses of people you route documents to. Stored on the document record. Signers themselves do not need a CyberSygn account.
Audit metadata. Every signing event captures a timestamp, the signer's IP address, and their user agent string. This is what makes the signed document evidentiary. The audit certificate page includes this data.
Payment data. When you pay, your card information goes directly to Stripe. We never see card numbers or CVCs. We do see your subscription tier, status, current period end, and a Stripe customer ID.
Telemetry. Page views, feature events (upload, send, sign, complete), and caught errors. Stored in Cloudflare Workers Analytics Engine, our own first-party storage. Linked to a hashed sender ID, not your name or email. No cookies, no third-party tracking, no advertising identifiers.
2. What we do not collect.
- Card numbers, CVCs, or bank details. Those go directly to Stripe.
- Browsing history outside CyberSygn.
- Location beyond country and city (resolved from your IP by Cloudflare).
- Anything from third-party data brokers.
- Biometric data.
- Contents of your other documents, calendar, or contacts.
3. Why we collect what we collect.
- Account data: to let you sign in, see your documents, and contact you about your account.
- Document and signer data: to deliver the signing service you asked for.
- Audit metadata: because a signature without a trail is just a picture.
- Payment data: to charge you the right amount and keep your subscription accurate.
- Telemetry: to know which pages convert, which features get used, and where the product breaks. Aggregated, never to profile individuals.
4. Who we share data with.
Three vendors, all listed below. Each is a subprocessor under standard data-processing agreements. We do not share data with anyone else.
- Cloudflare (hosting, storage, DNS, analytics). All your data lives on Cloudflare infrastructure.
- Resend (transactional email). Your name and email address get sent to Resend when we deliver magic links and completion emails.
- Stripe (payments). Card data goes here. Stripe gets your email and the subscription details.
We do not share data with advertising networks, data brokers, marketing platforms, or AI model providers.
5. How long we keep it.
- Account data: until you ask us to delete it. Within thirty days of deletion request, removed from production systems; encrypted backups roll off after ninety days.
- Document files: thirty days after upload, then auto-deleted. You can delete sooner from the dashboard.
- Audit metadata: kept with the document record; deleted when the document record is deleted.
- Payment records: as long as Stripe and our accountants need them for tax law (typically seven years).
- Telemetry: ninety days, then aggregated and the raw events deleted.
6. Your rights.
Wherever you live, you can:
- Ask what we have about you. We will send a JSON export within thirty days.
- Ask us to correct or delete it. Same thirty-day window.
- Cancel and walk away. Your subscription stops at the end of your billing period; your data deletes within thirty days unless you say keep it.
- Opt out of telemetry. We do not currently surface a toggle in the UI; email us and we will exclude your sender ID from collection within seven days.
If you live in the EU, UK, or California, you also have rights under GDPR, UK GDPR, and CCPA respectively. They overlap heavily with what we already do above. Specific requests: privacy@cybersygn.io.
7. Cookies.
We do not use cookies for tracking. We use one localStorage key (cybersygn.senderId) to identify your browser as belonging to one user, one key for your theme preference, and a token key when you are signed in. None of these leave your device except as documented above.
8. AI training.
We do not use your contracts to train AI models. We do not allow our vendors to use your contracts to train AI models. Our robots.txt deliberately welcomes AI crawlers to our public marketing pages because we want to be cited when someone asks ChatGPT for a DocuSign alternative, but no AI crawler ever has access to documents you upload.
9. Children.
CyberSygn is not for children. We do not knowingly collect data from anyone under thirteen.
10. Security.
Documents are encrypted at rest. Sessions are scoped to the device that signed in. Magic links are 256-bit random tokens. Audit certificates carry a SHA-256 fingerprint of the original document. No system is perfectly secure; if we discover a breach affecting you, we will notify you within seventy-two hours of confirming it.
11. Changes.
If we change this policy in a way that affects you, we will email you before the change takes effect. Material changes also surface on this page with the updated date at the top.
Contact.
privacy@cybersygn.io for privacy questions. hello@cybersygn.io for everything else. We answer.