Veil Privacy Policy
DRAFT: for lawyer review. Not for publication. Last updated: 2026-10-30
Square brackets mark items to fill in or confirm before launch. Delete the "Notes for the lawyer" section before publishing.
1. Who we are
Veil is a web app that helps doctors blur faces in before and after photos. It is run by:
- Controller: [Company name — Diogo Semedo, Unipessoal Lda, name change in progress]
- NIPC (company number): [NIPC]
- Registered address: [Registered address, Porto, Portugal]
- Privacy contact: [contact email]
We are the controller for the personal data described in this policy. We are based in Portugal and handle personal data under the EU General Data Protection Regulation (GDPR) and Portuguese law.
Veil is for doctors who use it in their professional work. It is not a service for patients.
2. The short version
- Your photos never leave your device. Veil does not upload, store or see the photos you edit.
- Saved files carry no camera or location data. Veil removes it on export.
- We keep very little. For access codes we keep the code, its distributor, its tier and type, whether it is active, its expiry date, the date it was first used and a count of exports. We don't ask for your name.
- No ads and no third-party trackers. Any analytics we use is cookieless and shows totals only.
- You stay responsible for your patients. Patient consent and the images you publish are yours to manage. You can clear Veil's data from your device at any time.
3. Patient photos and your responsibilities
Please read this section carefully.
- Veil is not a processor of your patients' photos. A processor handles personal data on someone else's behalf. You process patient photos on your own device, and Veil never receives them. We do not host, store or process them for you.
- You are responsible for them. For any patient photo you open, blur, export or publish, you are the controller. You must comply with the GDPR and with the Portuguese Medical Code of Ethics (Código Deontológico da Ordem dos Médicos), including its rules on confidentiality.
- Get consent. Before you take or publish a patient's image, make sure you have a lawful basis. For publishing, that normally means the patient's explicit consent. Keep the consent on file.
- Blurring does not make a patient anonymous. Tattoos, scars, distinctive features, or a name or logo in the picture or caption can still identify someone. Check every image before you post it.
- Minors. If the patient is under 18, consent comes from a parent or legal guardian.
- Requests about patient photos go to you. If a patient asks you to stop using or delete a photo, you handle it, because we do not hold the photo.
4. What we process, why, and how long we keep it
| Data | Why | Legal basis (GDPR Art. 6) | How long we keep it |
|---|---|---|---|
| Access code, distributor, tier (Sponsored or Pro), type (distributor or congress), active status, expiry date, creation date, batch ID | To check your code and unlock the right features | Art. 6(1)(b): needed to provide the service you ask for | Life of the distributor agreement or congress, plus 12 months. Then deleted, or kept only as totals with no code attached |
| First-used date and time | To start a congress code's expiry period and count activations | Art. 6(1)(b) and (f) | Same as the code |
| Export count per code | To count exports made with a code, so the distributor can see its use. Only a number is stored | Art. 6(1)(f): our and the distributor's interest in reporting use of sponsored codes | Same as the code. After that, monthly totals only |
| IP address on failed code attempts | To block guessing of codes | Art. 6(1)(f): security and fraud prevention | 24 hours at most |
| Access code you type in, and your access token when you use a sponsored feature | To check your code once and your access later | Art. 6(1)(b) | We don't store tokens on our servers. The token stays on your device (section 6) |
| Feedback you send by email | To reply and to improve Veil. The feedback button opens your own email app, and we receive only what you choose to send | Art. 6(1)(f) | Until resolved, and no more than 12 months |
| Aggregated analytics: Cloudflare Web Analytics [delete this row if not enabled at launch] | To see which parts of Veil are used, in total | Art. 6(1)(f). No cookies, and nothing stored on your device | Aggregated figures: [period, confirm with Cloudflare] |
| Connection data when a page loads: IP address, browser type, time, page requested | To serve Veil and keep it secure | Art. 6(1)(f) | Hosting provider logs: [period, confirm] |
| Business contact details of distributors and congress organisers: name, work email, phone | To agree codes, set up dashboards and keep in touch | Art. 6(1)(b) and (f) | Life of the agreement, plus [5] years |
We don't ask for your name, phone number or address to use Veil. A feedback email may include your name or address, because it is in your message.
We don't make decisions about you by automated means. The only automatic check is whether your code is valid.
5. What we never collect
- Photos. We never receive the photos you open, blur or export, including the blurred versions. Veil never uploads them.
- Patient information. No patient names, medical records or other patient data.
- Camera or location data. Veil removes it from every file it saves.
- Face data. Face detection runs on your device, only to find faces so they can be blurred. It does not recognise who anyone is, and its results are not saved or sent to us.
- Advertising or tracking data. No third-party ads and no third-party trackers. The banners in the Free version are our own.
6. Data stored on your device
Veil keeps a small amount of data in your browser's local storage on your device. Nothing in it is sent to us except the access token, which the app sends when it checks your access or counts an export.
- Your access token. It shows that your code was accepted. It is signed, so it cannot be forged, but it is not encrypted. It holds your code, your tier, the distributor name and the expiry date. Anyone who can use your device could read it.
- Your choices, such as tool settings and language.
- Your free exports this month, for the Free version. We don't count free exports on our servers.
Veil does not store your photos. They stay in your browser while you work on them. When you save or share an export, the file goes wherever you send it: your Downloads folder, your photo library, or another app through the share sheet. Those apps and services apply their own privacy policies. This includes Instagram if you post there.
If you add Veil to your home screen, your browser may keep copies of the app's own files so it works offline. These files contain no photos and no personal data.
Some browsers, such as Safari on iPhone, can delete this kind of data after a period without use. If that happens, you may need to enter your code again.
To clear your data, clear Veil's website data in your browser settings. This removes your token, your choices and your free export count. You lose sponsored access on that device until you enter your code again. [Before launch: add a "clear my data" button in the app.]
7. Who we share data with
We don't sell your data, rent it, or share it for advertising.
Processors act on our instructions:
- Cloudflare, Inc. (United States). Cloudflare hosts Veil (Pages), runs our API (Workers), stores access codes (D1), and provides security and, if enabled, Web Analytics. Cloudflare processes data under its data processing terms with us.
- [Email provider for the feedback inbox]. Hosts our mailbox.
Other recipients:
- Distributors. A distributor sees only counts for its own codes: codes issued, activated and active, and exports in total and per month. It also sees the last four characters of each code. It does not see photos or patient data. If you got your code from a distributor, that distributor may know that you received it.
- Apps you choose to share to, such as Instagram. Their privacy policies apply.
Cookies. Veil sets no cookies for doctors. Cloudflare may set a few strictly necessary security cookies, for example to tell automated traffic from people. Our admin area, used only by the Veil team, uses a session cookie.
Outside the EU. Cloudflare is a US company, and its network spans many countries, so data can be processed outside the EU and the EEA. Transfers rely on the EU Standard Contractual Clauses in Cloudflare's data processing terms, and on the EU-US Data Privacy Framework where Cloudflare is certified. [Confirm current status.]
Third-party files. Veil loads its code, fonts and face-detection files from our own domain, not from other companies' servers. [Confirm before launch.]
8. How long we keep data
- Access codes: life of the distributor agreement or congress, plus 12 months. Then we delete the record, or keep only totals that cannot be traced to a code.
- Export counts: kept with their code. After the code's period ends, we keep only monthly totals for each distributor.
- Failed-attempt counter: 24 hours at most.
- Feedback emails: until we have answered, and no more than 12 months.
- Analytics: aggregated totals only. We keep no visitor-level records.
- Business contacts: life of the agreement, plus [5] years.
- Photos: Veil keeps none.
- Device data: until you clear it.
- Backups held by our hosting provider are overwritten on the provider's cycle. [Confirm period.]
We review these periods every year.
9. Your rights
Under the GDPR you can ask us to:
- give you access to the personal data we hold about you;
- correct it if it is wrong;
- erase it, where the law allows;
- restrict how we use it;
- give you a copy of data you gave us, in a common format (portability), where this applies;
- stop processing based on our legitimate interests (objection).
We don't rely on your consent for anything in this policy, so there is nothing to withdraw. If that changes, we will tell you first.
How to use your rights. Email [contact email] with the subject "Privacy request" and say what you need. We reply within one month. For complex requests we can take up to two more months, and we will tell you why. We may ask for something that confirms it is you, such as the access code you used.
Data on your device. We cannot see or change it. You can clear it yourself (section 6).
Patient photos. If you are a patient, please contact your doctor, who controls your photos. We don't have them.
Complaints. You can complain to the Comissão Nacional de Proteção de Dados (CNPD), Portugal's data protection authority, at www.cnpd.pt. We would welcome the chance to resolve things with you first.
10. Security
- Photos stay on the device. There are no patient photos on our servers to breach.
- Codes are 10 characters long. After more than 10 failed tries from one IP address in 10 minutes, further tries are refused for a time.
- Tokens are signed with a secret key, so they cannot be forged. The server checks them on each request.
- Admin access is limited to the Veil team and protected by a password. Distributor dashboards are reached by a private link.
- Secrets, such as keys and passwords, are kept in Cloudflare's secret storage, not in our code.
- Encrypted connection. Veil is served over HTTPS.
- Breaches. If a breach puts personal data at risk, we will tell the CNPD within 72 hours where the law requires it, and tell affected people when the risk is high.
- Your part. Lock your phone and computer, and clear Veil's data on any device you share.
11. Children
Veil is for adults using it in their professional work. We don't knowingly collect data from anyone under 18.
12. Changes to this policy
We will update this page when Veil changes how it handles data, and we will show the new date at the top. For significant changes, we will tell you in the app before they take effect.
13. Contact
Questions about this policy: [contact email].