1. What this service does
Bagsey calculates a SHA-256 fingerprint of a selected file in the customer’s browser. In the standard flow the source file is not uploaded. Bagsey stores account details, the fingerprint, file name/size and supplied metadata, payment and order records, signed evidence, verification events, and support correspondence needed to operate the service.
2. Who is responsible
The controller must be identified here before launch: [FULL LEGAL ENTITY NAME], [REGISTERED OFFICE], [CONTACT EMAIL]. Do not rely on this draft as a complete notice until those details, applicable registration numbers and data-protection contact route have been checked.
3. Why we use personal data
We use account and service data to perform the contract, secure accounts, prevent fraud, respond to support requests, meet legal/accounting obligations and pursue legitimate interests in service integrity. Payment card data is handled by Stripe; Bagsey should not store full card details. The applicable lawful basis, processors, international-transfer safeguards and retention schedule require review before launch.
4. Retention, evidence and your rights
Evidence and order records may be retained for the purchased verification term and any lawful accounting, security or dispute period. This is not an unlimited-retention promise. Requests for access, correction, objection, restriction or erasure must be assessed individually because deletion cannot silently rewrite signed historical evidence or override legal obligations.
5. Cookies and similar technology
Bagsey uses essential session cookies to keep an authenticated customer signed in and protect requests. They are not used for advertising. Before any analytics, advertising, non-essential storage or new third-party tracking is enabled, this notice and a consent mechanism must be reviewed and updated. Customers can remove cookies in their browser, which may sign them out.
6. Security and contact
Use the support contact above for privacy requests; do not attach an original confidential document unless a safe support route has been agreed. This draft does not promise absolute security or perpetual hosted availability. Customer-held evidence packages remain useful independently of hosted verification when verified with a separately trusted key.