Your data
Everything we hold sits in two places: Stripe, which takes the payment, and one file store, which holds the order record, your photograph and the finished documents. There is no database, no customer relationship tool, and no third party we hand your details to for marketing. What follows is written from the code rather than from a policy template, which is why it includes the parts that are weaker than you might assume.
What is collected
| Collected | Stored in | Used for |
|---|---|---|
| Email address | Order record, and Resend to send the mail | Delivering the documents, order lookup, and support replies |
| Name, date of birth, gender, nationality, place of birth, country of residence, state or province, phone | Order record | Printed into the booklet and the ID card |
| Licence number, issuing country, licence class, issue date, expiry date | Order record | The licence details the translation renders |
| Portrait photograph and your signature | Two separate image files in the same store | Reproduced on the document |
| Payment details | Stripe only | We receive the checkout session id and the amount. Card numbers never reach our servers |
| Chosen destinations and validity, and the add-ons you selected | Order record | What you bought, and what the price was built from |
| First-touch attribution: landing page, referring site, utm parameters, Google click id | Your browser first, then copied onto the order record | Knowing which channel an order came from |
| Abandoned application: email, name, destination and validity, if you enter an email and do not finish | A separate lead record | Up to two reminder emails, then nothing further |
| Support email you send us, and our replies | A message record per email, grouped by your address | So a support thread survives longer than one inbox |
| A review, if you submit one: display name, optional country, rating, text | A review record, unpublished until approved | Shown on the site once approved |
How the store is protected
Each record is a file at a path derived from a secret, so the paths cannot be guessed or listed by anyone outside the service. They are not protected by a per-request permission check: whoever holds the full address of a file can read it. That is the same property that lets the download link in your email work without an account, and it is the honest description of the trade-off rather than a claim of encryption at rest that would not add anything here.
How long it is kept
Until you ask for it to be deleted. There is no scheduled purge and no retention window in the code, and an order record outlives the permit it produced because re-downloads and re-issues read from it. Stating a tidy “deleted after ninety days” policy that nothing implements would read better and be false.
How to have it deleted
Email support@vialy.org from the address you ordered with, quoting the order number. Deleting the order removes the record and its checkout pointer; the generated booklet, ID card and your uploaded photograph are separate files that this does not touch and that are removed by hand. Say you want the files gone too, so the request covers both.
Stripe keeps its own record of the payment, which we cannot delete and are not entitled to. A lead record from an unfinished application is deleted the same way, on the same request.
Analytics and advertising tags
Analytics, Google Ads and Reddit tags each load only when their measurement id is configured; where an id is absent, the tag never initialises. Arriving from a Google ad writes that click id to a cookie, and the page you landed on is kept in your browser so the order can be attributed to a channel. None of it is sold or shared for anyone else's marketing.
What is not on this page
A breach history, because there is no logging in place that would let us claim one way or the other, and an absence of evidence is not a record. The formal statement of your rights is the privacy policy; this page is the implementation detail underneath it.
Vialy is a private translation service, not a government body.