Privacy Policy

Sendly lets you build a digital card and share it as a link. To do that we store your account, the card you make, and the media you put in it. We do not sell your personal information, we do not show ads on Sendly, and we do not use the contents of your cards to train machine-learning models. The only tracking we run is a count of how many people visit, which our host keeps without cookies, and a check on whether our own advertising is working — a Google cookie for the ads we buy, and a referral code if you arrived through one of our affiliate partners. None of them ever sees what is in a card. We also count how many times a card has been opened, and show that to the person who made it. You can delete a card, or your whole account, whenever you want.

• Your account. An email address and a password, or a Google account. If you sign in with Google, Google passes us your name, email address, and profile picture — nothing more. We never request access to your Gmail, Drive, contacts, photos, or calendar.
• The cards you make. Everything you put in one: your name, the recipient's name, written messages, photos, videos, voice recordings, any other media you upload, and the link to any song you add.
• Delivery details. If you ask us to email a card link, we keep that email address on the card so the link stays recoverable if it gets lost.
• Payment details. Payments run through Stripe. Stripe tells us that a payment succeeded and which email address was used. Your full card number never reaches Sendly and we never store it.

Our hosting provider keeps standard server and security logs — IP address, browser type, and which pages were requested — so we can keep the service running and spot abuse.

We count how many people visit Sendly. We also bring people here two ways — ads we buy on Google, and affiliate partners who link to us and earn a commission when a card is bought. Both of those need to be measured or we are paying for nothing. That count and those two measurements are the only tracking on this site, and this is all of it:

• A count of visitors, kept by our host. Vercel, the company that hosts Sendly, counts how many people visit and which pages they look at. Its script is served from Sendly's own address and sets no cookie. For each page you view it records the time and the page's address, with anything after a question mark or # cut off apart from campaign tags (the utm_… and ref labels a link carries to say where it was posted). With the first page you open, it also records the address of the page that sent you here, as your browser reports it (usually just the site's name), unless that was Sendly itself. From the details every browser sends to every site, it works out a rough location (country, region and city) and your device type and model, operating system and browser, with their versions. To tell one visitor from another without a cookie, Vercel works out a code from your request that resets every day, so one day's visit cannot be linked to the next. We only ever see totals. The count never includes your name, your email address, or anything you wrote or uploaded, and it sends nothing at all from the page a card link opens.
• A Google Ads measurement cookie. Google's measurement script runs on Sendly's own pages and sets a cookie in your browser. If you arrived from one of our ads, that link carried a click tag and the cookie remembers it, so that when a card is published we can tell Google the ad worked. What Google receives is a count, an amount, and a reference code — never your name, never your email address, and nothing you wrote or uploaded.
• An affiliate referral code. If a partner's link brought you here, it carried a referral code. We store that code in a cookie that page scripts cannot read — only our own server can — and it lasts up to a year, so a partner is still credited if you come back later and buy then. If you go on to buy a card, that code is attached to the payment record at Stripe and our server tells Awin, our affiliate network, that a sale happened, so the partner gets paid. What Awin receives is the amount, the currency, the referral code, a reference code for the order, and any discount code you used — never your name, never your email address, and nothing you wrote or uploaded. If no partner link ever brought you here, we send Awin nothing at all.
• Awin's own tag, and a backup image. Awin asks advertisers to run a small script of theirs on their pages, and we do, on the same pages as the Google one and under the same rules. Awin can set its own cookie in your browser to recognise a partner referral. If a partner referred your purchase, the confirmation page tells that script the sale happened, and also loads one small invisible image from Awin saying the same thing — their backup for when the script cannot run. Both carry the same amount, currency and reference code our server already sent. If no partner referred you, neither one fires. Neither loads on the page a card link opens.
• Nothing tracks the page a card link opens. Neither the measurement script nor anything of Awin's loads there, we never set a referral cookie on it, and our visitor count sends nothing from it. The card's link is never sent to Google's ads, to Awin, or into the visitor count. One exception worth stating: if a payment went through but the card was never published, opening the link is what repairs it — and if that purchase came from a partner, finishing it is what finally reports the sale. Nothing about the reading is reported, and nothing about the card leaves us.
• How often a card was opened. Separately from any of the above, we count how many times each card has been opened and when it was last opened, and we show that to the person who made it. It stays with the card, on our own servers. It is not advertising data and it never goes to Google, to Awin, or to anyone else.
• Measuring, not profiling. We do not show ads on Sendly, and we have deliberately switched off Google's ad-personalisation features, so your visit is not used to build an advertising profile or a remarketing list.

