# KOGOTO Privacy Policy **Effective date: 2026-11-20. Version: 2026-11-20.** Replaces the version of 2026-11-06. Not reviewed by a lawyer (see Section 15). KOGOTO helps you meet people who are physically nearby. This policy explains, as accurately as the current app and backend actually work, what personal data KOGOTO processes, why, how long it is kept, and what rights you have. Where a legal question has not yet been confirmed by a lawyer, this policy says so instead of claiming compliance it cannot prove. ## Contents 1. [Who operates KOGOTO](#1-who-operates-kogoto) 2. [Contact](#2-contact) 3. [What data KOGOTO processes](#3-what-data-kogoto-processes) - 3.1 Account and sign-in · 3.2 Profile · 3.3 Stories · 3.4 Nearby · 3.5 Events · 3.6 KOGOTO Spots · 3.7 Announcements · 3.8 Spot Feed · 3.9 Creators · 3.10 Connection requests · 3.11 Chats and messages · 3.12 Voice messages · 3.13 Sharing a location · 3.14 Group chats · 3.15 Voice calls · 3.16 Blocking and reporting · 3.17 Notifications · 3.18 KOGOTO Reminders · 3.19 Language · 3.20 Product analytics · 3.21 Ambassador campaigns · 3.22 Website · 3.23 Security and technical data · 3.24 What KOGOTO does not collect 4. [Why KOGOTO processes data, and what is required](#4-why-kogoto-processes-data-and-what-is-required) 5. [Legal basis](#5-legal-basis) 6. [Who receives your data](#6-who-receives-your-data) 7. [International transfers](#7-international-transfers) 8. [How long data is kept](#8-how-long-data-is-kept) 9. [Your rights](#9-your-rights) 10. [Deleting your account](#10-deleting-your-account) 11. [Exporting your data](#11-exporting-your-data) 12. [Minimum age](#12-minimum-age) 13. [Security](#13-security) 14. [Changes to this policy](#14-changes-to-this-policy) 15. [Legal review status](#15-legal-review-status) ## 1. Who operates KOGOTO KOGOTO is operated by a private individual based in Austria, not a registered company. Contact for any privacy question or request: **kogoto2026@gmail.com**. The operator's full legal name and a postal address are not yet published; an Austrian provider information (Impressum) is therefore still incomplete. This does not affect your ability to contact KOGOTO, exercise your rights (Section 9) or delete your account (Section 10). ## 2. Contact For any question about this policy or your data: **kogoto2026@gmail.com**. ## 3. What data KOGOTO processes ### 3.1 Account and sign-in - First name, email address, password (stored only as an Argon2 hash; KOGOTO can never see or recover your password), date of birth (used to check your age; others only ever see your age, never your date of birth) and the **country you live in** (your current country of residence, not your country of birth). - Whether and when your email address was verified, and which version of the Terms of Service and Privacy Policy you accepted and when. - **Sign in with Google or Apple (optional).** The account identifier the provider gives you (an opaque id), the email address the provider confirms (with Apple this can be a private-relay address) and your name if the provider supplies it. KOGOTO verifies the provider's signed identity token, keeps **no** Google or Apple access token, and stores only the link between your KOGOTO account and that provider identifier. A returning Google or Apple user is always recognised by that identifier, so signing in again never creates a second account. You never have to use a provider sign-in; email and password are always available. - **Signing in on a new phone.** Your sign-in credentials are stored in your phone's protected storage (Keychain on iPhone, Keystore on Android) and are never moved to another phone. On a new phone you sign in again; the app then tells you which sign-in method your account uses, so you don't create a second account by mistake. ### 3.2 Profile - Bio, interests, your profile picture and any additional gallery photos you upload (up to 6). Photos are re-encoded and their metadata (including any location) is removed. - Your profile picture and gallery are visible to: your accepted connections and people with a pending connection request between you; people who find you in Nearby while your Nearby is on; people checked in at the same Spot at the same time; members of a group chat you are in (profile picture only); and people viewing a Spot review you wrote (profile picture only, Section 3.6). Never to someone you blocked or who blocked you, and not while your account is suspended. A photo you delete is no longer shown. ### 3.3 Stories - Photos and optional captions you post as Stories, visible only to your accepted connections and removed after 24 hours unless you keep a private copy in "Saved"/"Old Stories". - Who viewed or liked one of your Stories, and when — visible only to you. Viewing your own Story is not recorded. - If you mention an accepted connection in a Story, KOGOTO stores the mention and sends that person the Story photo as a message in your chat, with a notification. ### 3.4 Nearby - Whether Nearby is on and for how long. You choose each session's length (30 minutes, 1, 2 or 4 hours); it always switches off automatically, and you can turn it off at any time. There is no "always on". - While Nearby is on, your phone broadcasts a short-lived, random, regularly changing Bluetooth identifier. It contains no name, email or other personal information; only KOGOTO's server can link it to your account when another KOGOTO user with Nearby on detects it. Your phone also briefly reports ("encounter") that it detected someone, so both of you can see each other; these records expire after a few minutes. - **Nearby never uses GPS** and stores no geographic coordinates. Proximity is only ever shown as an approximate label (for example "very close"), never an exact distance. (The only time KOGOTO receives your geographic position is when you share a location in a chat yourself, Section 3.13.) ### 3.5 Events - If you join an Event (by its QR code or code), KOGOTO stores which Event, when you joined and until when (as long as the Event lasts, or until you leave). Some Events take place regularly (for example every Friday); each date is a separate Event, and joining one date does not join you to the others. - KOGOTO keeps the list of Events you joined while your account exists. It is not shown to others, is included in your data export and is deleted with your account. Past memberships are not currently deleted after a fixed period; if that changes, this policy will say so first. - Joining an Event never makes you discoverable by itself. It only lets other members of the same Event see you **while Nearby is on for both of you**. There is no member list. Joining an Event never adds you to its group chat. - Events are created only by KOGOTO or approved Creators and may show the organiser's name, a description and an image. ### 3.6 KOGOTO Spots - **Not active yet: profile pictures on reviews.** Until this is switched on, a review is shown with your first name only, without your profile picture (this also applies to Section 3.2). - **Visits.** If you join a Spot (a real place such as a café, bar, club, university or venue) by its QR code or code, KOGOTO stores which Spot, when you joined, until when (your choice, at most 24 hours) and, if you leave early, when. Others only see how many people are currently there, unless they are checked in at the same time. A finished visit is deleted 7 days after it ended; the Spot's visit total (a number not linked to you) is then increased by one. - **Following.** If you follow a Spot, KOGOTO stores that until you unfollow or delete your account. Following is always your own choice — never automatic, and separate from joining. Everyone sees a Spot's number of followers, never who follows. Following can subscribe you to the Spot's announcements (Section 3.7). - **First join.** The first time you join a Spot, KOGOTO records the date (kept while your account and the Spot exist) to show the Spot's welcome message only once, to know you have joined a Spot before, for the organiser's count of different visitors, and for Ambassador campaigns (Section 3.21). If the organiser set a welcome message, it is shown to you once, with the organiser's name and profile picture. - **Reviews.** If you review a Spot, KOGOTO stores your rating (1–5), any text and when. Your review is shown with your **first name and profile picture** to people viewing the Spot's reviews (never to someone you blocked or who blocked you). Changing or removing your profile picture is reflected there. You can edit or delete your review; it is deleted with your account. KOGOTO never posts anything to Google or another review site. - A Spot has no stored location coordinates. - Two people checked in at the same Spot at the same time can send each other a connection request without Nearby; this creates no proximity record. ### 3.7 Announcements - The organiser of a Spot or Event (KOGOTO or an approved Creator) can send announcements through KOGOTO: for a Spot to the people currently joined, its followers or both; for an Event to the people currently joined. - The organiser picks recipients from a list showing only each eligible person's **first name, profile picture**, a short identifier and whether they joined and/or follow — never email, phone number or other details. You are only listed while you are joined or follow, haven't switched announcements off and haven't blocked the organiser. - Switching off "Spot & Event announcements" in notification settings stops them completely (no push, no inbox copy). Eligibility is re-checked when each announcement is sent. - KOGOTO stores each announcement and your copy (and whether you read it) and deletes them after 90 days. ### 3.8 Spot Feed - A Spot's organiser can publish posts with text and images (metadata removed). Publishing doesn't notify anyone. - If you like a post, KOGOTO stores that and when; everyone, including the organiser, only sees the total number of likes. Unliking deletes the like. Liking never follows or joins the Spot. ### 3.9 Creators - KOGOTO may approve independent organisers as **Creators**, who manage their own Spots and Events in the Creator portal. Creators are not KOGOTO. - If you apply, KOGOTO stores your Creator status and its changes, which Creator Terms version you accepted and when, your last name and/or organisation name, a **phone number** (not verified; used only by the KOGOTO team to contact you, never shown to others) and a short description, the Spots, Events (including the schedule of regularly repeating Events) and images you submit, and an audit record of your Creator actions and of KOGOTO's moderation decisions. - A Creator account created in the Creator portal has no app profile: KOGOTO stores your name, email, password hash and the details above; your date of birth is checked for the minimum age but not stored. - KOGOTO emails you about your Creator account (codes and links, password resets, application decisions) through Brevo (Section 6). - In the Creator portal you can sign in with email and password or, where offered, Google or Apple — always the same KOGOTO account as in the app. - Creators see aggregate statistics for their content. The only individual people they see are the announcement recipient list (Section 3.7) and the first names and profile pictures in their Spot/Event group chats (Section 3.14). ### 3.10 Connection requests - Requests you send or receive and their status (pending, accepted, declined, cancelled or blocked), and any short "Ask" question and reply before accepting. An accepted connection is what KOGOTO calls a "Meetup". - **A pending request stays open until** the other person accepts or declines it, you cancel it, a block resolves it, or one of the accounts is deleted. (Before KOGOTO 1.2.2, requests expired after 30 minutes; such older requests remain marked "expired".) ### 3.11 Chats and messages - **Not active yet: "Delivered".** Until this is switched on, KOGOTO does not record when the other person's app loaded a one-to-one chat. "Seen" works as before. - The messages you send in a one-to-one chat with an accepted connection or in a group chat: text, photos you choose to send (including a "Meetup Souvenir" selfie), voice messages (3.12) and locations you choose to share (3.13); when each message was sent, delivered to the recipient's app and read; emoji reactions; and whether a message is a reply. "Delivered" means the other person's app has loaded the chat (one time per chat and person). - You can remove your own messages; a removed message becomes a "Message removed" placeholder without content. - **Editing and deleting (once switched on for your account):** you can change the text of your own message until the other person (in a group: any other member) has read it; the previous text is replaced and not kept, and the message shows "edited". Within 48 hours of sending you can delete your own message for everyone: its text, photo, voice message or location is removed from KOGOTO's servers (files are deleted) and a "deleted" placeholder remains so the conversation stays readable. Copies someone already made (screenshot, forwarding) cannot be removed. - **Delete for me:** hides any message only on your side; the other people still see it. KOGOTO stores that you hid it. - **Chats are not end-to-end encrypted.** Messages, photos, voice messages and shared locations are encrypted in transit between your phone and KOGOTO (HTTPS) and stored on KOGOTO's servers (Supabase, Frankfurt, Germany), where they are technically accessible. ### 3.12 Voice messages - KOGOTO uses your microphone **only while you record a voice message** — while you hold the record button or after locking the recording — for at most **60 seconds**. Your phone asks for microphone permission the first time. You can cancel before sending; nothing is uploaded until you send. - KOGOTO stores the recording (AAC audio), its length and a short volume outline for the waveform, in private storage (Supabase, Frankfurt). It has no public link: only the people in that chat can play it, and KOGOTO checks every time that they still belong to the chat. - Voice messages are not transcribed, analysed or used for anything except delivering them. ### 3.13 Sharing a location - **Choosing a place.** If you choose "Share location" in a chat, a map opens with a pin in the middle. If you already allowed location access, it starts at your current position (read once); otherwise nothing is asked until you tap "My location". You can move the map, search for a place or enter coordinates; only the place you then send is shared, as one pin (latitude and longitude, rounded to about 1 metre). Everyone in that chat can see it. - **Map and address services.** The map images come from **OpenFreeMap** (`tiles.openfreemap.org`), which receives your IP address and the map area shown. The address under the pin and the place search use your phone's own geocoding service (Google on Android, Apple on iPhone), which receives the point or the search text. KOGOTO sends neither of them any account data. - Location permission is requested only at that moment ("while using the app"; never "always"). There is **no live location, no location history, no background tracking and no automatic sharing**. - Opening a pin in a maps app (Apple Maps, Google Maps or a browser) is your choice; that app then receives the coordinates under its own policy. ### 3.14 Group chats - **Only by your own choice.** Choosing people when creating a group, or adding them later, sends them an invitation in the app. Nobody becomes a member without accepting it: until then other members see nothing about them, and they can decline. Joining any group (also by link or as a Spot or Event group) needs an app version that has shown you this policy. - **Private groups.** You can create a group with people you are connected with. Admins can add connections, remove members, make others admins and create an invite link or QR code; anyone with the current link can join, and a new link stops older ones working. KOGOTO stores the group's name, optional description and picture, its members, their role, when they joined, whether they muted the group and when they last read it. - **Spot and Event groups.** A Spot or Event can have a group chat. Only people who joined that Spot or Event can take part, and only if they choose to join the chat themselves — joining a Spot or Event never adds you to it. If you are no longer eligible, you are removed and get no more notifications. An Event's group stays available to its members after the Event ends. - **What other members see:** your first name, your profile picture (not if one of you blocked the other), your role, when you joined, your messages in that group, and read status only as an aggregate. Never your email. - You can leave a group at any time. Your messages stay for the remaining members (you can remove them yourself). When the last member leaves, the group and its content are deleted. Groups have at most 75 members. ### 3.15 Voice calls - **Only between connected people, only when someone calls.** You can call a connection from a one-to-one chat (once calls are switched on for both of you). KOGOTO never calls on its own and never listens in. - **Microphone.** The app asks for microphone access the first time you start or answer a call and uses it only during a call. - **How the audio travels.** The audio goes directly from phone to phone (WebRTC), encrypted in transit (DTLS-SRTP). KOGOTO's server only passes on the technical connection setup (network addresses and session parameters); it receives no audio and **no call is recorded**. If no direct connection is possible, the encrypted audio may be relayed through a relay server (TURN) that cannot read it. KOGOTO does not call this end-to-end encryption: the keys are agreed between the two phones, but that setup passes through KOGOTO's server. - **Your IP address.** With a direct connection both phones learn each other's IP address and port, as with any internet call. A network helper service (STUN, run by Cloudflare) sees your IP address when a call is set up. - **What KOGOTO stores.** Who called whom, when, whether the call was answered, missed or declined, and how long it lasted; a short line appears in the chat. The connection setup data is deleted one hour after the call, the call details after 30 days; the line in the chat stays as long as the chat. - **Ringing.** So that your phone can ring, KOGOTO stores which of your app installations can receive calls: an installation ID, its push token (on iPhone also a call push token), the platform and the app language. They are deleted when you sign out or delete your account, or after 60 days without use. Calls arrive as push notifications through Google Firebase and Apple's push service. On iPhone the call appears in the system call screen (CallKit); KOGOTO calls are not added to the phone's recent-calls list. ### 3.16 Blocking and reporting - Who you blocked (private; the person is never told). A block applies to Nearby, connection requests, one-to-one chats, Stories, reviews and Spot announcements. In a group chat you both belong to, you don't see each other's messages or profile picture and cannot add each other; a member who blocked, or was blocked by, a Spot's or Event's organiser cannot use its group. - Reports you file, with the category and any description. Reports are confidential: only KOGOTO's operator sees them, and the reported person is never told who reported them. - KOGOTO's administrators can moderate Spot/Event content and keep an audit record of moderation and admin actions. ### 3.17 Notifications - If you allow notifications: your device's push token, the app language of that device and your notification preferences (requests, messages, Stories, Spot & Event announcements, message previews). - **What a notification contains.** A chat notification contains the sender's first name, a short generic text in your language ("New message", "Sent you a photo", "Sent you a voice message", "Shared a location") and internal identifiers; a group notification also contains the group's name. It is delivered through Google Firebase Cloud Messaging (on iPhone handed to Apple's push service). A reaction notification contains the person's first name and the emoji. A group you muted sends you no notifications. - **Message text previews are off unless you turn them on**, and KOGOTO currently keeps previews unavailable for everyone, so no notification contains message text. - **Sender's picture.** A chat notification can show the sender's profile picture. The picture is not sent through Google or Apple: the notification carries only a temporary token (2 hours, for this sender and you only), and your phone downloads a small copy directly from KOGOTO, which first checks that you may still see that picture. - On Android, message notifications are marked private so a locked screen can hide them; on iPhone this depends on your settings. - For each announcement sent to you, whether its push was accepted for delivery (for aggregate delivery counts only). ### 3.18 KOGOTO Reminders (optional, off by default) - If you switch on KOGOTO Reminders (with or without an account), KOGOTO stores a random identifier for your app installation (only its hash), its push token, platform, app language, time zone, app version, when you last opened the app, how many reminders were sent and when, and, if signed in, a link to your account. It is used only to send **at most two** reminders after a period without use (after 14 and 30 days, on a Friday or Saturday evening). Never by email. - Switching Reminders off deletes this data. Otherwise it is deleted with your account or after 180 days without the app being opened. Daily counts not linked to anyone are kept for 400 days. ### 3.19 Language - The app language you choose (English, German, French, Spanish, Italian, Portuguese, Arabic or Japanese) is stored on your device, and with your push token so notifications arrive in your language. In the Creator portal it is stored with your account for Creator emails. It is never shown to others. ### 3.20 Product analytics - A small, fixed set of usage events tied to your account: opening the app; turning Nearby on or off; joining or leaving an Event; joining, leaving, following or unfollowing a Spot; the Meetup request, accept, decline, confirm and cancel steps; and whether a push notification succeeded. - Stored only in KOGOTO's own database. **No third-party analytics or advertising SDK is used.** The events contain no message or Story content, no location, no email and no raw Bluetooth, push or advertising identifier. - They are read mainly as aggregates and never used for advertising. One exception: Ambassador campaigns (Section 3.21). They are deleted with your account. ### 3.21 Ambassador campaigns - **Current status.** Approved Creators ("Ambassadors") can promote one of their Spots for a fixed fee for agreed content. The **individual attribution and evaluation of new users described below is not active.** If KOGOTO switches it on, it applies only to people who register afterwards with an app that showed them this disclosure at sign-up — never to earlier accounts, never to people under 18, never to earlier activity. - **How it would work.** A campaign can add a capped bonus for genuinely active new users. You can be credited only if you created your account during the campaign and your first join of its Spot happened during the campaign and within 7 days of registering (at most one campaign ever). To decide whether you count, KOGOTO evaluates, individually for you, your own events from your first 14 days: how often and on how many days you opened the app (at least 5 times on 3 different days, at most 3 counted per day), whether you turned Nearby on, whether you follow the Spot, and whether your account is active, verified and not suspended. Only the result is stored. Joining a Spot is never treated as proof that you were physically near anyone. - The Ambassador sees totals (credited, qualified, not counted yet) and the bonus only once at least 5 people were credited, and the exact totals after the campaign ends (in a small campaign, an Ambassador who invited you may be able to tell whether you counted). They never see who you are or your activity. No referral link, device identifier or IP check is used. - You can **object at any time** without giving reasons by email to kogoto2026@gmail.com; you are then never credited and an open entry is closed without further evaluation. - If you delete your account, the entry loses its link to you and remains only anonymously for payment accounting. As an Ambassador, KOGOTO stores your campaigns, the agreed terms and the payment records (not your payment details). ### 3.22 Website (kogoto.app) - The website is served by Cloudflare, which processes your IP address and request data to deliver and protect the pages. It sets no cookies and stores nothing in your browser. It uses Cloudflare Web Analytics (page views, referrers, browser/device type, speed; no cookies or fingerprinting according to Cloudflare) and KOGOTO's own campaign counter (the campaign source in the link you opened, the page, device and OS type, event type). None of this is linked to a KOGOTO account. ### 3.23 Security and technical data - Standard request and error logs of KOGOTO's hosting provider and backend. KOGOTO's own code does not log passwords, tokens, codes or message content. - App crash diagnostics (Google Firebase Crashlytics): stack trace and device, OS and app version only — never a user identifier. - Abuse protection: counters keyed by email address or, for the web portals, IP address, kept about 7 days. - **Backups:** once a day an encrypted copy of the database and stored files is made (by an automated job on GitHub's servers) and stored, encrypted before it leaves the job, in Cloudflare R2 in the EU — daily copies for 35 days, monthly copies for 13 months — only to restore the service. ### 3.24 What KOGOTO does not collect KOGOTO does **not** collect: your location (except a location you choose to share in a chat, Section 3.13), your phone number (except in a Creator application, Section 3.9), your contacts, SMS or call logs, or any audio other than a voice message you record and send. Call audio goes between the phones and is neither received nor recorded by KOGOTO (Section 3.15). ## 4. Why KOGOTO processes data, and what is required Email, password, first name, date of birth and country are required to create an account; Nearby, chats, Stories, Spots and Events need the data described for them to work. Bio, interests, extra photos, Stories, voice messages, location sharing, group chats and Reminders are optional and used only when you choose them. ## 5. Legal basis *Candidate legal bases under the GDPR — **not yet confirmed by a lawyer**.* - **Contract (Art. 6(1)(b))**: account, profile, Nearby, Events, Spots (including following and reviews), connection requests, chats, voice messages, location sharing, group chats, delivered/read status, voice calls, editing and deleting messages. - **Legitimate interest (Art. 6(1)(f))**: security logs, abuse prevention, reporting/blocking/moderation, crash diagnostics, aggregate product analytics, backups, website analytics, the 7-day retention of finished Spot visits and — only if switched on — the Ambassador evaluation (Section 3.21; KOGOTO weighed it against your interests: few records, only from your first 14 days, only the result kept, no effect on your use of KOGOTO, never for minors, objection possible at any time). - **Consent (Art. 6(1)(a))**: push notifications (your phone's permission and the in-app switches), message previews, KOGOTO Reminders. You can withdraw consent at any time. - **Ambassador contracts and payment records**: contract with the Ambassador (Art. 6(1)(b)) and legal obligations (Art. 6(1)(c)). ## 6. Who receives your data KOGOTO does not sell your data and shares none with advertisers or data brokers. These providers process data on KOGOTO's behalf: | Provider | Purpose | Data | |---|---|---| | Render (Frankfurt, Germany) | Backend hosting | All data passing through the backend | | Supabase (Frankfurt, Germany) | Database and private file storage | Account, profile, messages, photos, voice messages | | Cloudflare | Network/security layer, web portals, kogoto.app website and analytics, encrypted backup storage (EU) | IP address and request data; website counts; encrypted backups | | GitHub (Microsoft) | Runs the daily backup job | The data being backed up, only during the job | | Google Firebase | Push notifications; crash diagnostics | Push token and notification content (Section 3.17); crash data without user identifiers | | Apple Push Notification service | Delivers notifications to iPhones | Push token and notification content | | Brevo | Transactional emails (codes, password resets, Creator emails) | Email address and email content | | Google / Apple sign-in | Optional sign-in | Provider identifier, email and name from the identity token | | Cloudflare (STUN; TURN only if switched on) | Setting up voice calls; relaying encrypted call audio when no direct connection is possible | IP address and port; encrypted audio it cannot read | | Apple Push Notification service (calls) | Making iPhones ring for a call | Call push token, caller's first name, call ID | | OpenFreeMap | Map images for shared locations | IP address, map area shown | | Google (Android) / Apple (iPhone) geocoding | Address of a chosen point and place search when sharing a location | The point or the search text, IP address | ## 7. International transfers KOGOTO's backend, database and file storage run in Frankfurt, Germany (EU). Several providers are based in, or use staff or sub-processors in, countries outside the EEA, mainly the USA: - **Render** (USA): EU-U.S. Data Privacy Framework (as stated by Render) and Standard Contractual Clauses (SCCs). - **Supabase** (Singapore/USA): data stays in Frankfurt; support, logs and administration can involve Singapore and the USA (SCCs). - **Cloudflare** (USA): SCCs (and the Data Privacy Framework where certified); backup storage restricted to the EU. - **Google, Apple, GitHub**: under their data processing terms (Firebase including SCCs). - **Brevo** (France): EU. These statements reflect the providers' own information; KOGOTO has not yet checked each provider against the official Data Privacy Framework list. You can request a copy of the safeguards (Section 2). ## 8. How long data is kept Most data — profile, photos, messages, Nearby/Event/Spot state, analytics events — is kept while your account exists and deleted when you delete it (Section 10). Specific periods: - **Spot visits:** while active; finished visits 7 days after they end. First joins: while your account and the Spot exist. - **Event memberships:** while your account exists. - **Pending connection requests:** until they are answered, cancelled, resolved by a block, or an account is deleted. - **Chat photos and voice messages:** while your account exists. - **Announcements:** 90 days. - **Sign-in sessions:** until they expire or you sign out (expired ones are removed after about 90 days); codes and abuse counters: about 7 days. - **Notification picture tokens:** valid 2 hours, not stored. - **KOGOTO Reminders:** see Section 3.18. - **Ambassador campaigns:** as long as needed to calculate, review and document the payment, and as long as the law requires business records (in Austria generally seven years; not yet confirmed by a tax adviser). - **Backups:** deleted data can remain in encrypted backups until they expire (35 days; monthly copies 13 months); they are used only to restore the service, and restored data is deleted again under these rules. - **Earlier database copy (Ireland).** When KOGOTO moved its database to Frankfurt on 23 October 2026, the previous database (Supabase, Ireland, EU) was kept unchanged as a fallback. It is not used by the app and only the operator can access it. It contains the data as it was on that date, including accounts deleted since; deletions made after that date are not reflected in it. KOGOTO will delete this copy and will then remove this paragraph. - **Voice calls:** connection setup data 1 hour after the call; call details 30 days; the call line in the chat as long as the chat. - **Call-capable devices:** until you sign out or delete your account, at most 60 days after last use. - **"Deleted for me" markers:** as long as the message exists. ## 9. Your rights Under the GDPR you may have the right to **access** your data (Section 11), **rectify** it (most profile fields in the app), **erase** it (Section 10), **restrict** processing, **data portability** (Section 11), **object** to processing based on legitimate interest — in particular the Ambassador evaluation, at any time and without reasons — and **withdraw consent** at any time without affecting earlier processing. Contact kogoto2026@gmail.com. KOGOTO may need to verify that you are the account holder. You can also complain to a supervisory authority; in Austria the **Österreichische Datenschutzbehörde** (https://www.dsb.gv.at). ## 10. Deleting your account **Settings → Delete account** (with your password, or by signing in again with Google or Apple) immediately signs you out everywhere, stops Nearby and Bluetooth, removes your device from notifications, and deletes your profile, photos, Stories, connections and requests, messages (including voice messages and shared locations), Nearby state, Event memberships, Spot visits, follows, first joins and reviews, blocks, reports you filed, Reminders data and analytics events. In group chats your messages become "Message removed" placeholders without content and you are removed from all groups. An Ambassador entry loses its link to you. Backups expire as in Section 8. Deletion cannot be undone. ## 11. Exporting your data **Settings → My Data & Privacy → Download my data** gives you a machine-readable (JSON) copy: your profile, gallery and Stories metadata, connections, messages you sent (with their type: text, photo, voice, location, and the locations you shared), blocks and reports you filed, notification settings, current and recent Spot visits, followed Spots, first joins, your reviews, the Events you joined, and any Ambassador entry or campaigns. It never contains your password hash, tokens, other people's private data, or who reported you. ## 12. Minimum age You must be at least **16 years old**; this is checked in the app and, independently, by KOGOTO's server. KOGOTO does not knowingly collect data from anyone under 16. People aged 16 or 17 are never credited to Ambassador campaigns. See also KOGOTO's Child Safety Standards. ## 13. Security Passwords are hashed with Argon2; sign-in sessions, verification and reset codes are stored only as cryptographic hashes. All app–server communication uses HTTPS. Photos and voice messages are kept in private storage that is served only through KOGOTO's permission checks. Backups are encrypted before they leave the backup job, with a key only the operator holds. Notification picture links are signed, limited to one sender and one recipient, and expire after 2 hours. Chats are **not** end-to-end encrypted (Section 3.11). KOGOTO's hosting and storage providers apply their own security controls, which the operator has not independently audited. ## 14. Changes to this policy If this policy changes in a way that materially affects how your data is processed, KOGOTO updates the version above, makes the new version available in the app and at the public link, and informs users (for example by email or an in-app notice). This policy informs you; it is not something you agree to. Where KOGOTO relies on consent, it asks separately, and using KOGOTO is never treated as consent. **2026-11-20 (KOGOTO 1.3.0):** voice calls (Section 3.15); editing and deleting messages (3.11); choosing a place on a map, map images from OpenFreeMap and the phone's geocoding service (3.13); new recipients (6) and retention periods (8). These functions are switched on step by step and may not yet be available for every account at publication. **2026-11-06 (KOGOTO 1.2.2):** voice messages (microphone only while recording, at most 60 seconds); one-time location sharing in chats; private, Spot and Event group chats; delivered/read status; profile pictures on Spot reviews; pending connection requests no longer expire; KOGOTO Reminders (optional, off by default); Arabic and Japanese; regularly repeating Events; chats are not end-to-end encrypted (stated explicitly); guidance when signing in on a new phone. Not active at publication: location sharing, "Delivered" and profile pictures on reviews. Earlier versions: 2026-10-31, 2026-10-19, 2026-10-05, 2026-09-23, 2026-09-03, 2026-08-30 (change log available on request). ## 15. Legal review status This policy was prepared to describe KOGOTO's real technical behaviour accurately, but it has **not** been reviewed or approved by a qualified data-protection lawyer, and KOGOTO does not claim it is complete or legally sufficient for every jurisdiction. The translations of this policy are unreviewed; the English version applies.