Goodbye App sets no cookies of its own. Nothing we wrote puts a cookie on your device, on the website or in the app. What keeps you signed in and remembers your settings is local storage, which is a different thing and is listed in full below. The cookies that can appear on this site are set by other companies whose code runs on some of our pages, and they are named here too. No cookie here serves you an ad, because there is no advertising on the site or in the app. The advertising-related cookies that can appear are Google's, set by the tag described below. What that tag tells us is whether an advertisement we paid for brought somebody here, and that is the whole of what reaches us from it; what Google's own cookies hold, and what Google does with them, is governed by Google's policy, linked below, and not by this page. There is no Google Analytics.
In short, these technologies are used on Goodbye App to:
Nothing here decides what you are shown. There is no recommendation system, and nothing on your device ranks your feed or suggests accounts to follow. Nothing stored on your device measures how you use the service, and nothing else measures it for any purpose of ours beyond the two things named in our Privacy Policy: error logs, and the tag that measures our advertising, which is on the website only. The service itself does record the things it is made of, such as your likes, your comments, whom you follow and block, and the count of people who have played a post's video or audio. What it records, and what it does not, is set out in that policy.
Cookies are small pieces of data stored on your device by your web browser. They are used to remember information about your visit to a website, such as your login status, preferences, and other settings. Cookies can be either temporary (session cookies, which are deleted when you close your browser) or persistent (stored on your device until they expire or are deleted).
Pixels (also known as tracking pixels or web beacons) are tiny images placed in a page or an email so that loading them tells a server the page or email was opened. We place none of our own. Nothing we build into an email reports back when it is opened, so we cannot tell whether you have opened one, and no page here carries a pixel that reports to us. One page carries somebody else's: the donate page on the website, where PayPal's donate form holds a one-pixel image that loads from PayPal's servers as the page opens and tells PayPal that it was opened. There is no donate page in the app.
Local storage is a place in your browser where a site can keep small amounts of data. Unlike a cookie it is not sent to the server with each request, and other sites cannot read it. It stays until you or the site remove it. It is what we use.
This is the whole of it, on the website and in the app alike:
For a single visit, and cleared when the tab closes, the browser also holds where to send you after you sign in, whether a Google sign-in is in progress, and the name Apple sent once so that the sign-up screen can show it. Firebase Authentication, which checks your sign-in, keeps its own session record in your browser's storage in the same way, not in a cookie of ours.
None of it is a profile of you. Nothing you have written is in it, none of it is read by anything but the app on your device, and none of it is sent to us as such. Signing in on another device shows you the same account, because your language and your notification settings are stored on the account itself, not because anything on one device is linked to another. Your theme is not: it is kept on each device.
These are the companies whose code runs on some of our pages and may set cookies of their own. Each one's cookies are governed by its own policy, linked here, not by this page.
Two other requests carry your network address to a company outside this service but set nothing of ours. The copyright page loads a DMCA badge from images.dmca.com. And if you record a voice message in a browser that cannot record the format we need, the recording is converted on your own device using code fetched once from unpkg.com; the recording itself is never sent there.
Nothing of ours runs on anyone else's pages. We do not offer embeds, there are no Goodbye App timelines on other people's sites, and we publish no API for other sites to build on. If you follow a link out of Goodbye App , the site you arrive at sets its own cookies under its own policy.
Because we set no cookies, blocking cookies in your browser does not sign you out of goodbyeapp.com or break anything of ours, though it may affect reCAPTCHA, the Google Maps suggestions or the YouTube previews on the pages that use them. Clearing your browser's site data removes local storage too, which signs you out. If your browser blocks local storage entirely, you cannot sign in.
What we collect, and what we do with it, is set out in our Privacy Policy.