Privacy Policy

Last updated: 3 October 2026

1. What KinStatus is, and what it is not

KinStatus is a family check-in and reassurance service. It helps families who care for a loved one from a distance know when that person says they are OK, wants a call, or needs help.

Status — the check-in itself — is the core purpose of KinStatus. Last known location is optional, supporting context. The family-facing product only ever shows the single most recent location; KinStatus does not build a route history or movement log for your family to view.

KinStatus is built for reassurance, not surveillance. KinStatus is not an emergency service, not a medical, care, or rescue service, not a continuous-monitoring or security service, and it does not guarantee that any person is safe. It does not verify the truth of any status a person sends, and a missed or delayed check-in does not by itself mean something is wrong. In an emergency, call 112 or your local emergency number.

KinStatus is a family check-in and coordination service. Eligible new families may receive a 30-day free trial and can use Free Basic or choose a paid Plus or Family plan. Payments are handled by the applicable app store; KinStatus does not receive or store payment-card or bank-account details. Features, availability, and this Privacy Policy may change over time — see Section 24.

KinStatus is available internationally, subject to applicable local law, and is intended for use by adults aged 18 and over — see Section 22.

2. Who is responsible for your data (the controller)

KinStatus is operated by Desimir Abadzhiev (Десимир Абаджиев), a natural person established in the Republic of Bulgaria, VAT registered.

• Address: 28 Zlatorog Street, Plovdiv, Bulgaria
• Telephone: +359 886 876 542
• Email: support@kinstatus.app
• VAT number: BG8070038995
• Legal Notice: kinstatus.app/legal-notice/

All privacy questions and requests, and all general customer support, use the same address: support@kinstatus.app.

3. Who this policy is about

This policy applies to different people differently, depending on how they relate to KinStatus:

• Caregiver account holder — anyone who creates a KinStatus account.
• Family owner — the caregiver who created a family group and manages its membership.
• Invited caregiver or helper — someone added to a family group by its owner, with access determined by their role.
• Protected person, before activation — someone a caregiver has begun to set up in KinStatus but who has not yet activated the app on their own phone.
• Protected person, during and after activation — someone who has entered an activation code on their own phone and is connected to a family group. Once activated, the protected person is a direct user of KinStatus in their own right, with their own rights under this policy.
• Authorised representative — someone who contacts us on behalf of a protected person who cannot act for themselves.
• Support requester — anyone who contacts support@kinstatus.app, whether or not they otherwise use KinStatus.
• Website visitor — anyone who visits kinstatus.app, whether or not they use the app.

4. Information we process

