Privacy Policy
Last updated: November 2026
This policy explains what personal data uploadtoblockchain.com collects, why, and how — in line with the EU General Data Protection Regulation (GDPR) and applicable data protection law, regardless of where you access the service from.
1. Data controller
Alexis Soulet, sole trader (auto-entrepreneur), SIRET 84270005600018, 2 place de la bourse, 69002 Lyon, France. Contact: support@uploadtoblockchain.com.
2. What we collect
- Email address — collected by Stripe at checkout, used to identify your order, send your confirmation and certificate, and track any prepaid credit balance.
- The file you upload — processed to compute its fingerprint (hash), optionally encrypted, and stored permanently on Arweave (see below — this is not like ordinary data storage).
- File metadata — original filename, size, and (if you chose encryption) the nonce and authentication tag needed to decrypt it later. We never store the decryption key itself.
- Payment information — handled entirely by Stripe; we never receive or store your card details.
- Business invoice details — company name and tax ID, only if you request a business invoice, collected and processed by Stripe.
We do not require or use passwords, and we do not build advertising profiles.
3. Why we process it
- To deliver the service you paid for (execution of contract).
- To send you the confirmation email, permanent link, and any Bitcoin certificate.
- To respond to support requests.
- To comply with accounting and tax obligations.
4. A special note on permanence
The core of this service is publishing a permanent, public record — by design, once stored on Arweave or sealed into the Bitcoin blockchain, a file's fingerprint and (unless encrypted) its content cannot be deleted, by you, by us, or by anyone, because these networks are public and decentralized, outside our control. This means the GDPR right to erasure (Article 17) cannot apply to data once published this way — by using the service, you acknowledge and accept this before your file is ever processed. We can, on request, delete the record we hold about your order in our own database (your email and order metadata), but this cannot remove the underlying public record.
5. Who else sees data, and why
- Stripe — processes your payment and email address. See Stripe's privacy policy.
- Arweave network operators — permanently and publicly store the file (or its ciphertext) you chose to upload.
- OpenTimestamps calendar servers — receive only your file's SHA-256 hash (never the file itself) to seal it into Bitcoin, if you chose a Certified Proof.
- o2switch — hosts this website and our database, in France.
- Google Analytics and Microsoft Clarity — traffic statistics and session recordings/heatmaps, only if you accept the cookie banner. Clarity data is processed by Microsoft (EU/US) — see Microsoft's privacy statement.
6. Retention
- Order and account metadata (email, hash, file size, encryption nonce/tag — never the key): kept for as long as needed to support your order and status page, and as required by accounting law (up to 10 years for billing records).
- The file itself, once published to Arweave, is retained by that network indefinitely — independent of us.
7. Your rights
Subject to the limitation in Section 4 above, you can ask us to:
- Access the data we hold about your order.
- Correct inaccurate data (e.g. a mistyped email, before it's used).
- Erase the order record we hold ourselves (not the underlying published file/certificate).
To exercise these rights, contact support@uploadtoblockchain.com. You may also lodge a complaint with your local data protection authority — in France, the CNIL.
8. Cookies
This site only uses analytics cookies (Google Analytics) if you accept them via the banner shown on your first visit. If you decline, no analytics cookies are set. You can change your choice at any time by clearing your browser's local storage for this site.
9. Security
The site is served over HTTPS. Decryption keys are never transmitted to or stored on our servers — see the Terms of Service for how client-side encryption works. Access to our database is restricted.
10. Changes
This policy may be updated from time to time; the date at the top reflects the latest revision.