Forjed CD
Forjed CD Privacy Policy
This is the privacy policy of Forjed CD. Privacy policies differ for each service.
Last updated: October 27, 2026
Introduction
This policy explains what Forjed ("we") collects through Forjed CD (the "Service"), why, and how to delete it. File content and file names are encrypted in your browser before upload. We cannot decrypt them.
This policy follows the EU General Data Protection Regulation (GDPR) and Canada's Personal Information Protection and Electronic Documents Act (PIPEDA). Send questions to contact@forjed.xyz. We respond within 30 days.
Information we collect
We do not collect information that identifies you directly. Plus payments are processed by Stripe (see Third parties). We store only the data below.
| Data | Description | Purpose |
|---|---|---|
| Public ID | Random 32-character ID, used as your username | Identify your account; let others whitelist you |
| Private key (hashed) | Argon2id hash only. The key is shown once and not stored. | Verify login |
| Account creation time | Registration date and time | Account management |
| File content | Encrypted in your browser (AES-256-GCM) before upload. We store only the encrypted content. | Store and serve your files |
| File names | Encrypted in your browser (AES-256-GCM) before upload. We store only the encrypted name. | Show the name to you and people you share with |
| File size and upload time | Not encrypted | Show storage use and file list |
| Sharing settings | Private, burn-after-view, whitelist, editing allowed, confidential | Apply your access rules |
| Confidential warning text | Encrypted in your browser (AES-256-GCM) | Show your warning to viewers |
| Whitelists | Public IDs allowed to view or edit a file | Enforce access |
| Import reference | A file's original ID, kept when you re-import it | Prevent duplicate imports |
| Plus plan (if subscribed) | Stripe customer and subscription IDs, paid-until date, renewal status | Apply your plan; stop or resume payments |
When you or a whitelisted editor saves a PDF in the editor, the new file is encrypted in the browser and replaces the old one.
Information we do not collect
We cannot decrypt your files and do not log visits. We do not collect:
- Encryption keys or file passwords. The key in a share link follows the "#" sign, which browsers do not send to servers. Keys for password-protected files are derived in your browser.
- Readable file content or file names.
- IP addresses, browser details or visit history. Our server and app keep no access or error logs.
- Analytics, advertising or tracking data. No third-party fonts or tracking pixels. The only third-party script is Stripe's payment form, loaded only when you select "Pay with card".
- Location, camera or microphone data. Browsers are told to block these.
How we use your data
We use your data only to run the Service: login, file storage and sharing rules. We do not use it for marketing, profiling, analytics or advertising, and we do not sell it.
Legal basis (GDPR). We process your data to provide the Service you signed up for (contract, Art. 6(1)(b)). Security measures, such as the captcha and anti-forgery tokens, rely on our legitimate interest in protecting the Service (Art. 6(1)(f)).
Third parties
Our only third-party provider is Stripe, for Plus payments. We use no external login, captcha, analytics or font services. Registration uses a math question generated by our server.
Stripe. Stripe's script loads only when you select "Pay with card" in Settings. Before that, your browser does not contact Stripe, and Stripe does not receive your IP address or browser details.
After it loads, Stripe receives your card details, IP address and browser details to process the payment, and may set cookies. Stripe handles this data under its privacy policy. We do not send Stripe your account ID, name or email. Card numbers go directly to Stripe; we do not receive them. Stripe's advanced fraud signals are disabled. Stripe may process this data outside your country, including in the United States.
People you share a file with, by link or whitelist, can see the file and its name. Anyone with a share link can open the file unless it is private or whitelist-only.
Cookies and browser storage
The Service uses one cookie, to keep you logged in. It uses no tracking or advertising cookies.
- Session cookie. Holds a random session ID. Scripts cannot read it. It is deleted when you log out or close your browser. The server-side session holds your account ID, public ID and an anti-forgery token. During registration, it also briefly holds the captcha answer and your new keys until they are shown.
- Local storage. Your browser stores each file's decryption key, share link and title so you can reopen your files. This data stays on your device. You can export it from the Migration page. Clearing browser data deletes it; you then need the share link or password to open a file.
Visitors who only open a shared file get no cookie.
Retention and deletion
We keep account data while your account exists. Free plan files are deleted 24 hours after upload. Plus files are kept while Plus is active, and for 48 hours after it ends. You can also delete data at any time:
| Action | Deleted |
|---|---|
| Delete a file | Encrypted file, name, settings and whitelists, immediately |
| Open a burn-after-view file | File and record, on first download |
| Delete an object in the PDF editor and save | That text or image, removed from the file |
| Delete your account (Settings, confirmed with your private key) | Account, all files and records, your Stripe customer record, and your public ID on others' whitelists, immediately |
| Log out | Session, immediately |
You can also request deletion at contact@forjed.xyz. Include your public ID, since we hold no email address.
Security
File content, file names and confidential warnings are encrypted in your browser (AES-256-GCM) before upload. Password-protected files derive their key with Argon2id. Private keys are stored as Argon2id hashes. Downloads pass privacy, whitelist and burn-after-view checks. The Service sets browser security headers. The Service is built to limit what a breach can expose. We hold no names or contact details, and cannot read file content or file names. A breach could expose only encrypted files and limited metadata, such as public IDs, file sizes and upload times, which do not identify you directly. If a breach puts your data at risk, we notify the authorities as required by law and post a notice on the Service.
Your privacy rights
Under the GDPR, you can access, rectify, erase, restrict or port your data, and object to its processing. Under PIPEDA, you can access your information, withdraw consent where applicable, and complain to the Office of the Privacy Commissioner of Canada. In the EU, you can also complain to your local data protection authority. Send requests to contact@forjed.xyz with your public ID. You can also manage your files in My Files and delete your account in Settings.
Children
The Service is not intended for anyone under 16 in the EU or under 13 in Canada.
Where data is stored
EU users' data stays in the European Economic Area and moves to Canada only when needed. The EU recognizes Canada as providing adequate data protection. Canadian users' data is stored in the EU.
Changes to this policy
We announce changes on the Service 3 days before they take effect. Using the Service after that means you accept them.
Contact
Forjed, contact@forjed.xyz. We respond within 30 days.