• Account data: email address, display name, password (stored in hashed form), language and timezone settings.
• Family data: family group, member roles (owner, caregiver, helper), invitations and their status. Invite codes are verified and stored server-side using a hash; a caregiver's device, or a browser's local storage on web, may temporarily hold the plain invite code until it is used or the relevant storage is cleared.
• Protected-person data: display name, a relationship or category label, optional phone number, timezone, activation status, and location-sharing/permission state.
• Check-in and status data: scheduled check-ins and responses ("I'm OK", "Call me", "I need help"), timestamps, acknowledgements, reminders, and alerts.
• Location data (only while enabled — see Sections 8–9): the last known location of the protected person's phone — coordinates, accuracy, and time — kept as a single most-recent value shown to the family. We do not build a location history for your family to see.
• Battery and phone-health data: battery level sent with a location update, and technical phone-health signals such as whether notification and background permissions are enabled. We do not collect hardware identifiers such as an IMEI.
• Device and app data: device session records, app version, and push notification tokens, kept separately for caregiver devices and protected-person devices.
• App setup telemetry: a random identifier created for each installation of the app, app version, platform, language setting, whether the installation is new, and a limited record of setup steps and their outcomes — for example, which role was chosen, whether sign-in or code entry succeeded, and broad error categories. After you sign in, some of these events may be linked to your account on our servers. This telemetry is designed not to include your email address, name, phone number, any code you enter, status messages, or location.
• Install source (Android): when KinStatus is installed from Google Play, limited information about how the installation reached KinStatus, such as campaign source, medium, and campaign name, and whether the install-source information contains a marker indicating that the installation may have followed a click on one of our Google Ads. We do not store Google's raw ad-click identifiers, and we do not collect your device's advertising ID for this purpose. (The separate advertising-effectiveness measurement in the Android app, described below, does use the advertising ID.)
• Security and anti-abuse data: rate-limiting and abuse-prevention records, and an internal log of significant account and family actions.
• Support and rights-request data: messages sent to support@kinstatus.app, including deletion and other rights requests, and, where applicable, contact and authority information for anyone acting as an authorised representative of a protected person.
• Trial and eligibility data: your family's trial start and end information and a technical record used to prevent repeated free trials. A supported device identifier may be processed transiently by KinStatus to create a purpose-bound derived value; the raw identifier itself is not stored. The derived value is treated as personal data and is not used for advertising, profiling, or location tracking.
• Subscription data: the family linked to the subscription, the app-store provider, product and plan identifiers, subscription status, renewal or expiry information, and store purchase or transaction identifiers needed to validate and administer the subscription. KinStatus does not store your card number, bank details, billing address, or other payment-instrument data. Certain store-event identifiers may also be stored as derived hashes for notification processing, security, or deduplication.
• Website connection data: when you visit kinstatus.app, ordinary connection and server-log information such as IP address, browser and device information, requested pages, and timestamps may be processed to deliver and secure the site. On the pricing page, the request IP is also used momentarily to determine the visitor's country for localised pricing — see Section 21.
• Website analytics and advertising-measurement data: information about how the website is used and whether a visit came from our advertising, processed through Google Analytics and Meta technologies on the website — see Section 21.
• Android app measurement data (caregivers only): after a caregiver uses the sign-in or registration buttons in the Android app, limited analytics and advertising-effectiveness measurement through Google Analytics for Firebase and Meta App Events, which may use the device's Android advertising ID — see "Advertising-effectiveness measurement in the Android app" below.

Apart from the Google and Meta measurement in the Android app described below, the KinStatus app does not include third-party analytics, advertising, or crash-reporting software. The app setup telemetry and install-source information described above are collected by KinStatus itself and stored with our database provider (Section 15). We use them only to understand how people find and set up KinStatus, to find where setup goes wrong, to improve reliability, and to measure at a limited level which channels or campaigns bring new installations. We do not use them to secretly track anyone, to build advertising profiles, or for behavioural advertising. We do not sell personal data.

Advertising-effectiveness measurement in the Android app

Current versions of the KinStatus Android app include Google Analytics for Firebase (provided by Google) and Meta App Events (part of the Meta SDK, provided by Meta). We use them for limited app analytics and to measure how well our advertising works — for example, whether people who install KinStatus after seeing one of our ads go on to create an account, set up their family, and connect their loved one's phone. This measurement is not used in the KinStatus iOS app.

When it starts. On the caregiver sign-in and registration screen, a notice next to the sign-in and registration buttons (such as Continue with Google, Register, and Log in) explains that continuing includes this measurement. When you use one of those buttons, the measurement is turned on for that device.

Before that point. Google Analytics for Firebase runs in a restricted mode: KinStatus tells Google that analytics storage, advertising storage, advertising user data, and ad personalisation are all denied, so the Firebase software does not use an app-instance identifier or the advertising ID. In this mode, Google may still receive limited technical signals about app use that are not linked to those identifiers. The Meta software is not started and does not send app events to Meta.

After that point, on that device:

• Google Analytics for Firebase collects information about how the app is used, such as app opens, sessions, and the KinStatus events listed below, and may use the device's Android advertising ID to measure the results of our advertising with Google. KinStatus tells Google that ad personalisation is denied for this information.
• Meta App Events records when the app is opened and closed, together with the KinStatus events listed below, and may use the device's Android advertising ID and information from Google Play about how the app was installed (the install referrer) to measure the results of our advertising with Meta.

