Privacy Policy
Effective Date: October 4, 2026
Thank you for using FinalSaying. We value your privacy and are committed to protecting your personal data. This Privacy Policy explains who we are, what information we collect, how we use and safeguard it, and your rights. FinalSaying is designed to let you write encrypted messages that will be delivered to your chosen recipients after your death, and we take privacy very seriously in providing this service.
Who We Are
FinalSaying (referred to as "we" or "us" in this Policy) is a personal project operated by an individual developer based in Germany. Because we operate in the European Union, we adhere to EU data protection laws, including the General Data Protection Regulation (GDPR). FinalSaying allows users (referred to as "you") to create secure, encrypted messages and have them delivered at a later time (for example, after the user's passing).
As an individually-run service, we strive to be transparent and respectful of your privacy. This Policy applies when you use the FinalSaying website or service.
What Data We Collect
We only collect the minimum personal information necessary to provide the FinalSaying service. Here is what we collect and what we do NOT collect:
- Google Account Information: When you sign up or log in via Google Sign-In, we receive your name and email address from your Google account. This is used to create and manage your FinalSaying account (so we know who you are and can authenticate you). We do not collect your Google password or any other Google account data beyond your name and email.
- Your Messages: The text and subject line of the messages you write on FinalSaying are collected and stored encrypted at rest in our database, so it cannot be read directly from the database without the encryption key. We decrypt it when it needs to be delivered to your designated recipient(s), and when you view or edit it yourself.
- Your Attachments: Files you attach (such as photos) are handled differently from message text, and we want to be precise about it. They are stored as ordinary files in our object storage (DigitalOcean Spaces), not encrypted by us, at long random web addresses that cannot realistically be guessed. Anyone who has the address of a file can open it without signing in, because those addresses are what allow the files to be shown to you in your dashboard and to your recipients when a message is delivered. Treat an attachment link like a password: do not share it. If you need a file to stay strictly private, consider whether a photo is the right way to send it.
- Recipients' Contact Information: If you provide contact details for the people who should receive your messages (for example, an email address for an intended recipient, or a phone number for WhatsApp delivery), we collect and store that information. We treat this data as confidential. It is stored in our database protected by access controls and our database provider's encryption at rest, but unlike your message text it is not encrypted with our own message key, because we need to read it to deliver your messages. We use it solely to deliver your messages to those recipients at the appropriate time. (Please ensure you have the right to share any third-party contact information with us.)
- Your Phone Number (Premium, optional): If you add your own phone number, we store it, unencrypted by us, and use it only to send you WhatsApp check-in reminders through Twilio.
- Check-in and Delivery Records: We store your check-in frequency, the dates of your check-ins and reminders, whether you have been marked as deceased, and the delivery status of each message (including when a recipient first opened it). We need these records to run the check-in sequence and to know what has been delivered.
- Payment Information: FinalSaying offers premium features available through a one-time payment. If you choose to make a payment, this will be handled by our third-party payment processor (Stripe). We do not collect or store your sensitive payment details (such as credit card numbers) on our servers. Stripe will collect payment information securely for processing transactions. We may receive and store basic information from Stripe, such as your premium status and payment confirmation, to know that your payment was processed. We do not receive your full credit card details or bank information.
- Customer Support Communications: If you contact us via email (for example, at our support email address), we will collect whatever information you choose to provide in that communication. This likely includes your email address and the content of your message. We will use this information to respond to your inquiry or request and to resolve any issues you reported.
Cookies: Strictly Necessary: We set two strictly necessary cookies, without which the site cannot work: a session cookie that keeps you signed in after you authenticate (the session itself is stored in our own database, not in the cookie), and a CSRF token cookie that protects you against a class of attack in which another website submits requests as you. We also store your answer to the cookie banner described below on your own device, so that we do not ask you again. These are essential to the service you asked for, or are a record of your own choice; under EU rules, strictly necessary cookies do not require consent. None of them is shared with anyone. You can delete them at any time through your browser; doing so will sign you out and make the banner reappear.
Cookies: Analytics, Only If You Accept: We use Google Analytics 4 to understand which pages people find useful — how visitors arrive, which articles they read, and how far down they get. We use it to improve what we write, not to profile individuals, and we do not use it for advertising. Nothing loads until you agree. When you first visit, a banner asks whether you accept analytics cookies. Until you choose "Accept", no analytics script is downloaded, no analytics cookie is set, and no data about your visit is sent to Google. If you choose "Reject", or simply ignore the banner, that remains true for your entire visit. The site works identically either way.
If you accept, Google Analytics sets cookies (named _ga and _ga_<id>) that hold a randomly generated identifier. That identifier lets us recognise a returning browser, so that a person who reads three pages is counted once rather than three times. We enable IP anonymisation, so your IP address is truncated before it is stored. These cookies expire after up to two years, and analytics data is retained for 14 months. What we measure, if you accept: the pages you view, roughly how far you scroll, which sections of an article hold your attention, how long you stay, and whether you click a link that leads off the site. This is aggregated in Google's reporting; we do not attempt to identify individual readers, and we never connect analytics data to the content of your messages.
Who receives it: Google Ireland Limited, and its parent Google LLC in the United States, act as our analytics provider. Data may be transferred outside the EU; Google relies on the European Commission's Standard Contractual Clauses and the EU–US Data Privacy Framework for those transfers. Google's own description is at policies.google.com/privacy. Legal basis: your consent, under Article 6(1)(a) GDPR and § 25(1) TTDSG. You can withdraw it at any time using the "Cookie settings" link in the footer; withdrawing deletes the analytics cookies from your browser and stops any further collection. Withdrawal does not affect the lawfulness of what was collected beforehand. We use no advertising cookies, no tracking pixels, and no Facebook pixel or similar tools, and we do not track you across other websites.
Server Logs: We keep server logs, and they do contain some personal data. Specifically: our web server records standard access logs (including your IP address, the page requested, and your browser's user-agent string), our application records your IP address when an error occurs and when an administrative action is taken, and we count requests per IP address in order to rate-limit abusive traffic. We do not use any of this to build a profile of you, to analyse your behaviour, or for marketing; it exists to keep the service running securely and to let us debug faults. The legal basis is our legitimate interest in the security and reliability of the service. These logs are kept only as long as they are useful for that purpose and are not combined with your message content.
No Advertising Data Collected: We do not collect any data for advertising or marketing purposes. We do not show ads in our service, and therefore we don't collect data such as ad preferences or advertising IDs. The analytics described above are configured for measurement only: advertising storage, advertising personalisation and ad-related identifiers are switched off, and analytics data is never used to build an advertising profile of you. You will also not receive any marketing emails or newsletters from us — we will only contact you for service-related reasons (e.g. important updates to the service or your account, if ever necessary).
In summary, we collect the information you provide directly (your account info and message content), the bare minimum technical data to make the service work, and — only if you accept the analytics cookies described above — aggregated statistics about how the site is used. We deliberately avoid collecting any extra personal data that is not needed.
How We Use Your Data
We use the personal data we collect only to provide and improve the FinalSaying service and to fulfill your requests. Specifically:
- Providing the Service: We use your Google account name and email to create your FinalSaying account and let you log in securely. Your email may be used to identify your account and, if needed, to communicate with you about service-related matters (for example, if there is an important update or if we need to inform you of something critical about your account). We use the information about your payment status (from Stripe) to enable access to premium features.
- Storing Your Messages: We use (store) the content you write (messages and attachments) in order to carry out the core purpose of FinalSaying — which is to hold these messages until the appropriate time and then deliver them to your chosen recipients. The storage is encrypted, as noted, and the content is essentially "locked away" until it's time to send it. We do not otherwise read or use the content of your messages for any purpose other than storing it and sending it to the intended recipient when the time comes.
- Delivering Messages to Recipients: Delivery is triggered only by the check-in mechanism: if you do not respond to a check-in email and the reminders that follow it (17 days in total, as described on our Security page), we treat you as having passed away. We do not receive or verify death notifications. We then decrypt the message content and use the recipient contact information you provided to deliver the message. If the delivery is via email, we send an email through our email provider (Resend) from noreply@finalsaying.com to that recipient with your message. If the delivery is via WhatsApp, we send a WhatsApp notification through Twilio to the recipient's phone number; it names you and the recipient and contains a private link, and the message text itself is read on finalsaying.com rather than sent through WhatsApp. Your data is used strictly to ensure your final messages reach the people you intended, in the manner you specified.
- Payments and Premium Access: If you purchase premium access, we use your data to manage your account. For example, we may use your email to send you a receipt or confirmation of payment (though Stripe usually handles receipts). We also rely on Stripe to inform us if your payment was successful, so we can grant access to premium features accordingly. We only use this information to manage the services you are paying for.
- Customer Support and Communication: If you reach out to us via the contact email for help or with questions, we will use your email address and the information you provided to respond to you. We will only use this information to assist you and resolve your support issue. We won't use support inquiry data for any other purpose.
- Service Improvements: Internally, we review the usage of our service in general terms (e.g. how many users we have, or generic trends). If you have accepted analytics cookies, we also use the aggregated Google Analytics reports described above to see which pages and articles are useful and which are not, so that we can improve them. Beyond that, the data we look at is non-personal or aggregated: for example, we might keep track of how many messages in total are being stored (without reading them) or note if email deliveries succeed or fail to improve reliability. We never use the content of your messages, your attachments or your recipients' details for analytics, and analytics is never applied to your account content — it covers site usage only.
- Legal Compliance: If ever required by law (for instance, to comply with a valid court order or legal obligation), we may have to use or disclose certain data. This is not a routine use of data, but we mention it here for completeness. Unless we are prohibited from doing so, we would inform you if we ever had to disclose your information for legal reasons.
What We Do Not Do: We do not use your personal data for advertising or marketing, and we do not build a profile of you as an individual. We do not sell or rent your information to anyone. We do not send you promotional communications. We do not use automated decision-making or profiling that has legal or significant effects on you. The one measurement we do carry out — Google Analytics, and only with your consent — is described under "Cookies" above; it reports aggregated site usage and is not linked to your account or to what you have written. All other processing of your data is related directly to the service you have signed up for.
Emails We Send You (and How to Make Sure You Receive Them)
We use your email address to operate the service itself, not to market to you. You will receive check-in requests at the interval you choose, reminder emails if you do not respond, and occasional service messages about your account. Your designated recipients will receive your final messages by email when the conditions for delivery are met.
Addresses we send from:
- noreply@finalsaying.com — all automated mail: check-in requests, reminders, and the final messages delivered to your recipients.
- contact@finalsaying.com — support replies and any direct correspondence with us.
Please add both addresses to your email address book or contacts (sometimes called a safe-sender list or allowlist), and mark our messages as "not spam" if you ever find one in a spam or junk folder. This matters more here than with an ordinary service: FinalSaying decides whether to deliver your messages based on whether you respond to our check-in emails. If those emails are filtered and you never see them, the service may treat your silence as your passing. Signing in to your dashboard also counts as a check-in, so it is a reliable fallback. Where appropriate, consider telling your recipients that they may one day receive a message from noreply@finalsaying.com, and asking them to add it to their own contacts, so they do not mistake it for spam.
WhatsApp: if you are on Premium and add a phone number, WhatsApp check-in reminders come from our WhatsApp Business sender through Twilio. WhatsApp and Twilio decide whether business messages are delivered and may filter, delay or block them, so treat WhatsApp as a backup to email, never a replacement.
We cannot control spam filters, email providers or WhatsApp. Section 16 of our Terms explains the limits of what we can guarantee about delivery.
Legal Bases for Processing (GDPR)
For users in the European Union (and similar jurisdictions), we need to explain the legal grounds on which we process your personal data under the GDPR:
- Performance of a Contract (Article 6(1)(b) GDPR): Most of what we do with your data, such as running your account, storing your messages, sending you check-in emails and reminders, delivering your messages and handling your premium purchase, is necessary to provide the service you signed up for under our Terms.
- Consent: By signing up for FinalSaying and providing your information, you are giving us consent to process your personal data for the purposes described above. For example, you consent to us storing your name and email by using Google Sign-In, and you consent to us processing the sensitive content you input (messages, attachments, recipient info) in order to carry out the service. You can withdraw your consent at any time (see "Your Rights" below), but note that if you withdraw consent for essential data, we may not be able to continue providing the service. Consent is also the basis for the analytics cookies described under "Cookies" above, under Article 6(1)(a) GDPR and § 25(1) TTDSG; that consent is separate, entirely optional, and withdrawing it through the "Cookie settings" link in the footer has no effect on your account or on the delivery of your messages.
- Legitimate Interest: In certain cases, we rely on legitimate interests as our legal basis. Our legitimate interest is in operating a secure and reliable service that delivers users' final messages as intended. For instance, it is in our legitimate interest (and yours as well) that we securely store your messages and deliver them to recipients when the time comes. We also have a legitimate interest in using certain data to maintain the service (e.g., using your email to notify you of critical account issues, or using minimal payment information to manage premium access). When we process data based on legitimate interests, we ensure that this does not override your rights and freedoms – in other words, we only use data in ways you would reasonably expect when using FinalSaying.
In all cases, we handle your data in a manner that is compliant with GDPR and other applicable laws. If we ever need to process your data for a new purpose not described in this Policy, we will seek your consent or inform you of the new legal basis as required.
Data Sharing and Third-Party Services
We do not sell your data to anyone. We only share your information with a few trusted third-party service providers as necessary to operate FinalSaying. These providers are bound to handle your data securely and only for the purposes of providing their services to us (not for their own use). Here are the third parties we work with and what for:
- Google (Google LLC) – Authentication: We use Google Sign-In to allow you to log in to FinalSaying easily. When you use Google Sign-In, Google confirms your identity to us and shares your basic account info (name, email). We use that to log you in. Google may independently record the fact that you used Google to authenticate with our service (this could include logging your IP address or device info on their side, as part of their security measures). This data is handled according to Google's privacy policy. We do not send any of your FinalSaying data back to Google aside from the authentication request. In short, Google helps verify you, and we trust Google as a secure identity provider.
- Google (Google Ireland Limited, and Google LLC) – Analytics, only with your consent: If, and only if, you accept analytics cookies in the banner, we use Google Analytics 4 to measure how the site is used. In that case Google receives, from your browser, the pages you view on FinalSaying, your truncated (anonymised) IP address, your approximate location derived from it, your browser and device type, and the engagement events described under "Cookies" above, together with the random identifier stored in the
_gacookies. Google Ireland Limited is our provider for visitors in Europe; its parent Google LLC is in the United States, so data may be transferred outside the EU, and Google relies on the European Commission's Standard Contractual Clauses and the EU–US Data Privacy Framework for those transfers. We never send Google your message content, your attachments, your recipients' details or anything that identifies your account. If you reject the banner or ignore it, none of this happens: no script is loaded and no request reaches Google. You can withdraw your consent at any time from the "Cookie settings" link in the footer. - Stripe (Stripe, Inc.) – Payments: If you subscribe or make payments on FinalSaying, we use Stripe to process those payments. When you enter payment information (like your credit card details) during a purchase, you do so via Stripe's secure checkout forms. That information goes directly to Stripe; we do not see or store your card number or bank info. Stripe will provide us with data like your name, email, and whether the payment was successful, as well as possibly the last four digits of your card or an expiration date (for reference and receipts). We may also send Stripe your user identifier or email to tie the payment to your account. Stripe might log transaction details (such as your IP at time of payment or a device identifier) to comply with anti-fraud and legal obligations on their side. Stripe is a GDPR-compliant company and will handle your data according to their privacy policy. We only use Stripe to ensure we can securely accept payments and manage subscriptions – no payment data is used outside of that purpose.
- Resend (Resend, Inc.) – Email Delivery: Resend is a third-party email sending service for developers. We use Resend to send every automated email from FinalSaying, all from noreply@finalsaying.com: your check-in requests and reminder emails, and the final messages you want delivered via email to your recipients. This means that when an email needs to be sent, its content is transmitted to Resend's system: for check-ins, your name, email address and check-in link; for a final message, the recipient's email address, the sender name you chose, the subject and body of the message, and any photos attached to it. Resend then delivers the email to the recipient's mail server. Resend may temporarily log information about email transactions – such as when the email was sent, whether it was delivered successfully, opens or bounces, and possibly the IP addresses involved in sending/receiving – as part of their service monitoring. These logs help ensure the email was delivered and help with troubleshooting. We only send the necessary information to Resend for sending the email (we do not give them any data unrelated to the email being sent). All content sent through Resend is handled under their security measures. We trust Resend as a privacy-conscious service (they advertise GDPR compliance and strong data protection). The emails sent via Resend will, of course, contain the message content you wrote (decrypted at send-time so the recipient can read it). Resend does not have the ability to decrypt anything that wasn't already in plaintext when we handed it to them (we only decrypt right when sending). They act purely as a conduit to deliver the message.
- DigitalOcean (DigitalOcean, LLC) – Hosting and File Storage: Our servers, our database and our attachment storage all run on DigitalOcean infrastructure, in a data centre in Frankfurt, Germany. This means DigitalOcean holds, on our behalf, everything the service stores: your account details, your encrypted message text, your unencrypted attachments, and our server logs. DigitalOcean does not use this data for its own purposes; it acts as our infrastructure provider. This was missing from an earlier version of this policy, which was an oversight on our part rather than a change in how the service works.
- Twilio (Twilio, Inc.) – WhatsApp Messages: We use Twilio's WhatsApp API for two things: WhatsApp check-in reminders to you (Premium, if you added your phone number), and WhatsApp notifications to recipients of a final message. For reminders, Twilio receives your phone number and your name. For recipient notifications, Twilio receives the recipient's phone number, the recipient's name, the sender name you chose, and a private link to the message on finalsaying.com. Your message text is not sent to Twilio or WhatsApp; the recipient reads it on our website. Twilio passes these messages to WhatsApp (operated by Meta), which delivers them. Twilio and WhatsApp log transactional details such as the phone number, the time the message was sent and its delivery status. Twilio maintains its own privacy and security practices and is a reputable provider (also GDPR-compliant). We only use Twilio so that we can fulfill the WhatsApp delivery feature – we do not share any other data with Twilio beyond what is required to send the message.
In addition to the above, these general principles apply to our use of third parties:
- Necessary Sharing Only: We only share your data with the above providers for the specific purposes described. We do not share your personal information with any other third parties or individuals, unless it is required to carry out your requests or unless we are required by law (for example, responding to a lawful subpoena – which is rare and would be handled with care).
- No Third-Party Advertising or Marketing: We do not share, rent, or sell your information to advertisers or marketing companies. None of the limited data sharing we do is for commercial advertising purposes; it is all about providing the core service to you, or — for analytics, with your consent — about understanding which pages are worth keeping.
- Contractual Protections: We have agreements (to the extent applicable for a small project like this) with these service providers that require them to protect your data. For instance, using services like Google, Stripe, Resend, and Twilio implies agreement to their terms which include commitments to privacy and data protection. They are data processors or service providers for us, and they are only allowed to use your data to provide services to FinalSaying, not for their own independent use.
- International Data Transfers: Some of our third-party providers are based outside the EU (for example, Google, Stripe, Twilio, and Resend are U.S.-based companies, though they may have EU servers). This means your data might be transferred to or processed on servers located in the United States or other countries outside the European Economic Area. When we transfer data to these providers, we rely on legal mechanisms to ensure adequate data protection, such as the European Commission's Standard Contractual Clauses or the providers' certifications and compliance with GDPR. We only work with providers that we believe have strong data protection standards. By using FinalSaying, and specifically by opting to use features that involve these third parties, you understand that your data may be transferred to these services as needed to operate. We take steps to ensure any such transfer is done securely and in compliance with applicable laws.
In summary, your personal data is never shared arbitrarily – it is only passed along to trusted partners to perform essential functions like authentication, payment, or message delivery, or — where you have accepted analytics cookies — to measure how the site is used. We do not allow any third party to use your data for their own marketing or purposes not authorized by us and you.
Information for Recipients of a Message
If you have received a message through FinalSaying, you are reading this because someone else gave us your contact details. You never signed up with us, so you are owed an explanation of how we come to hold your data. This section is our notice to you under Article 14 GDPR.
- What we hold and where it came from: your name, and the email address or phone number needed to reach you. We did not obtain these from a public source or buy them from anyone; they were entered by the FinalSaying user who wrote you a message, on the basis that they knew you and wanted you to receive it.
- Why we hold it: solely to deliver that person's message to you when the conditions for delivery are met. We do not market to you, profile you, or pass your details to anyone other than the providers who carry the message (see above).
- Our legal basis: our legitimate interest, and that of the person who wrote to you, in carrying out their clearly expressed wish that you receive their words. We balanced this against your privacy: the data we hold is minimal, it is used for one purpose, and you can ask us to erase it.
- If a message is delivered through the web link: we record the moment it is first opened, so that we and the sender's account can tell whether the message reached you. We do not record your location, and we do not link your browsing to your identity. The page will show you the same cookie banner as any other visitor: if, and only if, you accept it, the analytics described under "Cookies" above apply to your visit as they would to anyone else's. If you reject it or ignore it, nothing beyond the opening timestamp is recorded.
- Your rights: you have the same rights as our own users, set out under "Your Rights Under GDPR" below, including the right to obtain a copy of what we hold about you, to have it corrected, to object to our holding it, and to have it erased. Write to contact@finalsaying.com and we will act on it. Asking us to erase your details means any message still waiting for you will not be delivered, and we will tell you before we act if that is the case.
Data Security
We understand that the data you entrust to FinalSaying is highly sensitive (personal messages, possibly final words, attachments, etc.). We take several measures to protect your data:
- Encryption of Message Text: The text of your messages is encrypted at rest in our database, so someone who obtained a copy of the database could not read it without the encryption key. Decryption happens when the message is delivered and when you view or edit it yourself.
- Attachments Are Not Encrypted by Us: As explained above, attached files are stored unencrypted in our object storage at long random addresses, and anyone holding such an address can open the file without signing in. We are stating this plainly rather than implying a protection that is not there. The storage provider encrypts data on its own disks, but that protects against physical theft of hardware, not against someone who has the link.
- Encryption in Transit: We use HTTPS (TLS) for all traffic between your device and our service, which prevents eavesdropping as your data travels over the internet.
- Access Controls: As a small, individually-run service, access to systems that store personal data is extremely limited. The developer/operator of FinalSaying is the only person who administratively manages the servers and database. There are no employees or unrelated third parties accessing user data. Within the system, your data is segmented by user account, and proper authentication is required to access it (only you can access your own account data via your login). We follow the principle of least privilege, meaning even within our infrastructure, we only open up what's necessary for the service to function.
- No Unnecessary Data Stored: As described in the collection section, we intentionally do not collect data that we don't need. By keeping logs short, and by collecting site analytics only from visitors who have accepted them — and holding those in Google's reporting rather than in our own database — we reduce the risk of any such data being leaked or misused. The less data we have, the less can go wrong with it. This is a form of "data minimization," which is a core principle of privacy and security.
- Secure Infrastructure: We host FinalSaying on secure servers (for example, reputable cloud service providers or hosting services) that employ industry-standard security practices. We keep the server software and dependencies up to date with security patches to protect against vulnerabilities. We also monitor the system for any suspicious activities.
- Third-Party Security: When we use third-party services (Google, Stripe, Resend, Twilio), we choose companies that are known for high security standards. These companies invest heavily in security and have certifications (for instance, many are ISO certified or SOC compliant). While using them means some data passes through their systems, we trust their security measures. For example, Stripe is known for secure handling of payment data, and Twilio and Resend are reputable for communications.
- Backups: Our database provider keeps backups of the database so that it can be restored after a failure. Message text stays encrypted with our message key inside those backups, and backups are subject to the provider's own encryption and access controls. In the event a backup restoration is needed, the same security controls apply.
- No Reading of User Content: Importantly, we (the operator) do not proactively read or access the content of your messages or attachments. The system might automatically handle them (e.g., encryption, storage, sending), but there is no routine where we look at your personal messages. We consider your content private and encrypted for your intended recipients only. In rare cases, if you request support that involves message content, we might need your permission to access it (for example, if you think there's a problem with how it was saved), but otherwise we leave it untouched.
- Breach Notification: While we strive to prevent any security breaches, no method of storage or transmission is 100% secure. In the unlikely event of a data breach that affects your personal data, we will notify you and the relevant authorities as required by law, and we will act promptly to contain and investigate the incident.
Our goal is to give you peace of mind that your sensitive messages are safe with us. We continually review our security practices to adapt to new threats and protect your privacy.
Data Retention
We retain your personal data only for as long as necessary to fulfill the purposes described in this Policy, or as required by law. Here's how that works in practice:
- Account Data: We will keep your account information (name, email, and related info) as long as you remain a registered user of FinalSaying. If you choose to delete your account or if we close the service, we will delete this information (unless we are required to keep it for legal reasons, explained below).
- Messages and Attachments: We store the messages and files you have saved with FinalSaying until they are delivered to your recipients, or until you decide to delete them. The core purpose of FinalSaying is to hold onto your messages until the appropriate delivery time (which could be many years in the future, depending on circumstances). Therefore, by default, we will retain your encrypted message content indefinitely (potentially for the remainder of your lifetime) or until the conditions for delivery are met (the check-in sequence goes unanswered). If you remove a specific message or attachment from your account, our system will delete that content from our storage (with the caveat that it may remain in secure backups for a short period, but will be purged from active use).
- After Delivery: We retain delivered messages and their attachments rather than deleting them automatically. This is deliberate: if a recipient tells us they never received a message, or it was lost in a spam folder, or a delivery has to be repeated or evidenced, we can only help if the content still exists. Delivered messages remain until you delete them while you are alive, or until your estate or a recipient asks us to remove them and we are satisfied the request is genuine. If you would prefer your messages to be destroyed after delivery, tell us and we will delete them on request.
- Payment Records: If you have made payments, we may need to retain some basic payment records (amount, date, service provided) for accounting and tax purposes. For instance, under German or EU law, certain financial records might need to be kept for a number of years. These records would typically reside with Stripe as well, but we might keep invoice information or transaction IDs. This data will be minimal and only used for legitimate financial record-keeping.
- Account Deletion and Your Requests: If you decide to stop using FinalSaying, you have the option to delete your account and all associated data. You can do this by contacting us (see "Contact Information" below) and requesting account deletion. We will then erase your personal information from our live databases, including your profile info and all messages and attachments you had stored. We will also instruct our third-party processors to delete data they hold on our behalf where applicable (for example, tell Stripe to remove personal details if possible, though they may retain transaction records as required for their legal compliance). Backup copies might persist for a limited time but will also be purged according to our backup retention schedule. Similarly, if you only want to delete certain messages or attachments, you can remove them from your account interface (if functionality allows) or ask us to do so, and we will delete those items.
In summary, we keep your data only as long as you want us to (since the service is user-directed) or as long as needed to carry out the service. If you remove your data or request deletion, we honor that and do not hold on to your personal information longer than necessary. Our aim is not to accumulate data but simply to serve your needs with the FinalSaying service.
Your Rights Under GDPR
Because we operate in the EU (and even if you're elsewhere, we want to extend the same principles), you have certain rights regarding your personal data. We fully respect and uphold these rights. Under the GDPR (General Data Protection Regulation), you have the following rights:
- Right of Access: You have the right to request a copy of the personal data we hold about you. This means you can ask us to confirm if we're processing your data and provide you with a copy of that data, as well as information about how we use it. For example, you can ask us to send you a report of your account information and any messages or attachments you have stored (note: message content would be provided in an understandable format – if it's encrypted, we may need to work out a way to provide it in decrypted form to you securely, since it's your data).
- Right to Rectification: If any personal data we have about you is incorrect or incomplete, you have the right to have it corrected. In practice, this might mean if your name is spelled wrong in our records or your email has changed, you can update it (either via your Google account or by telling us). We want to make sure we have accurate data, so we will gladly correct any mistakes. For user-generated content like your messages, rectification could mean you editing those messages if you wish; you typically have control to update your own content while you are alive and have access.
- Right to Erasure: Also known as the "right to be forgotten." You can request that we delete your personal data. This isn't limited to account deletion — you can ask us to remove any or all personal information we have about you. For FinalSaying, this would most often mean deleting your account entirely (and thus removing your name, email, messages, attachments, etc. from our systems). We absolutely respect such a request and will carry it out, except in cases where we legally must keep certain data (as noted in the Data Retention section, e.g. transaction records). If you request erasure, please note this is irreversible – if your data is deleted, any final messages that were scheduled will not be delivered because we will no longer have that data. We will inform you of the consequences if you choose to delete data that would affect the service.
- Right to Object: You have the right to object to our processing of your data in certain circumstances. Given that we do not market to you and do not track you across other sites — and that the one form of measurement we do use runs only if you opt in, and can be switched off again at any time from the "Cookie settings" link in the footer — the most relevant ground for objection in our case would be if we were processing your data under a "legitimate interest" and you have a particular situation that makes you want to object to that. For example, if for some reason you object to us holding your data for message delivery (perhaps you have changed your mind about using the service), you have the right to object. In practice, since we rely mostly on consent and minimal legitimate interest, an objection would likely be resolved by either us stopping that processing or by deleting your data (which is essentially the same outcome as a deletion request). You always have the right to object to any potential direct marketing use of your data – but we do not do any marketing with your data, so this is more a theoretical right in our context.
- Right to Data Portability: You have the right to obtain the personal data you provided to us in a structured, commonly used, machine-readable format, and you have the right to transmit that data to another service (or ask us to transmit it, where technically feasible). In simpler terms, you can ask for an export of your data that you could, for example, import into another application or just keep for your own records. For FinalSaying, this would likely mean we can give you a structured file (perhaps JSON or CSV or similar) containing your account info and the messages and attachments you saved (attachments could be provided in their original file form, and messages as text). We'll work with you to provide the data in a useful way if you need this. Portability applies to data you provided us directly or data generated by your activities, and since we don't generate much beyond what you provide, this largely overlaps with the Right of Access. Still, we are happy to help you port your data if needed.
- Right to Withdraw Consent: If we are processing any of your data based on your consent, you have the right to withdraw that consent at any time. For example, you consented to us using your Google account info when you signed up — you can later withdraw that consent by simply deleting your account (or contacting us to do so). Withdrawing consent will not affect the lawfulness of any processing we already did while we had your consent, but it will mean we stop processing your data going forward. In practice, withdrawing consent from FinalSaying would usually mean we have to deactivate or delete your account, since the service relies on the data you provided with consent. We will inform you if withdrawal will lead to service termination so you can make an informed choice.
- Right to Restrict Processing: In certain situations, you have the right to ask us to limit the processing of your data (essentially to just store it but not use it). This can be exercised, for example, if you believe your data is inaccurate (you can request restriction while we verify it), or if you have objected to processing and await verification of our grounds, or if you need us to preserve data for a legal claim while otherwise you'd want it erased. In our context, restricting processing might mean we keep your account and data but don't do anything with it until an issue is resolved. Since our default is not to use your data except for what you ask, restriction might rarely apply, but we will honor it if needed.
- Right to Lodge a Complaint: If you believe your privacy rights have been violated or you have a concern about how we handle your data, you have the right to lodge a complaint with a supervisory data protection authority. You can do this in the EU member state where you live, where you work, or where we are based (Germany). For example, in Germany the relevant authority is the Berliner Beauftragte für Datenschutz (Berlin Commissioner for Data Protection) since our operation is in Berlin. We would, however, appreciate the chance to address your concerns directly first – we're committed to privacy and will do our best to resolve any issues if you contact us.
We will not discriminate against you for exercising any of these rights. To exercise your rights, you can contact us at our email address provided below. We may need to verify your identity to fulfill certain requests (for example, to ensure that we don't give your data to someone else pretending to be you). Once your identity is confirmed, we will promptly act on your request. We aim to respond to all valid requests within one month, as required by GDPR, and usually sooner.
Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, legal requirements, or for other operational reasons. If we make changes, we will post the updated policy on this page and update the "Effective Date" at the top. For significant changes, we may also notify users via email or a prominent notice on the site, so you are kept informed.
Some reasons we might update the policy include: adding new features (for example, if we add a new third-party provider or a new way of collecting data, we'll update the policy accordingly), changes in applicable law, or improvements in our security and privacy measures. We encourage you to review this Privacy Policy periodically to stay informed about how we are protecting the personal data you entrust to us.
If you continue to use FinalSaying after a Privacy Policy update, we will take that as acknowledgment of the changes. However, if any change requires new consent from you (for example, if we ever wanted to collect additional data or use it for a new purpose), we will obtain that consent explicitly.
Contact Information
If you have any questions, concerns, or requests regarding your privacy or this Privacy Policy, please do not hesitate to contact us:
Email: contact@finalsaying.com
This is the dedicated contact for privacy and data protection inquiries. Whether you want to request deletion of your data, exercise any of your rights, or just ask a question about how we handle personal data, you can reach us at that email address. We will respond as quickly as possible.
Data Controller: Because FinalSaying is operated by a private individual in Germany, that individual is the data controller responsible for your personal data. You can use the above contact information to reach the data controller (the operator of FinalSaying).
We are committed to the principles of transparency, fairness, and user control in privacy. Your trust is very important to us. If anything in this Policy is unclear, please contact us and we will gladly explain or provide more details.
Thank you for reading our Privacy Policy. We hope it gives you confidence that your data is handled with care. Enjoy using FinalSaying, knowing that your privacy is respected.
