Privacy policy
Last updated: 14 November 2026
1. Controller
Afshin Babaei
Achalmstraße 37
71088 Holzgerlingen
Deutschland
Email: support@yippidi.com
Phone: +49 179 3922979
2. The key points in brief
- You don’t need an account and don’t have to sign up.
- We store your question, the names and your texts after the Yes only in encrypted form and only until your link has expired or been ended. The link itself carries the key to them, in the part after the “#”; when the link is opened, the browser does not send the key to our server. Without the link, we cannot read the content. So that your link is created with your payment and we can email it to you, the content and the key pass through our server once when you buy; we keep the key encrypted only until the email has gone out (section 5, which also explains when a link still carries its content itself).
- We use no tracking, no third-party analytics tools, no advertising and no third-party content (not even Google Fonts). Fonts are hosted on our own server. We only count daily totals ourselves, without cookies and without recognising you (section 3).
- Payment is made via Stripe’s payment page. We never see your card details.
3. Hosting and server logs
The website is served via Cloudflare (Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA). When the site is accessed, Cloudflare processes technically necessary data such as the IP address, time, address accessed (without the part after the “#”), browser identifier and error messages in order to serve the site securely and reliably and to fend off attacks. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in secure operation). A data processing agreement is in place with Cloudflare (Art. 28 GDPR). For transfers to the USA, we rely on the adequacy decision for the EU-US Data Privacy Framework, under which Cloudflare is certified. Our database (purchase and link entries and the encrypted content of the links, Cloudflare D1) is hosted by Cloudflare in the EU. We do not keep our own access logs (server logs). Cloudflare keeps this data only for as long as is necessary to serve the site securely and to fend off attacks, and deletes it at the latest when our contract ends.
Counter without personal data: To see whether the site is found and understood, we count daily totals on our own server: how often the home page was opened, a template was opened, the purchase dialog was opened and “Order with obligation to pay” was tapped, how many purchases were completed, how many links were opened and for how many of them an answer was sent. If you open the site through an address ending in “?v=…” (for example from one of our videos), we count that tag as well, so that we can see which video brings visitors. In this count we store only the day, the kind of step, the tag (if any) and the number – no IP address, no device or user identifier, no time of day and no connection to a purchase or link. If you order after opening the site with a tag, the tag is sent to Stripe with the order and kept there as a note on the payment (section 6); once the payment is taken, we use it to count one purchase for that tag. We set no cookies for this and neither store nor read anything on your device; individual visitors cannot be recognised this way. We recognise automated requests (for example search engines) by the browser identifier of the request and do not count them; none of it is stored. In so far as personal data is processed at all, the legal basis is Art. 6(1)(f) GDPR (legitimate interest in improving our service).
4. Storage on your device
We only store what is strictly necessary for the functions you request (§ 25 Abs. 2 Nr. 2 TDDDG). That is why there is no cookie banner. We do not use statistics, advertising or tracking cookies and do not track you across other sites; a “Do Not Track” signal from your browser therefore makes no difference.
| Name | Type | Purpose | Duration |
|---|---|---|---|
| yippidi.fav, yippidi.custom, yippidi.clang, yippidi.sound, yippidi.klang, yippidi.theme, yippidi.langHint | Local storage | Favourites, drafts of your questions and answers, chosen content language per template, sound setting and sound variant (only if chosen via the address), appearance (light or dark, only if you choose it yourself), language suggestion dismissed | until you delete them |
| yippidi.link-urls | Local storage | Your finished links (they carry the key to the content; links in the previous form carry the question and names themselves), so that you can copy them again under “Inbox” – only on the device on which you created them | until one day after the link expires |
| yippidi.yes-seen | Local storage | The answers to your links that you have already seen (link number and time of the answer, section 5) – so that the “Yes!” badge on “Inbox” does not reappear on every visit | until you delete them (at most 60 entries) |
| yippidi.demo-entitlements, yippidi.demo-links, yippidi.demo-manage, yippidi.test-gate | Local storage | Test mode only: simulated test purchases and test links; during a password-protected test phase, a checksum (never the password itself) so that you don’t have to enter it again every time | until you delete them |
| yippidi.pending | Session storage | Remembers during payment which template you are buying, your order number and your finished link (question and texts encrypted) together with the key to its content, so that the page fetches exactly this link after you return from Stripe | until you return, at the latest until you close the tab |
| yippidi_lang | Cookie | Your language, only if you change it yourself (we then no longer suggest another language) | 6 months |
| __Host-yp_ent | Cookie (HttpOnly) | Your purchases in this browser (so that you can see your links and orders and fetch your link after paying) and a random device number that is only used for protection against abuse (see below), signed, without name or email | 1 year, extended when used, at most 2 years from the first purchase |
| __Host-yp_co | Cookie (HttpOnly) | One-time random value that matches your purchase after you return from Stripe and links the content of your link stored beforehand to your order | 1 hour |
| __cf_bm, cf_clearance, _cfuvid | Cloudflare cookie (only if active) | Protection against bots and attacks: __cf_bm when bot protection is active, cf_clearance after a passed security check, _cfuvid with certain rate-limiting rules. No cross-site tracking. | __cf_bm: 30 minutes without activity; the others depending on the settings at Cloudflare |
Under “My inbox → Delete data on this device” you can remove everything at once as soon as none of your links is running and no order is still open (until then the data stays so you can copy or end the link). You can also delete cookies and site data in your browser at any time and thus object to the storage. Afterwards, you can get your purchases back via the private link in your order confirmation.
Protection against abuse: So that nobody floods our interfaces (purchase, links, contact, withdrawal) with requests, we count how often requests come from an internet address (for IPv6 addresses per connection, i.e. the first 64 bits); where there is a purchase cookie (ordering, fetching and ending a link, “My inbox”), we additionally or instead count per device number from it, and for withdrawals additionally per email address provided (normalised: ignoring upper and lower case, without a “+suffix”, without dots for Gmail) and per order number. For this, we only store the IP address, the email address and the order number as a salted hash, i.e. as a checksum that cannot be reversed without the secret additional value, and delete the counters after 24 hours, and the counters per order number for withdrawals after 7 days (at most three withdrawals per order number and week are possible there; in each case at the latest a few minutes later with our regular deletion run). The legal basis is Art. 6(1)(f) GDPR (legitimate interest in secure operation).
5. Sharing links
When you create a link, we store its content – the question, answer, names, letter text, the texts after the Yes, the character and what it is holding – encrypted in our database (section 3). Only the link itself carries the key to it, in the part after the “#”; we do not store the key (exception: from when you order until the email with your link has been sent, see below). Without the link, we cannot read the stored content either. Whoever opens the link sees this content: their browser fetches the encrypted content from our server using the link’s number (link ID) and only opens it on the device with the key from the link. In doing so, it does not send the key to us, and nothing is stored for this request. In rare cases a link is still created in the previous form, for example if the page was still open in an older version when you ordered or if storing the content failed; links created before the changeover on 11 November 2026 also have this form. In that case the content is contained in the link itself (after the “#”) instead of in our database, and we do not receive it when the link is opened. Please do not pass on the names of third parties if they do not want you to. We process the other person’s name on the basis of Art. 6(1)(f) GDPR (your and our legitimate interest in delivering your question to them as you wish). To ensure that only paid links are sent and that nobody can alter a link, our server gives each link a seal based on a checksum (hash) of the link content. When someone opens the link, their browser asks our server whether the seal and validity are correct; in doing so, it sends the link ID, template, expiry time, seal and, again, only the checksum. None of this is stored (legal basis: Art. 6(1)(b) GDPR, performance of the contract with the sender, and point (f), protection against altered links). When someone taps the envelope open in the opened link (for the love letter: the letter), the browser reports this again in exactly the same way; the first time, we record when the link was delivered (see below).
Each link can be opened for 7 days from when it is created, and you can end it early. For this, we store a random link number for each link, the template, the associated purchase, the time of creation, the expiry date and whether and when you ended it (with the version of the notice you confirmed). The question, answer, names and the texts after the Yes are not part of these entries; they are only held in the encrypted content (see above) and, around the time of the order, in the encrypted draft and in the encrypted link until the email has been sent (see below). When the link is opened, the other person’s browser briefly checks with our server, using this link number, whether the link is still valid, and uses it to fetch the encrypted content. Within the content, the question, answer, letter text and the texts after the Yes are additionally encrypted with a second key. We do not store this key either: our server calculates it from the link number and a secret master key. When you order, it only gives it to your browser (so that it can encrypt the content), and otherwise only releases it when someone taps the envelope. If a link is reported to us as a violation, we receive the key to the content with it and can read the content, including the additionally encrypted texts – but only as long as it is still stored (a link in the previous form also after that). The legal basis is Art. 6(1)(b) GDPR (contract). We delete the encrypted content once the link has expired or been ended – by you, a withdrawal, a refund or a chargeback – at the latest with our next regular deletion run. We delete the other entries 30 days after the link expires. So that no paid link is issued twice, we also record for each purchase which link numbers were created from it (without content); this forms part of the purchase records and is deleted together with them (section 6). For this purpose, we store a check value for one hour so that your browser gets exactly the link of your order after you pay.
Your link with your payment and by email: So that your link is created even if you close the page after paying, and so that we can email it to you, your browser sends the finished content of the link to our server when you click “Order with obligation to pay” – the question, answer, letter text and the texts after the Yes already encrypted, with only what the envelope shows readable (the names, the character and what it is holding) – together with the key that the link will later carry and the language in which the link should open. We store both encrypted in our database (section 3), create your link from them after the order confirmation – in doing so, we lock the content with the key from the link and store it in that form (see above) –, only then charge the amount and delete the draft afterwards; if the order is cancelled, we delete it immediately, and if no purchase is made, after 2 days. If the content did not arrive before payment, your browser sends it and the key again after you return, with the content encrypted in the same way. We keep the finished link encrypted until the email to you has been sent and then delete it, at the latest when the link expires; after that we only record whether and when the email was sent, and delete this too 30 days after the link expires. As long as we hold the key from the link in this way – in the draft and in the link we keep for the email –, we could technically open the content; after that, only if someone sends us the link, for example in a report. The email is sent via Mailjet (section 7) to the email address you entered at Stripe; Mailjet thereby also processes the link and with it the key to the content (for a link in the previous form: the names readable in it). On the page after your purchase we show you the address only in shortened form (a few characters before the @ and the domain). We do not decrypt the encrypted texts for this. For each order, we also record when it was checked, whether and when the amount was charged or the reservation released (with the reason), whether the link was shown to you on the page, and a checksum of your browser’s order number so that only your browser can fetch the link – without content; this forms part of the purchase records (section 6). If your link never reached you (never shown, email undeliverable, not delivered), we automatically refund the full price and notify our mailbox with the order number. The legal basis is Art. 6(1)(b) GDPR (contract).
Delivery: With this link number, we also record when the link was first delivered, i.e. when someone opened it and tapped the envelope open (for the love letter: the letter). Only this time is stored for it – no device, no IP address and not who it was. Automatic previews by messengers do not trigger this. The purpose is to prove that we have performed our service (withdrawal, chargebacks); the legal basis is Art. 6(1)(b) GDPR (contract with the sender) and point (f) (legitimate interest in being able to substantiate claims). We do not show the time to the sender; we only tell them if they withdraw from a purchase and the right of withdrawal has therefore already expired. If a withdrawal is received, the time is also included in the notice to our mailbox so that we can process the withdrawal (section 7). It is deleted three years after the end of the year in which the link was delivered (regular limitation period).
Answer: After Yes, the opened link shows a button for sending the answer next to the poster (“Send off your answer”, or with the sender’s name “Send your answer to …”). Tapping it is voluntary. Only when someone taps it does the browser report the answer to our server, together with the number of No attempts before it and – for the Date Ticket – the numbers of the three options tapped there before Yes (food, afterwards, when); before that, nothing is reported and nothing is stored, not even a No. With the link number, we then store the time, that number and, for the Date Ticket, the three option numbers – no free text, no device, no IP address and not who it was. The latest answer always counts: if the link is opened again and an answer is sent again, it replaces the previous one. If the report comes from a browser that holds the purchase cookie for this link (the sender trying out their own link), we do not store it. We show the time, the number and, for the Date Ticket, the three chosen options to the sender under “My inbox”. The legal basis is Art. 6(1)(b) GDPR (contract with the sender: they learn the answer to their question) and point (f) (their and our legitimate interest in this). The answer is deleted together with the other entries for the link, 30 days after it expires.
There is a private link for every purchase. It contains the purchase number and a secret key calculated from it, which we do not store. When you open it, we check the key and add the purchase to the purchase cookie in this browser.
Share menu and WhatsApp: For sending, Yippidi uses your phone’s share menu or a WhatsApp link. In doing so, we do not access WhatsApp, your contacts or chats, and we do not find out to whom you send something. With the share menu, your phone passes the prepared text and the link directly to the app you select. If you tap “WhatsApp”, wa.me opens, a service of WhatsApp Ireland Limited (Meta); the prepared text including the link is transmitted to WhatsApp, and WhatsApp’s privacy policy applies to any further processing. If you don’t want to use WhatsApp, simply copy the link and send it however you like.
6. Payment
Payments are processed by Stripe Payments Europe, Ltd. (1 Grand Canal Street Lower, Dublin 2, Ireland). On Stripe’s payment page, you enter your payment details and email address directly with Stripe. If you pay with PayPal, you log in to PayPal for this; PayPal (Europe) S.à r.l. et Cie, S.C.A. (22–24 Boulevard Royal, L-2449 Luxembourg) processes your data as an independent controller. Stripe processes your payment data partly on our behalf and partly for its own purposes (e.g. fraud prevention, anti-money laundering checks) as an independent controller; in this context, data may be transferred to Stripe, LLC in the USA (EU-US Data Privacy Framework or standard contractual clauses). Privacy at Stripe: stripe.com/de/privacy. We receive from Stripe the purchase number, product, amount, payment status and the email address for the purchase confirmation. With each purchase, we pass Stripe the product, the template chosen, the language, the currency and the version and time of your consent to the immediate start, and later also when your link was created and when it was delivered; Stripe stores these details with the payment so that we can also substantiate the purchase in the event of a withdrawal or chargeback (Art. 6(1)(b) and (f) GDPR). There, they are kept for as long as the payment itself (Stripe keeps payments for the statutory periods); the deletion periods below apply to our own database. The legal basis is Art. 6(1)(b) GDPR (contract) and point (c) (retention obligations under commercial and tax law). We keep our purchase records (purchase number, product, amount, time of your consent to the immediate start, link numbers created) for as long as the law requires: accounting vouchers and copies of invoices 8 years, books and records 10 years, business letters 6 years, each counted from the end of the calendar year; after that, we delete them. In our database, an automatic deletion run takes care of this: the note that the confirmation was sent after 6 years, the purchase together with the order history and the link numbers created from it after 10 years; cancelled orders for which nothing was charged are deleted after just 3 years, because by then any claims are time-barred (Art. 6(1)(f) GDPR). This also applies to orders whose reservation we have released (terms, § 3 para. 2). We also ask Stripe which country your card or PayPal account is from, to check whether we sell to your country (terms, § 3 para. 6); we do not store the country. If PayPal does not tell us a country, the country you order from counts: when you click “Order with obligation to pay”, we pass Stripe the country code that Cloudflare derives from your IP address (e.g. “DE”); we do not pass on the IP address itself (Art. 6(1)(b) GDPR). To prevent abuse, Stripe also gives us an identifier of your card or PayPal account (never the card number). Of this, we only store a salted hash in order to limit orders with the same card or PayPal account to 5 within 24 hours, and delete it after 2 days. If you withdraw from a purchase, we keep it until 30 days after the withdrawal in order to detect unusually frequent withdrawals with the same card or PayPal account; if it has already been deleted, we create it again for this purpose from the identifier held by Stripe. If a purchase is charged back or the bank reports a payment as fraud, we put salted hashes of this identifier and of the email address of this purchase on a block list for 2 years; we do the same if we have found fraud or abuse after a personal review. We check every order against the block list (terms, § 3 para. 6). We check the sales area, the card limit and the block list automatically. If we do not accept an order for this reason – or cancel it because your link could not be created (terms, § 3 para. 2) –, we send you a short email with the reason to the address from the payment page (sent via Mailjet, section 7); for this we only store the number of the payment session, the reason and the times, and delete them after 30 days (Art. 6(1)(b) GDPR). If your order was declined, write to us – we will review it personally (Art. 22(3) GDPR). To detect abuse, we personally review unusual accumulations of withdrawals and also use Stripe’s overview, which groups payments made with the same card or email address. For this, we count how often withdrawals were made in the last 30 days with the same email address or the same card or PayPal account (only as a checksum). If, after a personal review, we consider such an accumulation harmless, we note this for that email address or checksum; the note is deleted as soon as no further withdrawal is added for 30 days. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in preventing fraud and abuse).
Sales area notice and currency: So that you do not find out only after paying that we do not sell to your country, the page asks our server when it loads whether you are within our sales area. For this, Cloudflare derives only the country from your IP address; our server answers your browser only with yes or no. If the answer is no, a notice appears before the purchase dialog opens. We store neither the country nor the IP address for this. The legal basis is Art. 6(1)(f) GDPR (our interest and yours in avoiding orders that cannot go through). Which currency you are shown is decided by your browser itself, based on the time zone of your device; the time zone is not transmitted to us.
7. Confirmation email, emails and reports
Confirmation of your purchase: As soon as the content of your link has reached us, we send you an order confirmation to the email address you entered on Stripe’s payment page – with this, we accept your order (terms, § 3 para. 2). It contains your order, the price, the notice about your right of withdrawal, your private link and our Terms. We are legally obliged to do this (§ 312f BGB); the legal basis is Art. 6(1)(b) and (c) GDPR. We need your email address for the purchase because we have to send you the order confirmation; without it, no purchase is possible. To send it, we use Mailjet SAS (Paris, France) as a processor. Mailjet stores the data in data centres in the EU; for its customer support, Mailjet also uses sub-processors in the USA (e.g. Atlassian and Zendesk), safeguarded by the EU-US Data Privacy Framework or standard contractual clauses. We measure neither whether you open the email nor whether you click on links. For the confirmation and the email with your link, we do not store your email address in our own database but fetch it from Stripe for each sending. We only store it if you withdraw (see below) and as a checksum on the block list (section 6). We only store whether and when the confirmation was sent. We then send you the finished link in a separate email to the same address, in the same way (section 5). If an email to you bounces (e.g. because of a typo in the address), Mailjet tells us so with the email’s ID and the error; we then only note that the email with the link did not arrive, so that we can refund you (Art. 6(1)(b) GDPR) – we do not store your address in this case either. Mailjet keeps the sending data (recipient, time, delivery status) only for as long as is necessary for sending and troubleshooting, and deletes it at the latest when our contract ends.
If you write to us or report a link, we process your message and contact details in order to handle it (Art. 6(1)(b) or (f) GDPR) and delete them when they are no longer needed. If you report a link, we open it to check the report and block it if it breaks the rules; with the reported link, we can read the content, including the additionally encrypted texts – if the content is held by us, only as long as it is still stored (section 5). Our mailbox is hosted by STRATO GmbH (Berlin), with which we have a data processing agreement.
Contact form: If you write to us via the contact form, we send your email address, your message and – if provided – your name by email to our mailbox (sent via Mailjet, see above). We store none of this in our database, and we do not send an automatic reply. To protect against abuse, we count how often messages come from an internet address; for this, we only store the IP address as a salted hash and delete the counter after 24 hours at the latest. The legal basis is Art. 6(1)(b) GDPR if your message concerns a purchase, otherwise point (f) (answering your enquiry). We delete the message once it has been dealt with and there is no obligation to retain it.
Withdraw from contract: If you declare a withdrawal via “Withdraw from contract here”, we store your name, the order number, your email address, the language and the time of receipt, and send you an acknowledgement of receipt by email (sent via Mailjet). We are legally obliged to do this (§ 356a BGB); the legal basis is Art. 6(1)(c) GDPR, and additionally point (f) for the purpose of proof. If the withdrawal comes from the browser in which you made the purchase, we match the order number you provided against your purchase cookie; if it comes from another device, we match the order number and email address against the payment details at Stripe. If they match, we immediately end any links from this purchase that have not yet been delivered, so that they are no longer delivered after the withdrawal, and cancel an order that is still in progress (Art. 6(1)(b) GDPR). If the email address does not match the payment, we do not stop anything and tell you so right away on the page and in the confirmation of receipt, so that you can send the withdrawal again with the matching address. We forward your withdrawal with these details and – if available – the time of delivery by email to our mailbox so that we can process it (sent via Mailjet, mailbox at STRATO). To protect against abuse, we count withdrawals per internet address, per email address and per order number, all only as a salted hash (section 4). We do not store an order number that does not exist and do not send an email about it; if many of them come from one internet address, we block that address for one hour. We delete these details three years after receipt (standard limitation period).
8. Your rights
Right to object (Art. 21 GDPR): Where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR, e.g. protection against abuse and against altered links), you can object to this at any time on grounds relating to your particular situation. To do so, write to us at support@yippidi.com.
You have the right of access, rectification, erasure, restriction of processing, data portability and objection (Art. 15–21 GDPR). You can lodge a complaint with a data protection supervisory authority, e.g. the authority responsible for our place of business: the State Commissioner for Data Protection and Freedom of Information Baden-Württemberg (Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg), Lautenschlagerstraße 20, 70173 Stuttgart (baden-wuerttemberg.datenschutz.de).
9. Notes for individual countries
New Zealand: If you buy from New Zealand, the Privacy Act 2020 applies in addition. Afshin Babaei is then also your privacy officer, reachable at support@yippidi.com. You can ask for access to your data and for its correction. If you are not satisfied with our answer, you can complain to the New Zealand Privacy Commissioner (privacy.org.nz).
USA, in particular California: We do not sell personal data and do not share it for advertising. No third parties collect data on our site about your behaviour over time or across different websites; how we handle “Do Not Track” signals is described in section 4. Which data we process and with whom we share it is set out in sections 3 to 7. To request access, correction or deletion, email us at support@yippidi.com.
Children: Yippidi is not directed at children under 13, and we do not knowingly collect data from them. If we learn that a child under 13 has given us data, we delete it.
10. Changes to this privacy policy
If we change this privacy policy, we publish the new version on this page and update the date at the top (“Last updated”). You will always find the current version here.