The KinStatus events. KinStatus itself sends exactly three events: an account was newly created (sign_up, which Meta records as its standard "Complete Registration" event); a caregiver's first family setup was completed (caregiver_setup_complete); and a loved one's phone was first connected to the family (family_link_complete, counted at most once per family). Each event contains only its name. KinStatus does not add your name, email address, phone number, account or family identifiers, your loved one's details, invite codes, check-in answers or history, status or distress information, location, schedules, push tokens, or billing information to these events.

Information added by Google and Meta. Separately from the KinStatus events, the Google and Meta software automatically adds technical information to what it sends — for example, device model, operating-system and app version, language and time-zone settings, IP address, timestamps, and the identifiers described above. Google and Meta process this information under their own terms and privacy policies.

Who it applies to. This measurement is for caregivers only. It is switched off while a phone is used in the loved one's (protected person's) mode, and that mode never sends the KinStatus events. Before a phone has been set up for either role, the restricted mode described above applies.

Turning it off. In the Android app, go to Profile → Privacy and account → "Help us improve KinStatus". Turning this switch off stops Google Analytics for Firebase and Meta App Events on that device straight away, and you can turn it back on there at any time. Turning it off does not limit any KinStatus feature. The setting is stored on the device: if you reinstall the app or use another device, using the sign-in or registration buttons there turns the measurement on for that device again, and you can turn it off in the same way. Turning it off stops further collection; it does not by itself delete information Google or Meta have already received. You can contact support@kinstatus.app about that information — see Section 19.

What KinStatus keeps. The on/off setting is stored only on the device. To count each family's first phone connection at most once, KinStatus keeps on its own servers a record of the family and the time that event was counted; this record holds nothing else and is deleted together with the family.

5. Purposes and legal bases

We rely on different legal bases depending on who is involved and what is being done with their data. A caregiver's own contract with us does not by itself extend to, or provide the legal basis for, our processing of a protected person's data. Activating KinStatus is not, by itself, treated as conclusively forming a separate contract with the protected person. For the protected person's own check-in, status, and related notification processing described below, we instead rely on our legitimate interest in providing the service the protected person knowingly and voluntarily activates and uses, balanced against their rights and expectations, and subject to their right to object (Art. 6(1)(f)) — see Section 19.

Where we rely on legitimate interests (Art. 6(1)(f)), you have the right to object — see Section 19.

We do not make decisions about you that produce legal or similarly significant effects based solely on automated processing (GDPR Art. 22).

6. Special-category (health-related) information

KinStatus is not designed to collect medical records, diagnoses, or other health documentation, and it is not a substitute for one. Please do not enter medical details that are not necessary for a status message. If you believe special-category data has been entered into KinStatus, contact support@kinstatus.app.

7. Information a family member provides about you before you join

Before you activate KinStatus on your own phone, a caregiver setting up care for you can create a short, limited record about you: your name, your relationship to them, and, sometimes, your phone number. We do not collect your location, your check-in status, or your phone's technical state at this stage — those only begin once you activate KinStatus yourself (Sections 8–9).

This record comes from your family member, not from you, and is processed on the basis described in Section 5. It is not made visible to other KinStatus users or families. You have the rights described in Section 19 with respect to this record, including the right to ask who can see it, to object to it, and to request its erasure, whether or not you go on to activate KinStatus. To exercise any of these rights, contact support@kinstatus.app.

If we hold information about you that a family member gave us rather than you, we will give you the information GDPR Article 14 requires — who we are, what we hold, why, and what your rights are — no later than a reasonable time after we obtain it, and in any event within one month, or earlier if we contact you or disclose the data to a further recipient sooner.

8. Location and background location

KinStatus only receives a location update from the protected person's phone while the protected person has granted the Android location permission to KinStatus, and while location sharing is enabled for their account. Future location access is controlled entirely through the phone's Android Settings and the system location permission — there is no separate in-app location toggle for the current version of KinStatus. Granting this Android permission is a technical operating-system control, not a form of consent under the GDPR; our legal basis for this processing is described in Section 5.

Once the Android location permission is removed, Android stops supplying KinStatus with any new location coordinates, so no reading can be captured after that point. This does not mean nothing more is delivered to us afterward — see Section 9 for how a small number of readings already captured before the permission was removed are handled.

9. Location sharing — turning it off