Beyond what is listed above we run no analytics. Three tracking scripts from other companies run on this site, and no others: Google's measurement script, Awin's tag, and Vercel's visitor count, which our host serves from Sendly's own address. One further request goes to Awin without a script — the backup image on a partner-referred confirmation page. Neither Google's measurement script nor anything of Awin's loads on the page a card link opens, and the visitor count sends nothing from it. The only other outside code is Google's sign-in helper, which Firebase — the service that runs Sendly accounts — loads so that signing in with Google works. On phones and in Safari it loads on every page, including the page a card link opens; we do not use it to measure anything. One more thing can load, but only when someone asks for it: if a card includes a song and the person opening it taps play, the music service's own player — Spotify, Apple Music, YouTube, SoundCloud, Amazon Music, Tidal, or Deezer — loads inside the card. It comes from that service and follows that service's privacy policy, not ours. It is told which song to play and that the request came from Sendly, not the card's link or anything else in the card, and nothing from it loads until play is tapped. A blocker that blocks Google and Awin stops everything of theirs; a blocker that only stops scripts will let the image through, which is what the image is for. A partner-referred sale is also reported from our own servers, which no blocker can stop — which is exactly why it is worth spelling out above: a referral code, and the fact that a sale happened. Sendly works the same either way.

• Building, storing, and displaying the cards you create.
• Emailing a card link when you ask us to.
• Taking payment for a card and sending you a receipt.
• Answering you when you contact support.
• Keeping accounts secure and investigating abuse of the service.
• Counting how many people visit Sendly and which pages they look at.
• Measuring whether the ads we run for Sendly actually bring anyone here.
• Crediting the partners whose links bring people to Sendly.

We do not sell or rent your personal information, we do not share it for cross-context behavioural advertising, and we do not use the contents of your cards for advertising or to train machine-learning models.

Signing in with Google gives Sendly your name, email address, and profile picture. We use them for one thing: creating and securing your Sendly account so your cards are yours. That data is not sold, not shared with advertisers, and not used to train models.

Sendly's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can withdraw Sendly's access at any time from your Google Account permissions page.

We use a small number of service providers to run Sendly. Each one only handles what it needs to do its job for us.

• Google Firebase — accounts and sign-in, the database your cards live in, and storage for the photos, videos, and recordings you upload.
• Stripe — processing payments.
• Resend — sending card-link emails.
• Vercel — hosting and serving the site, and counting visits to it. The visitor count receives which pages were viewed, with anything after a question mark cut off apart from campaign tags, and never anything from the page a card link opens or from inside a card.
• Google Ads — counting whether the ads we run for Sendly lead to a published card. It receives a count, an amount, and a reference code, and nothing from inside a card.
• Awin — our affiliate network, which pays the partners who link to us. When a partner's link brought you here and you buy a card, our server tells Awin the sale happened, and your browser tells them as well — through their script and through one image they ask us to load. It receives the amount, the currency, the referral code, a reference code for the order and any discount code you used, and nothing from inside a card. Sales by someone no partner link ever referred are never reported to Awin.

We will also disclose information where the law requires it, or where we genuinely need to in order to protect someone's safety or defend our rights.

A published card can be opened by anyone holding its link. We ask search engines not to index card pages, but a link can be forwarded — so treat the link the way you would treat the card itself, and think twice before putting something in a card that you would not want passed along.

Pasting the link into a message shows a picture of the card's cover — the first screen the person opening it sees, names included — and messaging apps such as iMessage, WhatsApp and Messenger may keep their own copy of that picture. A card with a passcode shows a sealed envelope instead, and nothing from inside it.

We keep your account and your cards for as long as your account exists. You can delete any individual card from your dashboard at any time, which removes the card and the media in it.

To delete your account and everything in it, email us at sendlycard@outlook.com from the address on the account. We will delete your account, your cards, and your uploaded media; copies in routine backups clear within 30 days. We may keep payment records for as long as tax and accounting rules require.

Depending on where you live, you may have the right to ask for a copy of the personal information we hold about you, to have it corrected, or to have it erased. Email us and we will help — we do not charge for this and we will not make the service worse for you because you asked.

Sendly is not intended for children under 13, and we do not knowingly collect their personal information. If you believe a child has given us information, email us and we will delete it.

If this policy changes we will post the new version here and update the date at the top. If a change materially affects how we handle your information, we will tell you by email or in the app before it takes effect.

Questions about this policy, or about your data, go to sendlycard@outlook.com. You can also reach us from the support page.