Privacy notice
Draft pending legal review.
Last updated: 31 July 2026
This notice describes what Referly stores, where it stores it, and what you can do about it. It is written to be understood, not to cover us: if anything here does not match how the product works, that is our mistake and we want to hear about it.
Who is responsible
Referly, an independent product. For anything about your data, write to hola@referly.id.
What we store
Your email, to identify you and send your sign-in link. Your dossier content: what you write in each section and the images you upload. The public address you choose. And a record of when your profile is visited and when you generate a PDF or someone downloads your contact card.
We do not ask for a password, so we store none. We do not ask for a card. We do not store your IP address alongside your profile, and we do not build an advertising profile of you.
Where it is stored
In Supabase (database and file storage) and on Cloudflare, which serves the pages. Your images live in a storage bucket whose addresses are public: anyone with an image’s exact address can view it, even while your profile is unpublished.
What is public and what is not
Your profile is only reachable if you publish it, and even published it is not indexed by search engines: it reaches whoever you send the link to. Every section can be public, PDF-only, or hidden — anything marked PDF-only never appears at your public link.
Trackers
None. Your public profile loads no third-party scripts, pixels or fonts. Not even a YouTube video thumbnail: we fetch it once and serve it ourselves, so nobody outside Referly learns that someone is reading your profile.
Deleting your account
From your dashboard, at the bottom of the page. You type your address to confirm and everything goes: first your images from storage, then your account, your dossier, your sections and your visit records. We keep no copy and you do not have to write to anyone. It cannot be undone.
Changes
If we change anything material in this notice, we will say so here with the date. The version on this page is always the current one.