The protected person can stop KinStatus from receiving any further location readings by removing KinStatus's location permission in their phone's Android Settings — typically: Settings → Apps → KinStatus → Permissions → Location → Don't allow (exact wording and steps may vary slightly by Android version). This is an operating-system control, not a separate switch inside the KinStatus app.

A few things to know about how this works in practice:

• Location readings already captured on the phone before the permission was removed may remain briefly in a small on-device queue and may still be delivered to us afterward. This queue holds at most 200 readings, and readings older than approximately 23 hours become eligible for removal from the queue. No reading captured after the permission was removed is ever added to this queue.
• Removing the permission does not, by itself, delete a last known location value we already received and stored before the permission was removed. That value may remain visible to your family group with its original timestamp. It should not be understood as a live or current location merely because it remains visible — always check the timestamp shown alongside it.
• Restoring the Android location permission later may allow location updates to resume.

See Section 17 for how long a last known location value is otherwise retained.

10. Family group access and roles

Your status, last known location (where enabled), battery, phone-health information, and last-activity information are visible to your family group according to member roles. The family owner manages the family group and its membership, including inviting and removing helpers; helpers and other caregivers have the access their role provides but cannot manage who belongs to the family. A protected person's device connection to the family group can be revoked by the family owner.

A family role does not by itself prove legal authority, guardianship, or consent to monitor another person. You must not invite, monitor, or disclose information about another person without a lawful basis and that person's own knowledge and agreement.

11. Notifications and push tokens

KinStatus sends notifications to two separate audiences — caregivers and the protected person — using separate push tokens for each. We store a push token for each registered device, together with a hashed copy used for technical verification; both are kept only for notification delivery.

There are several distinct kinds of reminders and alerts:

• Locally scheduled check-in reminder — scheduled directly on the protected person's phone by the app itself, using the phone's own operating system.
• Server-side reliability reminder — a remote reminder for the same scheduled check-in, sent to reduce the chance that a check-in is missed if local scheduling does not work as expected.
• Caregiver-triggered reminder — a caregiver can trigger a reminder sent remotely to the protected person's phone.
• Strong-signal alert — a caregiver can send a more urgent remote alert to the protected person's phone.
• Acknowledgement confirmation — when a caregiver acknowledges a check-in, a remote confirmation may be sent back to the protected person's phone.
• Alerts to caregivers — caregivers receive remote notifications about check-ins, alerts, and reminders concerning a protected person in their family.

Remote notifications are delivered using Firebase Cloud Messaging and/or Expo Push, depending on notification type and device. We cannot guarantee that any notification is delivered, seen, or acted on — see Section 1.

12. Battery, phone-health, on-device location queue, diagnostics, and last-activity data

• Battery level sent with a location update shows your family approximately how much charge the protected person's phone has. It follows the same basis and availability as the location update it accompanies (Sections 8–9). A previously stored battery value is not automatically removed when location sharing is turned off; it is retained on the same terms as the last known location value it accompanied.
• Phone-health / permission-state snapshots let a caregiver understand why location or notifications might not be updating, and show approximately when the phone last sent any signal to KinStatus. This is diagnostic information only — it does not include coordinates or hardware identifiers. Phone-health snapshots continue to be collected and remain visible to the family group even if the Android location permission is removed, so a caregiver can diagnose why location has stopped updating; this diagnostic processing is separate from, and not controlled by, the Android location permission described in Section 9.
• Last check-in / status activity shows your family when the protected person last responded to a check-in. This is derived only from check-in events, not from location, and continues to be collected regardless of location-sharing status. A separate "last signal from the app" indicator, sourced from the phone-health snapshot rather than a check-in, may also be shown; it reflects device/app activity, not that the protected person has actively confirmed anything.
• On-device pending-location upload queue: while the phone is trying to send a location update, it may hold that reading, and a small number of other recent readings, on the device itself, so none are lost if a single send attempt fails. This queue holds coordinates, accuracy, battery level, and capture time for up to 200 readings, kept only on the protected person's own phone. Readings older than approximately 23 hours become eligible for removal from the queue. This queue is not shown to your family — it is an operational buffer, not a location-history feature.
• On-device diagnostic events: the app on the protected person's phone may keep a technical log of events such as when its location service started, stopped, or encountered an error, used only to diagnose why location updates might not be working. This log does not include coordinates, is kept only on the protected person's phone, and is bounded to at most 200 entries. It is not shown to your family.

