◌ Stillmood
Stillmood · Your rights

Privacy policy

Your feelings. Clear choices.

Effective from 22.10.2026

Who is responsible

The data controller for Stillmood (published in Polish as Nastrojnik; Google Play publisher brand: Kolava) is:

Bartłomiej Kolawa
Młynne 340, 34-600 Limanowa, Polska
kontakt@bartlomiejkolawa.pl

Contact us about access, privacy or deletion at the email above.

Your journal on your device

Guest journal entries, moods, emotions, triggers, needs, notes, exercise answers, safety plans, time capsules and progress are stored locally. Only enter information you wish to provide; avoid other people’s personal data. The safety plan is an exception: you can add names and phone numbers of people you want to reach; with sync consent they are stored in the cloud with the plan.

We do not use journal content for advertising or AI model training. Narration and illustrations are prepared assets; playing them does not send your notes to media-generation providers. Some session and story recordings are downloaded from Supabase servers (file storage). Like any server, they see your IP address, the time of the request and the requested file. The file is identified by a hash of its contents rather than by the recording’s name, although the public list of recordings shows which recording a hash belongs to. The request carries no account or installation identifier, and we do not link downloads to your account or to statistics. Downloaded recordings stay on your phone; you can delete them in Me → Reminders and narrator voice → Recordings on this phone. Your journal is not included in Google cloud backups; it moves only in a direct transfer to a new phone that you start yourself. You can save a free copy of your entries, notes, answers and plan as a JSON or CSV file at any time (Me → Privacy → Export data); files you export are yours to manage.

Sleep and steps from Health Connect

If you choose to connect Stillmood to Health Connect, the app reads only sleep duration and step counts from the last 30 days to compare them with your check-ins on your device. This data is not stored on a server, synced, shared with third parties, or used for advertising or analytics. Connecting is optional; “Disconnect” in Stillmood stops reading. You can separately revoke system permissions in Health Connect.

Use of information received from Health Connect adheres to the Health Connect permissions policy, including the Limited Use requirements.

Accounts and sync

Supabase provides online accounts for Stillmood. Before sign-in, we ask for explicit consent to sync your journal and progress, including entries previously saved as a guest. We record the consent version, language and time. Profile settings are synced too: language, time zone, support style, reminders, theme, chosen goals and your statistics choice. Account data includes your email, identifier and authentication information. Passwords are not stored as plain text in the app. For account security, Supabase records the IP address and device or browser information of sign-in sessions.

You can use email and password or sign in with Google. Google sign-in supplies identity confirmation, basic profile and email; we do not request access to mail, Drive or Calendar. Supabase sends account confirmation and password reset messages through Resend. Resend processes the recipient address, message content including the code, and delivery information. Journal entries are not sent through this channel.

Guest mode does not require an account. Signing out does not erase server data. You can delete your account and linked data in the app or through the account deletion procedure on this website.

Purchases, analytics and this website

Google Play or the App Store processes payment. RevenueCat verifies subscriptions using user/installation identifiers, purchase, product and entitlement information and technical device/connection information. If the transaction country is unknown, RevenueCat determines the country from the IP address; it does not keep the IP address itself. The country code also reaches our database with purchase events and is removed after 90 days. This can also occur without a journal account. We do not receive your full payment-card number.

Voluntary testing with an access code requires an app account. To administer the test, we store the account and campaign identifiers, Free or Plus assignment, activation status and access start and end dates. RevenueCat manages promotional Plus access. These records contain no journal content or health data and do not require optional usage statistics to be enabled. We delete them in the next daily cleanup after access has expired for 90 days and campaign enrolment has closed, or earlier when the account is deleted; only aggregate used-slot counts remain.

Usage statistics are optional and off by default. With consent, including in guest mode, we send Supabase a random installation identifier, event names and times, keys of the exercises, sessions, stories and other content you open, app version, operating system, language, plan, narrator variant, reminder settings (morning, evening) and sync status (counters, last sync time and last error code). The installation identifier may be linked to the account signed in when statistics are sent and to a subscription identifier; after signing out or deleting the account, the app creates a new identifier. In the admin panel, statistics of an installation linked to an account are shown together with that account’s email address. Statistics exclude notes, selected emotions, triggers, answers, journal content, Health Connect data and SOS usage. Turning consent off in Privacy clears the local queue and requests deletion of installation data on the server, together with its link to the subscription at RevenueCat and in purchase records; offline deletion is retried when the app reconnects. This does not override legal retention requirements for transaction records.

