Kinstories Privacy Policy

Who is responsible for the data

The data controller is Artemijs Semjaņņikovs, self-employed, Latvia. Questions and requests about data — info@kinstories.app.

What data we process

• Account: name, email address; if you sign in with Telegram — your Telegram ID, name and username; passkeys — only the public part of the key and the device name.
• Circle data: what members add to a circle — people, birth dates and other events, places (optionally a map pin), contacts, relations, life path (education, work, places lived), stories, newsletter answers.
• Notifications: where to send them — email, Telegram (chat number), browser notification subscription.
• Technical data: sign-ins on devices (browser and system from the User-Agent header, sign-in time), IP address on sign-in attempts (to limit code guessing), the circle activity log and the server request log (for security and troubleshooting).

Data about other people

You can add relatives and loved ones who don't have an account. By adding a person you confirm that you may share this information with the circle members, and you add only what is appropriate for the family. If someone else added your data and you want it corrected or deleted — write to info@kinstories.app, we'll help.

Why and on what basis

We don't use data for advertising, don't sell it and don't share it for marketing.

• To provide the service (contract — these rules and the terms of use): account, circles, reminders, newsletter.
• Security (legitimate interest): protection against code guessing and abuse, logs, troubleshooting.
• Browser notifications — only after you allow them in the browser; you can turn them off in “Where to send”.

Where data is stored and who processes it

• Cloudflare — hosting, database, sending emails. Data may be processed in data centers outside the EU; Cloudflare applies the EU Standard Contractual Clauses and participates in the EU–US Data Privacy Framework.
• Telegram — if you connect Telegram: the bot's messages are delivered through it.
• Browser push services (Google, Mozilla, Apple) — deliver notifications to the browser; the notification content is encrypted.
• OpenFreeMap — map base layer: when a map is shown, the browser loads its tiles from their servers.

How long data is kept

• The account and circle data — as long as the account exists (circle data — as long as the circle exists).
• Sign-in attempts and codes — up to a day after the code expires.
• Device sign-ins — up to 90 days of inactivity, then up to 30 more days.
• The server request log — 30 days; it contains only the request address and field names, without the data itself.
• The circle change feed (“What's new”) — a year; it is deleted together with the circle.
• After an account is deleted, data is deleted immediately; it may remain in database backups for up to 30 days.

Your rights

You can: get your data (the “Download my data” button in “My settings → My data”), correct it, delete the account (in the same place), restrict or object to processing, get the data in a machine-readable form. For any request write to info@kinstories.app — we'll reply within a month.

If you believe we are violating your rights, you can complain to the supervisory authority — in Latvia it is Datu valsts inspekcija (dvi.gov.lv), or to the authority of your EU country.

Deleting the account

The account is deleted immediately in “My settings → My data → Delete account”. If you own a circle that has other members, transfer ownership first. Circles where you are the only member are deleted entirely. In shared circles people and stories remain — they are the circle's data; your account is unlinked from them.

Age

Kinstories is for people aged 16 and over. If you are younger, please don't create an account.

Cookies and browser storage

We use only necessary cookies: for sign-in (session) and for confirming the sign-in code in the same browser. Browser storage — for small interface settings. No analytics, advertising or third-party cookies, so there is no consent banner.

Changes

If the policy changes, we'll update the revision date on this page, and we'll announce important changes in advance — by email or in the app.