13. Security, anti-abuse, and audit records

To protect accounts, invite codes, and the location-upload path against abuse, we record certain technical identifiers (such as IP address and user agent) as pseudonymous hashes wherever technically implemented, rather than as plain text. We also keep an internal log of significant account and family actions, such as invitations, role changes, and permission or preference changes. Ordinary application access to this log does not allow changing or deleting past entries.

14. Free trial, paid plans, and Free Basic

Eligible new families may receive a 30-day free trial. Eligibility is limited to prevent repeated use of the trial by the same family or device and depends on KinStatus being able to perform its supported eligibility check. The trial does not require payment details and does not turn into a paid plan by itself. If no trial is available, or after a trial ends, the family can use Free Basic or choose a paid plan.

For trial-abuse prevention, KinStatus may process a supported device identifier transiently and store a purpose-bound derived value rather than the raw identifier. The derived value is treated as personal data, is used only for trial-abuse prevention, is not shown to KinStatus users, and is not used for advertising, profiling, or location tracking. If you believe trial information about your family is incorrect, contact support@kinstatus.app.

Plus and Family are paid plans. Purchases are handled by the applicable app store. KinStatus receives the subscription information needed to validate the purchase and keep the family's entitlement in step with the store-reported subscription status; KinStatus does not receive or store your payment-card or bank-account details.

Free Basic is a limited mode. Safety-related access described elsewhere in this policy and the Terms is not converted into a payment-status claim.

Premium is planned for a later release. If Premium introduces new processing activities, this Privacy Policy will be updated as appropriate before those activities are used.

15. Who else processes your data

We use service providers to help us run KinStatus, including:

• Supabase — our database, authentication, and server functions provider.
• Expo — push notification delivery to caregiver and protected-person devices.
• Google (Firebase Cloud Messaging) — push notification delivery to Android devices.
• Google (Google Maps) — map display in the caregiver app.
• SuperHosting.BG EOOD ("СуперХостинг.БГ" ЕООД), Bulgaria — website hosting and support-mailbox hosting.
• Google Play — distributes KinStatus on Android and, when a subscription is purchased through Google Play, processes the store purchase and related payment/account information under Google's own terms. KinStatus receives only the subscription information needed to validate and administer the KinStatus entitlement; KinStatus does not receive the user's payment-card or bank-account details.
• Apple App Store — where KinStatus or a KinStatus subscription is offered through the Apple App Store, Apple processes the applicable store, account, and payment information under Apple's own terms. KinStatus receives only the transaction/subscription information needed to validate and administer the KinStatus entitlement.
• Google (Google Play and Google Ads install attribution) — when KinStatus is installed from Google Play on Android, Google Play provides the app with limited information about how the installation was reached, which may include campaign details from our Google Ads advertising (Section 4). Google processes ad clicks under its own terms.
• Google (Google Analytics) — measurement of how the kinstatus.app website is used (Section 21).
• Meta (Meta Pixel and Meta Conversions API) — measurement of how our advertising performs on the kinstatus.app website (Section 21).
• Google (Google Analytics for Firebase) — in the Android app, limited app analytics and measurement of how our Google advertising performs, for caregivers after the sign-in or registration action (Section 4, "Advertising-effectiveness measurement in the Android app").
• Meta (Meta App Events) — in the Android app, measurement of how our Meta advertising performs, for caregivers after the sign-in or registration action (same part of Section 4).

Google Analytics, the Meta Pixel, and the Meta Conversions API are used on the kinstatus.app website. Google Analytics for Firebase and Meta App Events are used only in the KinStatus Android app, as described in Section 4. Google and Meta also process this information under their own terms and privacy policies.

Within your family group, information is visible according to role (Section 10). We disclose information beyond this only where necessary to comply with an applicable legal obligation, respond to a valid request from a public authority, protect someone's vital interests in an emergency, or establish, exercise, or defend a legal claim.

