Last updated 30 September 2026
Privacy Policy
This explains what RelayMe does with personal data. RelayMe is a link-in-bio service at relayme.bio, operated by ClearPath Advisory.
1. Who is responsible
ClearPath Advisory
ul. Michała Kleofasa Ogińskiego 11 lok. 9, 03-318 Warszawa, Poland
NIP 9512604332
hello@relayme.bio
We have not appointed a Data Protection Officer, and are not required to, because we do not carry out large-scale monitoring or process special category data as a core activity. Write to the address above with any question about this policy.
2. Two kinds of people
This policy covers two groups, and they are treated differently:
- Account holders — people who sign up and build a page.
- Visitors — people who open somebody’s public page at relayme.bio/name.
Where a section applies to only one group, it says so.
3. What we collect from account holders
Your email address. Collected when you sign in. We use passwordless sign-in, so we never receive or store a password.
If you choose Google sign-in. Google authenticates your account and shares your Google account identifier, email address and basic profile information, such as your name and profile photo, with our authentication provider Supabase. We use these details to identify your RelayMe account. Google sign-in requests basic identity information only; it does not request access to your Gmail messages, contacts or Google Drive files. You can still use an email sign-in link instead. Google sign-in is separate from optional marketing measurement and does not depend on accepting the marketing banner.
The content of your page. Your username, display name, bio, links, social handles, chosen theme, fonts and colours, and any profile photo or background image you upload. All of this is content you choose to publish, and it is public by design once your page is live.
Subscription details, if you pay. We store a Stripe customer reference, your plan, its status and its renewal date. We never see or store your card details — those go directly to Stripe and never touch our servers.
4. What we collect from visitors
When someone taps a link on a public page, we record:
- which link was tapped, and which page it belongs to
- the time of the tap
- whether the browser looks like a phone or a computer
- the referring website address, where the browser supplies one
- the country the request came from, as a two-letter code such as PL or US, supplied by our host. We store the code and nothing narrower — no city, no region, and no address. Page owners on a paid plan see a count of visits per country for their own page.
We do not record IP addresses, device identifiers, names, or anything that identifies a visitor personally. We do not set cookies on visitors, and we do not build profiles, follow people between pages, or share this data with advertisers. Tap counts and country counts are shown only to the owner of the page in question, as totals — never as a list of individual visits.
5. Storage in your browser
RelayMe stores three necessary things in your browser to provide the service. On our marketing and sign-up pages only, it can also store your marketing measurement choice and a temporary signup marker if you opt in:
- Your sign-in session — keeps you logged in, until you sign out.
- relay.pending — holds Pro settings you are trying out, so they survive the trip through checkout. Cleared when applied or discarded.
- relay.invite.seen — remembers you have dismissed the sign-up prompt, so we do not show it again.
- relayme.marketing-measurement-consent-v2 — records whether you accepted or rejected optional Google and Meta measurement on our marketing and sign-up pages. Earlier Google-only choices do not authorize Meta.
- relayme.marketing-signup-intent — temporarily records when an opted-in visitor starts signing up, so a completed registration can be distinguished from an email-link request. It contains a time, not an email address, and is cleared after the sign-in callback.
The first three items are strictly necessary to provide a service you asked for, so they do not require consent. Google Ads and Meta Pixel measurement are different: they are off by default and run only after you choose Accept in the banner. You can choose Reject and still use RelayMe. Creator pages never load these advertising tags.
6. Analytics and advertising on our own pages
Our own pages — the home page, pricing, the blog, this page and the terms — use Vercel Web Analytics so we can see how many people visit and which pages they read. It records the page address, the referring site, and coarse device and country information. It sets no cookies, stores no identifier on your device, and does not follow you to other websites.
On our marketing and sign-up pages, we also offer optional marketing measurement. If you accept, the advertising and measurement partners named below may use cookies and similar technologies to measure whether an advert led to a RelayMe sign-up and to improve advertising. Google Ads and Meta Pixel may receive information from your browser such as the page address, device and browser details, IP address, and advertising identifiers or cookies where available. Meta Pixel receives a PageView on our marketing and sign-up pages and a CompleteRegistration event only after a new account is verified following a consented signup attempt in the same browser. We do not send either provider the content of creator pages, sign-in emails, passwords, payment details, or creator-page visitor data. Meta's automatic matching of email addresses and other customer details is off.
You can reject this measurement when the banner appears or withdraw consent at any time with . Rejecting stops future advertising events; it does not affect your account or page. Your browser may retain cookies already set by a partner until you clear them in your browser settings.
Neither Vercel Analytics nor marketing measurement runs on the pages our users publish.If you arrived here by opening someone’s relayme.bio/name page, no third-party advertising or analytics tag of ours ran on it. That is a deliberate line: creator pages carry our own counting and nothing belonging to anyone else.
Google and Meta are the marketing measurement providers on RelayMe's own pages. We will name any additional provider in this policy before activating it.
7. Exporting and sharing what we hold
Page owners can download their own statistics — including the country breakdown described in section 4 — as a spreadsheet file. The export contains totals per country and nothing about individual visitors, because nothing about individual visitors exists to export.
We can also export account records for our own administration and for answering the requests described in section 9. Those exports stay with us and are not shared with anyone else.
8. Why we are allowed to process this
| Purpose | Legal basis |
|---|---|
| Running your account and publishing your page | Contract, Art. 6(1)(b) |
| Sending sign-in links | Contract, Art. 6(1)(b) |
| Taking payment and managing subscriptions | Contract, Art. 6(1)(b) |
| Counting taps so page owners can see what works | Legitimate interests, Art. 6(1)(f) |
| Keeping the service secure and preventing abuse | Legitimate interests, Art. 6(1)(f) |
| Optional marketing measurement on marketing and sign-up pages | Consent, Art. 6(1)(a) |
| Meeting accounting and tax obligations | Legal obligation, Art. 6(1)(c) |
Where we rely on legitimate interests we have weighed those interests against your rights. Tap counting records no personal identifier, which is what makes that balance come out the way it does.
9. Who else is involved
We use these service providers and marketing partners:
| Provider | What they do | Where |
|---|---|---|
| Supabase | Database, authentication, file storage | EU (Frankfurt) |
| Vercel | Website hosting and delivery, and cookieless analytics on our own marketing pages only | US, edge worldwide |
| Authentication when you choose Google sign-in; optional Google Ads measurement on our marketing and sign-up pages after marketing consent. | US, worldwide | |
| Meta | Optional Meta Pixel measurement of our own marketing page views and verified registrations after marketing consent. No Pixel runs on creator pages. | US, worldwide |
| Stripe | Payment processing | EU and US |
| Resend | Sending email | US |
Transfers outside the EEA are covered by the European Commission’s Standard Contractual Clauses, and where applicable the EU–US Data Privacy Framework.
If you give a RelayMe page your email address. Some pages carry a card asking for one. That address belongs to the person whose page it is, not to us — they decide what to send you and they are responsible for it. We store it for them, send you one message to check the address is really yours, and store nothing at all until you click the link in it. Every message includes a way to leave, and leaving deletes the address rather than marking it. RelayMe itself will never email you.
Links that play on a page. A Pro account can set a YouTube, Spotify or SoundCloud link to play where it stands rather than sending you elsewhere. Until you press play, nothing is requested from any of them — the card you see is drawn by us, from the page’s own colours. Press play and the player loads from that company, which is the moment your browser first contacts them and the point at which their own terms and cookies apply, not ours. YouTube is loaded through its no-cookie domain.
Counting a visit. When someone opens a RelayMe page or taps a link, we record the event so the page’s owner can see how it is doing. To avoid counting the same person over and over, we take a one-way hash of their IP address, keep only the hash, and delete it within a few hours. The address itself is never stored, and the hash cannot be turned back into one.
Fonts are served from our own servers, not from a font network, so loading a RelayMe page does not reveal your IP address to any third party for typography.
One exception. Where a link’s own website does not publish an icon, we fall back to Google’s favicon service for that small image. Your browser fetches it directly, so Google receives your IP address for that request. It happens only on pages containing such a link, and only for the icon.
10. How long we keep it
- Account and page data — for as long as your account exists.
- After you delete your account — removed within 30 days, other than anything we must keep for tax or accounting.
- Tap records — 24 months, then deleted.
- Payment records — 5 years from the end of the relevant tax year, as Polish accounting law requires.
11. Your rights
Under the GDPR you may ask us to:
- give you a copy of your data (access)
- correct anything wrong (rectification)
- delete your data (erasure)
- pause processing while a dispute is resolved (restriction)
- hand your data to you or another provider (portability)
- stop processing based on legitimate interests (objection)
Write to hello@relayme.bio. We reply within one month, at no charge unless a request is clearly unfounded or repetitive.
Most of this you can do yourself. Edit or delete any link, page or image from your dashboard, and delete your whole account from the account panel there.
If we get it wrong, you can complain to the Polish supervisory authority: Prezes Urzędu Ochrony Danych Osobowych (UODO), ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl. You may also complain to the authority where you live or work.
12. Security
Access is enforced at the database level by row-level security, so one account cannot read another’s private data even if the application layer were to fail. Card details never reach our servers. Administrative credentials are used only in server-side code and are never exposed to browsers.
No system is perfect. If a breach occurs that is likely to risk your rights, we will notify the supervisory authority within 72 hours and tell you directly where the risk is high.
13. Children
RelayMe is not intended for children under 16 and we do not knowingly create accounts for them. If you believe a child has signed up, write to us and we will delete the account.
14. Changes
If we change this policy in a way that affects you, we will email account holders before it takes effect. The date at the top always shows the current version.
Questions about any of this? hello@relayme.bio — a person reads it.