Privacy Policy
This is how MyFeelings and this website handle personal data, split by what is live today and what is planned for the app, which has not been released yet. Effective 2026-09-11.
Who we are
MyFeelings is provided by Keep Global Limited, a company registered in the United Kingdom under company number 17452153, with its registered office at 128 City Road, London, EC1V 2NX, United Kingdom. For anything in this policy — a question, a correction, or a request about your own data — write to [email protected]. Keep Global Limited is the controller of the personal data described below.
What data we collect
What we collect depends on how you reach us, and splits into what is live on this website today and what is planned for the app once it ships. Nothing below is collected in the present tense for the app — it has not been released yet.
This website
Visiting this site sends the usual technical signals a browser sends to any page — which pages you view, the page you came from, a rough location derived from your IP address, and the type of device and browser you used — to our website analytics processor, listed below. We do not set a cookie and we do not write anything to your browser to recognise you on a later visit; see "Cookies and similar technologies".
Writing to us
Today, reaching us means emailing [email protected] directly — there is no web form yet, so your message goes straight to our own inbox and is not processed by any third party on the way. We keep whatever your message and your own email address contain, to reply to you. If a web form is added later, its operator will be named in the table below, the same way every other processor is.
The app, once it is released
Using the MyFeelings app will require an account, and your check-ins, notes and tags will be stored on our servers as part of it rather than only on your own device. That means the content of a check-in — the feeling you chose, any tag, and anything you wrote in a note — is personal data we hold, not only data you hold. Notes in particular can contain whatever you decide to write, including other people's names and details of your health, which is why this is the section to read before you start using the app. We host that data ourselves, on our own servers in Germany — it does not sit with a third-party platform. Once the app is released its own in-app disclosure will describe the account precisely, and this page will be updated to match it before that happens.
The app is also expected to send product-usage analytics and crash or diagnostic reports, so that problems can be found and fixed. Which companies process those has not been confirmed either, for the same reason: the owner has told us these two features exist, not who runs them.
Payments, once subscriptions launch
Subscriptions are planned and not available today. If they launch, they would be sold through Apple's App Store, which makes Apple the seller of record — we would receive confirmation of a subscription, never your card details.
Why we process your data
UK GDPR requires a lawful basis for each purpose above. This is ours, purpose by purpose:
- Website analytics — our legitimate interest in understanding how this site is used, kept to a minimum because no cookie or persistent identifier is set.
- Replying to a message you send us — our legitimate interest in answering correspondence you chose to start, and your own choice in sending it.
- The app account, once released — performance of a contract. Creating an account is how you ask us to keep your check-ins, and keeping them is the service the account exists to provide; you agree to that when you create one, and you end it by deleting the account.
- App analytics and crash reports, once released — our legitimate interest in understanding how the app is used and fixing what is broken in it.
- Subscriptions, once launched — performance of a contract, and our legal obligation to keep accounting and tax records.
Who receives your data
This table lists every recipient of personal data we know of, live and planned. UK GDPR asks us to identify who receives personal data, so each one is named here rather than covered by a vaguer line like "and other service providers". If a recipient is ever added, it appears here before it starts receiving anything.
| Recipient | What for | Status | What this means for you |
|---|---|---|---|
| Google Analytics 4 | Website analytics | Live today | Runs on this website only, and is configured to store nothing on your device: it sets no cookie and writes nothing to your browser, so it cannot recognise you on a later visit. |
| Amplitude | App analytics | Planned — not running | Receives how the app is used — which screens are opened, which features are reached — so the app can be improved. It does not receive the words you write in a note. |
| Firebase Crashlytics (Google) | Crash & diagnostic reports | Planned — not running | Receives a report when the app crashes: what the app was doing, the device model and the operating system version, so the fault can be found and fixed. |
| Apple | Subscription payments | Planned — not running | Subscriptions are planned and would be sold through the App Store, which makes Apple the seller of record. We would receive no card details. |
| Keep Global Limited (our own servers) | Account | Planned — not running | An account is required to use the app. Your check-ins, notes and tags are held on our own servers in Germany — not with a third-party platform — as part of that account. |
Today, 1 of the 5 recipients above are live; the remaining 4 are planned for the app and are not receiving anything yet.
International data transfers
The check-ins, notes and tags in your account will be held on our own servers in Germany. Germany is in the European Economic Area, and the UK government has made adequacy regulations covering the EEA, so moving that data from the United Kingdom to Germany needs no further safeguard. This is the part of the picture that matters most, because it is the part that holds what you actually write.
The other recipients in the table are third-party companies, and some of them process data outside the United Kingdom: Google Analytics 4 for this website, Amplitude and Firebase Crashlytics for the app once it ships, and Apple if subscriptions launch. Sending personal data to a country the UK has not found adequate requires a safeguard, such as the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses. We have not yet documented which applies to each of them, so we are not naming one here that nobody has signed. That is a gap, and writing it as one is better than filling it with a mechanism for the sake of completeness.
How long we keep data
We keep personal data only for as long as the purpose it was collected for requires, and delete or anonymise it once that purpose ends. Rather than leave that as a sentence about reasonable periods, here is the actual schedule. Where a row says a period applies to the app, it starts when the app does.
| What | How long | Why | Status |
|---|---|---|---|
| Your check-ins, notes and tags | for as long as your account is open, then deleted within 30 days of you closing it | They are the thing the app is for; keeping them after you leave serves nobody. | Our commitment |
| Your account itself | until you delete it, or after 24 months of no activity, whichever is first | An account nobody has opened in two years is a standing risk with no benefit. | Our commitment |
| Crash and diagnostic reports | 90 days | Long enough to find a pattern across releases, short enough not to become an archive. | Our commitment |
| Website analytics | 14 months | Google Analytics 4 own retention maximum for event data on its standard setting. | Our commitment |
| Emails you send us | 24 months from the last reply | So a conversation can be picked up again, and so a complaint has a record. | Our commitment |
| Records of a purchase | 6 years from the end of the accounting period | UK company law requires accounting records to be kept; this is not ours to shorten. | Required by law |
Your rights
Under UK GDPR you can ask us to: confirm what personal data we hold about you and get a copy of it; correct it if it is inaccurate; delete it; restrict how we use it; receive a portable copy in a common format; and object to processing based on our legitimate interests. We do not carry out automated decision-making that has a legal or similarly significant effect on you. Write to [email protected] to use any of these rights. If you are unhappy with how we have handled your data, you can also complain to the UK's independent regulator, the Information Commissioner's Office (ICO), at ico.org.uk.
Children
MyFeelings is not for anyone under 18, and we do not knowingly collect personal data from anyone below that age. If we learn that someone under 18 has given us personal data, we will delete it. A parent or guardian who believes their child has done so can write to [email protected].
Cookies and similar technologies
This website sets no cookies and writes nothing to your browser's storage. Its analytics is configured so that it holds nothing on your device between visits, which is also why there is no cookie banner here — there is nothing stored to ask your permission for. If the app introduces anything like a cookie once it exists, that will be described here and in the app's own disclosure, not assumed from this website's setup.
Changes to this policy
We may update this policy as MyFeelings, its processors, or the law around them change. We will update the effective date below when we do, and, once the app is released, a change that affects it will also be described in the app's own in-app disclosure rather than only here.
Effective date
This policy took effect on 2026-09-11. See also the Terms of use that apply alongside it.