16. International transfers

Some of the service providers listed in Section 15 may process data outside the EU/EEA. Where this occurs, we are required to use a lawful transfer mechanism recognised under GDPR Chapter V for that transfer. Contact support@kinstatus.app if you would like information about the specific safeguard that applies to a particular provider.

17. How long we keep your data

We keep personal data only for as long as a specific purpose requires, or as long as the law requires:

• Last known location: kept until it is overwritten by a new location update or deletion is requested. Removing the Android location permission stops new updates but does not, by itself, delete a previously stored value.
• On-device pending-location queue: kept only on the protected person's device, capped at 200 readings, with readings older than approximately 23 hours eligible for removal.
• On-device diagnostic events: kept only on the protected person's device, capped at 200 entries.
• Location history: not applicable — KinStatus does not build one for your family to see.
• Unactivated invitation / pre-activation records: kept while the invitation is pending, and deleted if activation does not occur within a reasonable period, or on request.
• Temporarily stored raw invite code: cleared automatically once used; otherwise not retained beyond the invitation's validity.
• Check-in and status events, reminders, alerts, and last-activity data: kept for the life of the account, to provide the check-in history the service is built around, and deleted on account deletion subject to Section 18.
• Phone-health/permission-state snapshots: the most recent snapshot is kept to support diagnostics; it is replaced each time a newer snapshot is received.
• Push tokens: kept while the device or session is active, and removed on logout, revocation, or when reported invalid by the notification provider.
• Device sessions: kept while active; after revocation, retained only long enough to support a security investigation into that session, then deleted or anonymised.
• Security and abuse-prevention records: retained only as long as needed to detect and respond to abuse patterns, then deleted or anonymised.
• Audit records: kept for the life of the account, and for a further period afterward proportionate to accountability and the possibility of a legal claim, then deleted or anonymised.
• Trial and eligibility records: retained only as long as reasonably necessary to prevent repeated free trials and operate the eligibility mechanism, then deleted or anonymised when no longer needed, subject to any applicable legal or security requirements.
• Subscription records: retained as reasonably necessary to administer subscriptions, entitlements, refunds or revocations, disputes, security matters, and applicable legal obligations, and then deleted or anonymised when no longer required.
• Support, rights-request, and authorised-representative verification records: retained for as long as necessary to evidence that we handled your request correctly, then deleted or anonymised.
• Website connection/server logs: retained only as long as necessary for security and operational purposes, then deleted.
• Android app measurement records: the on/off setting stays on the device until the app is removed or the setting is changed; the server record of when a family's first phone connection was counted is kept for the life of the family and deleted with it. Information received by Google or Meta through this measurement is retained under their own settings and policies.
• Backups: KinStatus or its infrastructure/hosting providers may retain backup copies for operational continuity and disaster recovery. Deleted information may remain isolated in such backups until it is overwritten or removed under the applicable provider's process.

Where a fixed period is not stated above, we use objective criteria tied to the purpose, your account status, or a specific legal requirement.

18. Account and data deletion

You can request deletion of your KinStatus account and data from within the app (caregiver dashboard, profile section, "Delete account"), which takes you to our deletion request page, or by emailing support@kinstatus.app from the address linked to your account. See our Delete Account page for details.

We verify each request proportionately to what is being requested and who is making it — see Section 19. We assess deletion requests in accordance with GDPR Article 17 and delete the personal data for which the right to erasure applies. Because family members and a protected person may have their own independent rights in shared records, some data may require a record-by-record assessment rather than a single blanket action. Where we retain any data after your request — for example, because the law requires or justifies it — we will explain what is retained, why, and for how long.

We respond to your request without undue delay and, in principle, within one month of receiving it, as GDPR Article 12(3) requires. This period normally begins when we receive your request. Where we have reasonable doubts about your identity or authority, we may request proportionate additional information; if we do so without undue delay, the response period may be suspended until we receive the necessary information. For complex requests, we may extend the response period by up to two further months; we will tell you of any such extension, and the reasons for it, within the initial one-month period.