Older app versions could, with usage statistics enabled, send the numeric change between a scale score before and after an exercise. Once the server-side change is deployed, we stop recording new values, including those sent by older versions. Historical statistics events remain subject to the retention period of up to 13 months described below; withdrawing consent requests their deletion as explained above.

Error reports have their own switch in Privacy, separate from statistics. A report contains the random installation identifier, the type of error, the places in the app’s code where it happened, the screen name and the app and system version; never journal content, notes, emotions, answers or SOS usage. Until you set the switch, reports are sent only while statistics are on; when something breaks, the app asks once whether to send them, and until you answer the error stays on your device. Turning reports off deletes this installation’s reports from the server.

The support form sends only the message you choose to submit, a random support identifier for this installation (for abuse protection and to delete reports with your account), its category, optional reply email and content key, plus the technical details shown in the preview if you leave that option enabled. For support reports, the network address is processed only as a cryptographic hash to protect against abuse. A draft stays on your device until sent. Please do not include passwords or journal entries. Support messages are accessible only to authorised support staff and are retained to handle the request and any applicable obligations.

Vercel hosts this website and may process IP addresses, request times, URLs and browser information to deliver and protect it. We have added no ads, marketing analytics, external fonts or tracking cookies. An email link opens your mail app; it does not send a message automatically. Correspondence is handled through Gmail and the publisher’s OVH Zimbra mailbox.

Purposes and legal grounds

Account, sync and purchase processing, and delivering the app’s content, including recording downloads, support performance of a contract (GDPR Article 6(1)(b)); legal obligations use Article 6(1)(c). Security, necessary correspondence and legal claims rely on legitimate interests (Article 6(1)(f)). Optional analytics and error reports rely on consent (Article 6(1)(a)).

Wellbeing content may reveal health information. Cloud processing requires explicit consent under Article 9(2)(a) and is not required for the local journal. You may withdraw consent by requesting deletion of cloud data. We do not make legally significant automated decisions. Exercise suggestions are computed on your device from your entries, sessions, favourites and chosen goals, including synced ones; they are not diagnoses.

Providers and international transfers

We use Supabase (accounts, database, sync and recording downloads), Resend (authentication emails), Google (optional sign-in and store), RevenueCat (subscriptions), Vercel (website), and Gmail and the publisher’s OVH Zimbra mailbox (contact). Apple provides the store on Apple platforms. The Supabase project database is in an EU region; other services, support or provider infrastructure may involve processing outside the EEA. Transfers require appropriate safeguards, such as an adequacy decision or standard contractual clauses. Ask the controller for details of the configuration and safeguards.

We do not sell journal data. Authorities may receive data where required by law.

Retention

Saved journal and progress data remains locally and, after sync consent, in the active database until you delete the data or account. We do not automatically erase your journal because of inactivity or subscription expiry. Deleting an individual entry may leave a technical deletion marker needed to sync devices. Account deletion removes the authentication account and linked records from the active database, the customer record at RevenueCat, your support and error reports, and that account’s data from the device where deletion was requested; purchase events are kept without identifiers. Exports and copies on other devices need separate deletion.

Unfinished check-in and edit drafts can be resumed for 30 minutes after the last save; once expired, the app removes them at the next check. Sleep and step data from Health Connect is read for the current comparison and is not copied to our database.

Technical data is deleted automatically: statistics events after 13 months, installation data after 13 months without activity, error reports after 90 days, support reports 24 months after the case is closed (36 months at the latest), and the full RevenueCat subscription event payload is reduced after 90 days to what billing records need.

Supabase, Resend and other providers retain backups and logs under cycles that depend on the service and its configuration. Deleting an active account does not immediately erase these copies. Contact the controller for backup and log retention details relevant to your request.

Stores and billing providers may retain transaction records under their obligations after journal deletion. Correspondence is retained to resolve the request and thereafter only for legal obligations or justified claims handling.

Your rights

You may request access, a copy, correction, deletion, restriction and, where applicable, portability. You may object to legitimate-interest processing and withdraw consent without affecting earlier lawful processing. Identity verification must be proportionate; do not send passwords or unnecessary ID scans.

We respond without undue delay, normally within one month, and explain any lawful extension. You can complain to Poland’s President of the Personal Data Protection Office (UODO) or your competent supervisory authority. Stillmood is intended only for adults aged 18 or over, not for children or teenagers. Contact the controller about a minor’s data.