A protected person, or someone with legal authority to act for them, can contact support@kinstatus.app to access, correct, or request erasure of data about them.

19. Your rights

Depending on your relationship to KinStatus (Section 3) and the legal basis that applies (Section 5), you may have the right to: access your data (Art. 15); have it corrected (Art. 16); have it erased where the Article 17 conditions are met; restrict its processing (Art. 18); receive a portable copy of data you provided under a contract (Art. 20); object to processing based on our legitimate interests (Art. 21); and, where consent is the applicable basis, withdraw it at any time with effect for the future only (Art. 7(3)). To exercise any of these rights, write to support@kinstatus.app.

How we verify a request depends on who is asking: if you are a caregiver account holder or an invited helper, we normally verify a request by requiring it to come from the email address linked to your account. If you are a protected person with no KinStatus account email of your own, we use a method proportionate to how you are connected to the service, and we do not require you to go through a caregiver's account to exercise your own rights. If someone contacts us as an authorised representative of a protected person, we verify their authority to act before proceeding. Verifying identity or authority may require us to ask you for proportionate additional information.

We respond without undue delay and, in principle, within one month of receiving your request (Art. 12(3)). This period normally begins when we receive your request. Where we have reasonable doubts about your identity or authority, we may request proportionate additional information; if we do so without undue delay, the response period may be suspended until we receive the necessary information. For complex requests, we may extend this by up to two further months; we will tell you of any such extension, and the reasons for it, within the initial one-month period.

20. Complaints

You have the right to complain to a supervisory authority. In Bulgaria, that is the Commission for Personal Data Protection:

2 Prof. Tsvetan Lazarov Blvd., Sofia 1592, Bulgaria
Email: kzld@cpdp.bg
Website: www.cpdp.bg

You may also complain to the supervisory authority of your own country of residence within the EU/EEA.

21. The website

When you visit kinstatus.app, our website host and any security or operational services we use may process ordinary connection and server-log information — such as IP address, browser and device information, requested pages, and timestamps — to deliver and secure the site. Messages sent to our support address are processed by our support mailbox provider to handle your request.

On our pricing page we show prices in your local currency where we can. To do that, our server compares your IP address against a country database stored on our own server, at the moment of your request, purely to determine your country. Your IP address is not stored for this pricing lookup, is not sent to an external geolocation service for that lookup, and no browser geolocation permission is requested. We do not set a country cookie. The final price and currency you pay are always the ones shown by your app store.

The website also uses Google Analytics to understand how visitors use kinstatus.app, and Meta advertising-measurement technologies — the Meta Pixel and the Meta Conversions API — to measure how well our advertising works, for example whether a visit came from one of our ads. These technologies may use cookies or similar technologies and may process information such as the pages you visit, browser and device information, and your IP address. Google and Meta process this information under their own terms and privacy policies.

The website shows a consent banner with Statistics and Marketing categories, where you can make your choices and change them later. These website choices apply to the website only. The separate Google and Meta measurement in the KinStatus Android app, and how to turn it off, is described in Section 4.

22. Adults and legal capacity

KinStatus is intended for adults (18 and older) caring for adult loved ones. It is not directed at children and must not be used to monitor a child, or any person, secretly or without a lawful basis and that person's own knowledge and agreement (or, where a protected person lacks the legal capacity to agree for themselves, the agreement of someone with legal authority to act in their interest — a family relationship by itself does not create that authority). If you believe a child's data has been entered into KinStatus, contact support@kinstatus.app.

23. Security

We use technical and organisational measures appropriate to the data involved, including role-based access rules enforced at the database level (row-level security), pseudonymous hashes used to reduce exposure of raw technical identifiers, revocable device sessions, and access controls on our internal action log. We use encrypted connections for the services we operate. No online service can guarantee absolute security; please use a strong, unique password for your account.

24. Changes to this policy

We will update this policy as KinStatus develops, and we will change the "Last updated" date above when we do. Where applicable law requires advance notice of a change, we will provide it through a channel required or permitted by that law.

25. Contact

Email: support@kinstatus.app
Legal Notice: kinstatus.app/legal-notice/

Related pages: Terms of Use · Delete Account · Support