KODKOD Privacy Policy
This policy covers the KODKOD service: the KODKOD app for Android and for iPhone and the servers they connect to. It describes what information is collected and processed, why, what is kept on your phone and what on our servers, who can see it, which service providers receive it, how long it is kept, how to withdraw a consent and how to delete it. Where the two apps behave differently, the text says so ("Android" or "iPhone"); everything else applies to both. The Hebrew version is at /privacy. The app's interface is in Hebrew, and Hebrew labels are given in brackets below.
Account deletion: delete your account in the app, or without it by following the account deletion page. See also section 9.
What is new in version 1.6 (compared with 1.4, the version in force):
- The iPhone app is covered: its notifications (through Expo and Apple), Apple's Push to Talk for background playback, and the iPhone's Talk and Action buttons (section 3.7, section 3.16, section 3.3).
- What is kept on your phone, and what is removed from it on sign-out and on account deletion (section 3.17).
- The diagnostic file you can choose to send, on Android and on iPhone (section 3.18).
- Silence, Do Not Disturb and Focus: what is read on the phone and what the server is told (section 3.19).
- Google Gemini and your consent: only in an organization's groups, never in private conversations; each person decides for their own content, enforced by who wrote it (section 3.5, section 6).
- Withdrawing consent: what you can turn off, where, and what happens to information already collected (section 10).
- Capabilities added since 1.4: "last seen" (section 3.13), forwarding (section 3.14), Bluetooth devices in silent mode on Android (section 3.15), and, in organizations, what administrators see, temporary membership and positions (section 5).
- The operator: Yair Maimon, a private individual (section 1, section 14).
1. Who we are
KODKOD is a push-to-talk group communication app for teams and organizations. You hold a button and talk; the members of your group hear you and can also read a transcript.
KODKOD is operated by Yair Maimon, a private individual, the operator of KODKOD ("we"), who is the controller of the information; identification number 043425081, official address: Ma'ayanot 507, Tekoa, Israel. Privacy contact: support@kodkod-hub.com.
KODKOD is not an emergency service and does not replace official emergency numbers. We do not guarantee that every message, notification, transcript or location will be delivered.
2. Scope
This policy covers the KODKOD app for Android and for iPhone, and its servers. Organizations that use KODKOD can also use web consoles, including the control room (Control). Authorized staff of an organization see some information in those consoles, as described in sections 5 and 7.
3. Information we collect
3.1 Your account
- Phone number (required). You sign in with it: we send a one-time code to it by SMS.
- Display name (required). It is shown to the people you communicate with.
- Profile picture and call sign (optional).
- If you join an organization: your membership, and any teams or labels the organization assigns to you.
We do not ask app users for an email address or a password, and there is no sign-in through Google, Apple or any other account.
3.2 Contacts (optional)
If you allow access to your contacts, the app reads your phone's address book. It does this to show which of your contacts already use KODKOD, to show familiar names on messages, and to let you invite people or share a contact.
- Sent to our server: the phone numbers in your address book, so we can check which ones belong to KODKOD accounts. They are encrypted in transit but not hashed. The check repeats from time to time while you use the app (for example, when you return to it) to keep the list current.
- Stored on our server: only the link between your account and the KODKOD accounts found among your contacts. Numbers that do not belong to a KODKOD account are not stored.
- Not sent: your contacts' names, photos and other address-book fields. They stay on your phone.
- If you share a contact in a conversation, that contact's name and phone numbers are sent as a message, and the conversation's participants see them.
Before your phone asks for the permission, the app explains what is sent to the server and what is kept. You can revoke the permission at any time in your phone's settings (section 10).
3.3 Microphone and push-to-talk (PTT)
- The microphone is on only while you transmit. That is:
- while you hold the talk button on the screen;
- while you press a hardware key or a headset or accessory button that you set up for transmitting (headset and accessory transmission is off until you turn it on in the app's settings);
- on iPhone, also when you start a transmission from the system's Talk button (on the lock screen or in the Dynamic Island) or with the Action button or a Shortcut, which start and stop a transmission to your locked recipient;
- during a hands-free lock, and in any case every transmission stops by itself after 60 seconds;
- while you record a voice message;
- while you record a video.
- Receiving is not recording. When the app is ready to receive transmissions, including in the background and with the screen off, it plays what others transmit. The microphone stays off and nothing is recorded.
- Every transmission is saved as a voice message. This includes live transmissions of at least 0.2 seconds. Each one is stored on our server and transcribed. Conversation participants can play it back. In an organization's group, the organization's authorized staff can play it back too (section 5).
- To keep working with the screen off, the Android app may show an ongoing notification during a transmission, in a direct call, or while receiving in the background. On iPhone, the system shows its own Push to Talk interface and audio indicator instead.
3.4 Messages and media
We store what is sent and created in conversations:
- text, voice messages, photos, videos and files (including the file name);
- shared contacts and shared locations;
- reactions and acknowledgements;
- whether a message was played or read.
We remove embedded metadata, such as GPS tags, from photos and videos before storing them.
3.5 Transcription and automated processing (AI)
- Transcription (Android and iPhone). Every voice message and every transmission is sent to a speech-recognition service. To recognize names, the service also receives the names and call signs of the conversation's participants and place names in the group's area. The transcript is stored with the message.
- Google Gemini and your consent. The AI analysis described in the next three items (urgency and places, summaries and digests, control room) is done with Google's Gemini API. Whether your content may be sent is your own decision, and our server enforces it for each person, by who wrote the content. The app works fully either way.
- Only in an organization's groups. Private conversations (between two people) and groups that do not belong to an organization are never sent to Gemini, on Android or on iPhone: not for urgency and place analysis, not as context and not for summaries. There, urgency is decided on our server, summaries are built on our server from quotes, and places are found only when written exactly. Groups of an organization we marked "may include minors" are not sent to Gemini either (section 12).
- Where you are asked (iPhone): once, on the last page of the setup wizard the first time you sign in, and at any time in Settings → Account → Privacy → AI (Google Gemini) (הגדרות ← חשבון ← פרטיות ← בינה מלאכותית (Google Gemini)). The screen names the provider (Google), the purposes and what is sent, with two equal buttons, "I agree" and "Not now", and nothing selected in advance. "Not now", or closing the screen, is recorded as not agreeing. We record your decision, its time, the version of the text, the platform and the app version.
- What is sent if you agree: the text of your messages and the transcripts of your voice messages, captions, file names, the name on a contact card you share (not its numbers), the fact that a location was shared (not its coordinates), your name and call sign, group and organization names, urgency marks and acknowledgements, and times; in an organization's groups, recent messages from the same group as context. Never sent to Gemini: recordings, photos, videos, file contents, phone numbers or coordinates.
- Decided by the author, not by who asks. Our server checks the consent of everyone who wrote the content — the sender, the person whose device spoke it, and the original sender of a forwarded copy — at the moment of each call to the model. A request by someone who agreed (refreshing a summary, a control-room question, an automatic scan) never brings in content of someone who did not.
- If you have not agreed, nothing of yours is sent to Gemini in any path: not for the urgency and place analysis of your own messages, not as context for other people's messages, not in conversation summaries, incident cards or digests, not in the control room's situation picture, questions or incident-board summary, and not to its report classifier — and neither your name nor your call sign. This applies in every organization's group, also when people in it agreed. Where an incident depends on your message, its card is built on our server from quotes, without a model.
- How urgency is recognized without the model. For a message of someone who has not agreed, urgency is decided on our server, with no third party: from keywords and from the sender's own emergency mark. These methods miss some distress messages, especially when distress is described indirectly, and keyword matching also raises some false alarms. They are not equivalent to the AI analysis, and their accuracy on real traffic has not been measured.
- Who is asked now (the transition): on iPhone, your content is sent to Gemini only after you agree. The Android app does not ask for this consent yet, and Android users have not given it: accepting the terms of use is not consent to this analysis. Until the Android app asks, the content of Android users who have not answered is analysed by Gemini as described in this section, on the basis of this notice only.
- Withdrawing: at any time, on the same screen in Settings (iPhone). New sends stop immediately: from the next call to the model nothing of yours is sent, and AI content disappears from your phone. We then delete what the model produced from your messages and kept in KODKOD: the model's wording of a message's urgency, the event label on the map, the short title of a control-room report, and the places found in your messages (places stated exactly, such as a road and a kilometre, are rebuilt without the model for messages of the last 24 hours); incident cards and digests of every conversation in which you spoke are deleted and rebuilt without you. Kept: each message's urgency level and its source, and the "correction / ended" marks on the map, because deleting them could bring back emergencies that were already closed; and transcripts, which are not made by Gemini.
- What was already sent cannot be recalled. Content sent to Google before you withdrew, or before you were asked, stays with Google under its terms; KODKOD can delete only what KODKOD keeps. On the paid tier Google keeps logs for a limited time only to detect abuse; it does not publish the number of days, and its terms offer no way to ask for a particular request to be deleted.
- Paid tier only. We use Gemini only on Google's paid tier. There Google processes the data as our provider under its data processing terms, does not use prompts or responses to improve its products, keeps logs for a limited time only to detect abuse, and may store data temporarily in any country where it has facilities.
- Urgency and places. The text or transcript of a message, together with recent messages from the same conversation, is analyzed by an AI model. The model estimates urgency and identifies places that were mentioned. This applies only to an organization's groups, not to private conversations.
- Summaries. An AI model produces short summaries of an organization's groups and of urgent incidents in them. In private conversations and other groups the summary is built on our server, without a model. For this it receives the message text, transcripts, and participants' names and call signs.
- Control room. In an organization's groups, messages are analyzed automatically. The analysis identifies field reports, builds a situation picture and answers questions from control-room staff. Private conversations are not processed for this.
- Address lookup. A place name found in a message, in a group and in a private conversation, may be sent to an address-lookup service (Esri). Only the place name is sent, without your name or your location.
AI output is an aid and can be wrong. We do not use it for decisions that have a legal or similarly significant effect on you. Transcription is part of how the service works and has no separate switch; analysis by Gemini depends on your consent (above).
3.6 Location (optional)
Location permission is optional, and the app works without it. On both Android and iPhone the app asks for location only while in use. It never asks for "always" (background) location permission. Before your phone asks for the permission, the app explains what location is used for and who sees it. If you allow it, your precise location is used as follows.
- Where a message was sent from.
- When you send a message, the app attaches the location your phone already knows, if it is from the last few minutes and accurate enough.
- This applies to messages in groups, including live transmissions (even from a hardware key, the lock screen, or the iPhone's Talk or Action button). No location is attached in private conversations, unless you deliberately send one with "Send location".
- The app does not start a new location fix for this.
- The location is stored with the message and never changes. Participants in the conversation can see it.
- Your current position, if you belong to an organization.
- While the app is open and in use on the screen, it reports your position from time to time, at most about once a minute.
- Sending a message does not update your current position: the location attached to a message belongs to that message only.
- Group map. When you open the map of an organization's group, your position is reported to that group. Group members who open the map can see it.
- Location requests from the control room. Authorized staff of your organization can request the current position of its members. The app answers automatically, without asking for approval, so as not to delay operations. When a position is sent, the app shows a short line: "the organization's control room asked for your location, and it was sent" (at most once every ten minutes, with no sound). If no position is available, the app reports that to the control room.
- What you choose to share: a location you send in a conversation (measured fresh when you send it), and marks you place on a shared map.
Maps. Map images load directly from Esri's map servers to your phone. Esri therefore receives your phone's IP address and the map area being viewed.
Who sees your location is described in section 5 and section 7.
3.7 Notifications
If you allow notifications, we store your phone's notification address (a "token") with your session. A message notification contains:
- the conversation name;
- the sender's name;
- a preview of up to about 120 characters of the text or transcript.
- Android: your phone is registered with Google Firebase Cloud Messaging, and notifications pass through Google's notification service.
- iPhone: your phone is registered with Expo's notification service, which obtains an address from Apple. Notifications pass from our server through Expo and then through Apple's Push Notification service, so both receive the content above.
A notification may appear on your lock screen, depending on your phone's settings. On Android, boost and emergency notifications are set to appear in full on a locked screen. On iPhone, the phone's own "Show Previews" setting decides. The app has no setting today to hide message previews. In the app you can choose when to be notified (section 10); emergency messages always arrive.
3.8 Device, security and usage information
- A random installation ID that the app creates, and a device key that our server stores only as a hash. We do not read the IMEI, serial number, Android ID, Apple's advertising identifier (IDFA) or any other advertising ID. On iPhone the installation ID is kept in the iPhone's Keychain, and may remain there after the app is removed (section 3.17).
- Version information: the app version, build number, platform and OS version. They are sent with each request.
- Sign-in and security records: the event and its outcome, IP address, client type and installation ID.
- Usage and diagnostic records: which actions were used, when, whether each request succeeded and how long it took, and server errors. They are linked to your account and contain no message content.
- When the app last contacted the server: we keep the time of the app's most recent request to the server (at most once every five minutes), with the device type and app version of that request. Such a request also happens in the background, without you opening the app, so this does not mean you were active. It is shown to our system administrators and to your organization's administrators (section 5). It is different from "last seen" in section 3.13.
The app has no ads, does not track you across other companies' apps or websites, and has no third-party analytics or crash-reporting tools.
3.9 Information about other people
Messages may mention other people. Control-room staff may record details of someone reporting an incident, such as a name and phone number. Please share only what the operation needs.
3.10 What we do not collect
We do not read your SMS messages, calendar or list of installed apps. We do not collect an advertising ID. The app has no in-app purchases, so we collect no payment details. We do not ask for a date of birth or an ID document.
3.11 What is required and what is optional
A phone number is needed to open an account and sign in. Everything else is optional: without microphone permission you cannot record or transmit; without location permission no location is attached to messages, none is reported to an organization or the maps, and you cannot send a location; without contacts permission the app cannot show which of your contacts use KODKOD, and you can still use it; without notification permission no notifications arrive while the app is closed. Before asking for microphone, location and contacts permission, the app explains what is collected and why.
3.12 Blocking and reporting
- Blocking: you can block a user, also before any conversation with them (from a member list, from your contacts or by phone number; a number that is nobody's is not kept). We keep who blocked whom and when. A block stops, in both directions, messages, voice messages, live transmission, boosts and likes in that direct conversation only, and no notifications are sent from it. Nothing changes in groups you already share or in organization groups, emergency messages included, but the blocked user cannot add you to a group. The blocked user is not told. The conversation's history stays and is not deleted.
- Reporting: you can report a user or a message. When a message is reported, a copy of that message only is kept: its kind, its text or transcript, the id of its attached file and when it was sent. The location attached to the message is not kept in the report. With the report we keep who reported, whom, the category chosen and a note, if one was written. We do not read other conversation content for reports, and we do not monitor conversations.
- Who sees a report: only KODKOD's system administrators. Organizations do not see reports. Every view of a report and every change to its status is recorded in the audit log. Reports are reviewed with an internal target of 48 hours, the most severe first. A reviewer can remove a reported message for everyone in its conversation.
- Filtering on iPhone: the iPhone app does not send a typed message that contains a term from a short list of offensive words; the words are not recorded anywhere. Received messages that may be offensive, and group messages from someone you blocked, are hidden until you tap to show them. Voice messages, live transmissions, photos, videos and files are not filtered.
3.13 "Last seen" — last activity in the app
- What is collected: while the app is open and showing on your phone's screen, it tells the server it is in the foreground (an x-app-active header on requests, and a short frame on the open connection). The server keeps a single value: the time of the latest such signal. Every new signal overwrites the previous one; there is no history, and we do not record when you opened or left the app. At most one signal a minute is kept.
- What does not count as activity: what the app does in the background (syncing, waking for a notification, acknowledging from the lock screen), receiving transmissions with the screen off, and activity on an organization's tablet. Your location is never used in any calculation of activity.
- Who sees it: only the other person in an accepted private conversation with you (not a conversation request that has not been accepted, and not when either of you has blocked the other), and only as a coarse line under your name: "active now" (within two minutes), "N minutes ago" (in steps of five minutes), "N hours ago", and after a day a date only. Never a clock time. It is not shown in groups, in a conversation with an organization position, in the control room or in the admin consoles.
- Hiding: under Settings → Account → Privacy (הגדרות ← חשבון ← פרטיות) you can turn on hide "last seen". Hiding is reciprocal: while you hide, others do not see yours and you do not see theirs. The value is still kept on the server so that hiding can be undone, but it is shown to nobody. Default: shown.
- Older versions of the app do not send the signal, so nothing is shown about their users.
3.14 Forwarding messages
- You can forward a text message, a voice message, a photo or a file from one conversation to another you take part in. A copy of the message is created in the target conversation, labelled "forwarded". The copy does not carry the original sender's name and does not say which conversation it came from; it is shown as your message.
- The copy does not include the location attached to the original, its reactions, its mentions or its urgency classification. It is classified as an ordinary message and triggers no boost or emergency alert.
- We keep, in the copy's record, a link to the original message, for the deletion described here. The link is not shown to participants.
- Deleting the original: when the original sender deletes their message, every copy forwarded from it, in every conversation, is deleted too. Whoever forwarded can delete their own copy only, which does not affect the original.
- Forwarding into an organization group is subject to everything said about such groups in section 5: the organization's authorized staff see the copy like any message in the group. Forwarding a message out of an organization group is allowed only to someone entitled to read it, and is their responsibility.
3.15 Bluetooth devices and playback in silent mode (Android)
On Android, while the phone's ringer is on silent or vibrate, the app plays sound by itself only into headphones or into a Bluetooth device you approved (Settings → Receiving messages → Playback in silent mode; הגדרות ← קבלת הודעות ← השמעה במצב שקט). To tell which device the sound goes to — headphones, a car system or an unidentified device — the app reads, on your phone, the device's type, name and address. On Android 12 and later it reads the type only if you allow "Nearby devices", which the app asks for only on that settings page. The iPhone app has no such page; how the iPhone plays in the background is described in section 3.16.
This information is processed on the device only: it is not sent to us or to any service provider, and it is not included in the diagnostic file you can choose to send. The list of devices you approved is kept on the phone only. You can remove a device at any time on that page, and the list is deleted from this phone when you delete your account. Another phone on which you used KODKOD keeps its own list until the deletion reaches it (the next time it connects to the service while still signed in to the account), or until the app is removed from it.
3.16 Background playback on iPhone (Apple Push to Talk)
- Your choice. To hear messages while the iPhone is locked or the app is in the background, the app offers, once, to turn on background playback ("Turn on background playback"; הפעל השמעה ברקע). Nothing happens unless you agree. It uses Apple's Push to Talk framework.
- What is stored on our server: the temporary Push to Talk address that Apple gives your iPhone, the app's identifier, and your receive settings (which conversations play by themselves, silence, and speaker hours), so that the server wakes the phone only when you would want to hear something.
- What Apple receives: when a message or a live transmission arrives for you, our server sends a wake-up notification directly to Apple, which passes it to your iPhone. It contains the conversation name and the sender's name and identifiers; it contains no audio, no text and no location. The iPhone then fetches the audio from our server. iOS shows the conversation and the current speaker in its own Push to Talk interface.
- What you should know: once turned on, messages may be played aloud even when the iPhone's silent switch is on; a Focus may delay or prevent playback.
- Turning it off: Settings → Receiving messages → Background playback (הגדרות ← קבלת הודעות ← השמעה ברקע), or by leaving KODKOD's channel in the system's Push to Talk interface. From then on our server stops using the address (it is marked invalid); the record is deleted with the session it belongs to, and on account deletion (section 8).
3.17 What is kept on your phone
Some information is kept on the phone itself, in the app's private storage. It does not leave the phone unless this policy says so.
- Sign-in details (session keys, your account identifier, phone number and name) are kept in the phone's protected storage (the Android Keystore or the iPhone Keychain).
- Messages and conversation lists are not kept on the phone for offline reading: the app loads them from our server each time.
- Voice messages waiting to be sent (for example without a network) are kept on the phone with their details — the recipient, an automatic preliminary transcript made on the phone, and the location to attach — until our server confirms it received them; then they are deleted from the phone.
- Received voice: on iPhone a voice message is downloaded to a temporary file to be played, and deleted after it is played or stopped; on Android it is played straight from our server. On Android, a document you open is copied to the app's cache and stays there until the phone clears it or the app is removed. Pictures may be kept in the phone's image cache.
- Settings and names: your app settings (receive settings, pinned conversations, appearance), and some names shown by the app without opening it — such as the names of conversations with unread messages, the name of your locked recipient, and names you taught voice quick-send — are kept on the phone.
- Android only: recordings you make of a contact's name, for announcing the recipient, are kept on the phone only and are never sent; and the list of approved Bluetooth devices (section 3.15).
- Technical logs: the app keeps a short rolling technical log on the phone for troubleshooting. On Android it contains no message content, names, phone numbers or locations. On iPhone it may include the names of conversations and speakers. It leaves the phone only if you choose to send it (section 3.18).
On sign-out the sign-in details are removed from the phone; voice messages waiting to be sent and your settings stay. On account deletion from the phone, the app also deletes waiting voice messages, resets your settings, and (on Android) deletes the technical log, the name recordings and the approved Bluetooth devices. Some items — certain names and settings listed above, and on iPhone the technical logs — are removed only when the app is removed from the phone. On iPhone, items in the Keychain (such as the installation ID) may remain even after the app is removed.
3.18 Diagnostic file (Android and iPhone)
Under Settings → Account → Send diagnostics (הגדרות ← חשבון ← שלח אבחון) you can create a file of technical events to help us fix a problem. The app asks for your confirmation first and then opens your phone's share menu: you choose where to send it (for example by email to us). The app never uploads it by itself.
- Android: only technical events from a fixed list (connection, wake-up, playback and service events), the phone model and system version. Message and conversation identifiers are replaced by codes that cannot be traced back without a key that stays on the phone. No content, names, phone numbers, locations or sign-in details.
- iPhone: the technical events of background playback, live transmission and Focus. Before the file is created, identifiers are shortened, sign-in details are removed and names are masked.
Whoever you send the file to receives it. If you send it to us, we use it only to diagnose the problem.
3.19 Silence, Do Not Disturb and Focus
To decide whether a message may play by itself, the app reads, on the phone, whether sound is silenced: on Android, the ringer mode and Do Not Disturb; on iPhone, whether a Focus is on (only if you allow the app to read Focus status). Which Focus, or why, is never read. These readings are not stored and are not sent to us. What is sent is only your receive settings and, while sound is silenced, a flag telling our server to hold live audio for now. The server is not told the reason.
4. How we use information
- To provide the service: sign-in, communication, transcription, maps, notifications and control-room features.
- To keep the service and accounts secure and prevent abuse.
- To find and fix faults, and to measure usage, load and reliability.
- To meet our legal obligations.
We do not sell personal information and do not use it for advertising.
5. Organizations, organization groups and the control room
- Organization groups. An organization group belongs to an organization. A group becomes an organization group only with its members' consent. The app shows a notice when you join one.
- What the organization sees in its groups. The organization's authorized staff (managers and control-room operators) see the group's messages, recordings, transcripts, AI summaries and the locations attached to messages. This applies to everyone who sends a message in that group, including people who do not belong to the organization.
- What the organization sees about its members. If you belong to an organization, its authorized staff see your membership and your current position as the app reports it while in use (section 3.6), and can request your position. The app also says this under Settings → Organization (הגדרות ← ארגון).
- What never reaches the control room. Private conversations between two people do not reach it: not their messages, recordings, transcripts, or any location shared in them, and sending a message in a private conversation does not update your current position either. Group conversations that do not belong to an organization do not reach it either.
- The organization is responsible for how its staff use the information they see.
What organization administrators see about members in the admin console
The organization's administrators (those with viewing rights in the admin console) see, beside the member list: when the app last contacted the server (see section 3.8 — background requests included, so this is not "last seen"), the device type of that last request (Android / iOS), and aggregate usage figures per member: the number of messages sent, the duration of voice transmissions in seconds, and the number of the organization's groups they belong to, by period. They do not see the "last seen" of section 3.13 or your hide setting. This exposure has existed since September 2026 and was not described in earlier versions of this policy.
Temporary membership of an organization
- An organization can issue a temporary join code that grants membership for a fixed period (between one hour and 30 days), beside its permanent code. Joining with a temporary code is full membership for that period: authorized staff see you as described in this section, and the organization can request your position.
- The app shows when the membership expires, and warns before it ends (immediately on joining if fewer than three days remain, otherwise three days before expiry).
- When the period ends the membership ends by itself: you are removed from that organization's groups (incident groups included); conversations that are not the organization's — independent groups and private conversations — do not change. Messages you sent stay in the groups, as described in section 8.
- We keep your membership periods in the organization (from when to when, and through which code) as part of the organization's record and for licensing.
Organization positions
- An organization can define a position (for example "duty officer") that a person holds for a period. Whoever is entitled to in the organization can "take" the position, and messages sent to the position then reach them.
- The name of the holder of a position is shown to whoever addresses it (in the conversation's subtitle), together with when the shift ends. "Last seen" (section 3.13) is not shown for a position, so as not to expose the activity of a changing person.
- A conversation with a position is private to each person addressing it. A new holder starts with an empty conversation and does not see what was sent to the previous holder; the previous holder stops receiving new messages at the moment of hand-over. The previous holder also no longer sees what arrived during their shift.
- We keep the position assignments (who held it, from when to when) as part of the organization's record, and for every message sent to a position, who held it at that time.
6. Service providers
These providers process information for us to run KODKOD:
| Provider | Purpose | What it receives |
|---|---|---|
| 019 (019sms) | Sending sign-in codes by SMS | Phone number and code |
| Google – Firebase Cloud Messaging | Notifications on Android | Notification token and notification content (section 3.7) |
| Expo (650 Industries) | Notifications on iPhone | The iPhone's notification address and the notification content: conversation name, sender's name and a preview of up to about 120 characters (section 3.7) |
| Apple – Apple Push Notification service, Push to Talk | Delivering notifications to iPhone; background playback | The notification content passed on by Expo; for background playback, the Push to Talk address, the conversation name and the sender's name (section 3.16) |
| RunPod | Running our transcription model | Voice recordings, participants' names and call signs, local place names |
| Google – Gemini API (paid tier) | Urgency, place detection, summaries, digests and control-room features — only in an organization's groups, by each author's consent (section 3.5) | Of authors whose content may be sent: message text and transcripts from an organization's groups (never from private conversations), captions and file names, recent conversation context, names and call signs, group and organization names, urgency marks and times. Never: recordings, photos, videos, file contents, phone numbers or coordinates. Retention at Google: Google does not use the data to improve its products and keeps logs for a limited time only to detect abuse; what was sent cannot be recalled (section 3.5). |
| Esri (ArcGIS) | Address lookup; map images | Place names from messages (including private conversations); your phone's IP address and the map area being viewed |
| Microsoft 365 | Email from the web consoles (invitations, password resets, join requests) | Email address, name and organization name of web-console users |
| Oracle Cloud Infrastructure | Servers, storage and backups, in the Jerusalem region (Israel) | All information the service stores |
KODKOD's servers and database are in Israel. Some providers process information outside Israel: Google (Gemini and Firebase), Expo, Apple, RunPod and Esri may process information in the United States and other countries, and Microsoft may process it in Israel or elsewhere.
7. Who can see your information
- Conversation participants see your name, picture and call sign, what you send, and the location attached to your messages.
- The other person in an accepted private conversation sees roughly when the app was last in the foreground on your phone ("last seen"), unless you hide it — in which case you do not see anybody else's either (section 3.13).
- Whoever addresses an organization position you hold sees your name as the holder of a position (section 5).
- KODKOD users who have your number in their contacts and have allowed contacts access can see that you use KODKOD, with your name and picture. They can start a conversation with you. Any user who knows your phone number, or who is in a group with you, can open a direct conversation with you.
- Your organization, as described in section 5.
- Service providers, as described in section 6.
- Authorities, where the law requires us to disclose information.
8. How long information is kept
On our servers:
| Information | Retention |
|---|---|
| Messages, recordings, transcripts, photos, files, shared contacts and the location stored with a message | Until the message is deleted by its sender or, in a group, by a group coordinator. There is no automatic deletion of messages after a fixed period today, and we do not promise one. |
| Videos | Deleted from our server about 24 hours after sending |
| The recording of a live transmission that could not be saved as a message because of a server fault | Its details are deleted after about 24 hours. The audio file may remain in the server's storage, not linked to any message, because automatic clean-up of such files is not switched on today. |
| Current-position reports | About 7 days |
| Control-room reports and incident records of an organization (may include a copy of message text, a summary and a location) | Kept as the organization's operational record, with no automatic deletion. When the original message is deleted, its content is removed from them too. |
| Links to your contacts who use KODKOD | Until they leave your address book, or until you delete your account |
| SMS sign-in codes | Valid for 5 minutes; deleted a day after they expire |
| Sessions | About 60 days after they end. Some session records, including those of the web consoles, are currently kept with no automatic deletion. |
| Notification token (Android and iPhone) and the iPhone's Push to Talk address with your receive settings | With the session they belong to: the notification token is removed on sign-out; the Push to Talk address stops being used when you turn background playback off or sign out. Both are deleted with the session (above) and on account deletion |
| Sign-in and security records | About 400 days |
| Usage and diagnostic records | About 90 days. Transcription and AI usage records: about 400 days. Aggregate statistics without names or phone numbers may be kept longer. |
| Place names learned from a group's messages (the phrase, the place it refers to, and the point it was said from) | No automatic deletion, including after account deletion |
| Acceptance of the terms of use: the version accepted, the language, the time and the privacy policy version shown | As long as the account exists. After the account is deleted, the record is kept without your name or phone number, for as long as needed to protect against legal claims and to comply with the law |
| Blocks | Until the block is lifted, or until either account is deleted |
| Your AI consent decision (the decision, its time, the text version, platform and app version) and the history of your changes | As long as the account exists; deleted with the account |
| What the AI model produced from a message (its urgency wording, a map label, a report's short title, places found in it) | As long as the message exists; deleted if its author withdraws consent (section 3.5). The urgency level and "correction / ended" marks are kept. |
| "Last seen": the time of the last activity in the app, and the hide setting | A single value overwritten by every signal, no history; deleted with the account |
| Organization membership periods (from when to when, and through which code) | Kept as the organization's record, also after the membership ends. |
| Organization position assignments | Kept as the organization's record. |
| A copy of a forwarded message | As an ordinary message in the target conversation; deleted when the original is deleted by its sender, or when the forwarder deletes the copy |
| Reports, and the copy of the reported message | Kept as evidence, also after an account is deleted, without name or phone number, for as long as needed to protect against legal claims and to comply with the law |
| Audit log of administrative actions | Kept for security and oversight, with no automatic deletion |
| Database backups and server logs (including IP addresses) | Backups and server logs currently have no fixed retention period and are not deleted automatically. They are kept on the service's servers in Israel. |
Clean-up runs on a schedule and may happen somewhat later than stated.
On your phone: as described in section 3.17. Information held by a service provider (section 6) is kept under that provider's terms.
9. Deleting information and your account
Deleting a message
You can delete a message you sent. In a group, a group coordinator can delete messages too. Deletion removes the message's content for everyone, including the copies in control-room reports. That covers its text, recording, transcript, photo, video, file, shared contact and attached location. The conversation keeps a marker showing that a message was deleted.
The deleted message's record keeps the file name, and the point if the message was a shared location. They are no longer shown. A notification already shown on someone's phone stays there.
Deleting your account
In the app (Android and iPhone), go to Settings → Account → Delete account (הגדרות ← חשבון ← מחיקת חשבון), then confirm with the code we send by SMS. Without the app: on the account deletion page, with a code we text to the account's number. Either way, deletion happens on our server, immediately, and cannot be undone. The code sent from that page only deletes; it never signs anybody in.
- Deleted:
- your phone number, name and profile picture;
- your notification tokens, the iPhone's Push to Talk address, sessions and registered devices;
- all current-position reports;
- your contact links and group memberships;
- pending SMS codes;
- the time of your last activity in the app and your "last seen" hide setting.
- Kept, without your name or phone number:
- Messages you already sent stay in their conversations, because they are part of other people's conversations, shown as from "Deleted user" (משתמש שנמחק). This includes their recordings, transcripts, media (including file names) and attached locations. The content itself can still identify you to people who know you: your voice, what was said, and where it was sent from.
- The records listed in section 8, linked to an identifier that does not name you. The audit log may include earlier values from administrative actions on the account.
- If you want recordings, transcripts and message locations removed, delete those messages before you delete your account.
- On the phone: deleting the account from the app also clears what is described in section 3.17. To remove everything the app kept on a phone, also remove the app from it. A copy already sent to a service provider (section 6) is not recalled.
Signing in again later with the same number creates a new, empty account.
10. Your rights and withdrawing consent
Subject to applicable law, you can ask to access, correct or delete the personal information we hold about you by writing to support@kodkod-hub.com. You can change your name and profile picture yourself in the app.
A minor, and a parent or guardian authorized under applicable law, may contact us about safety, privacy, access, correction or deletion. We will verify the requester's identity and authority proportionately and protect the minor's own privacy: being a parent does not by itself give access to a minor's conversations. A request about information an organization is responsible for may need coordination with that organization.
Withdrawing consent
You can withdraw a permission or a choice at any time. Withdrawal stops the processing from then on; it does not undo what was already sent or stored, which is kept and deleted as described in sections 8 and 9.
- Phone permissions (microphone, camera, photos, contacts, location, notifications, and on iPhone Focus status): in your phone's settings (Android: the app's information page → Permissions; iPhone: Settings → KODKOD). The app's own page, Settings → Permissions (הגדרות ← הרשאות), shows their state and leads to the phone's settings. Turning a permission off disables the features that depend on it.
- Location: after it is turned off, no location is attached to messages, none is reported to your organization, and a control-room request is answered "location unavailable". Positions already reported are deleted after about 7 days. There is no separate switch in the app to stop only the reporting to an organization.
- Contacts: after it is turned off, the address book is no longer read. Links already stored stay until the account is deleted; you can ask us to delete them sooner.
- Notifications in the app: Settings → Notifications → When to notify (הגדרות ← התראות ← מתי להתריע): every message, mentions and emergencies, or none. Emergency messages always arrive.
- Background playback on iPhone: Settings → Receiving messages → Background playback (section 3.16).
- Transmitting from a headset or accessory: the same switch that turned it on, under Settings → Direct call (הגדרות ← שיחה ישירה).
- "Last seen": hide it (section 3.13).
- Groups: you can leave a group (long-press the group → "Delete for me (leave the group)"; מחיקה אצלי (יציאה מהקבוצה)). If you are asked to approve a group becoming an organization group, you can refuse, and one refusal stops the change.
- Organizations: membership is managed by the organization, and the app has no "leave organization" button. To end it, ask the organization's administrator or write to us. Deleting the account also ends it.
- Terms of use: the acceptance cannot be withdrawn while you keep using the account. Declining at the acceptance screen signs you out on that phone; you can delete the account at any time, also without accepting.
- AI analysis (Google Gemini): on iPhone, in Settings → Account → Privacy → AI (Google Gemini). New sends stop immediately; what is deleted and what is kept, and why what was already sent cannot be recalled, is in section 3.5. The Android app does not offer this choice yet; until it does, you can ask us to record a refusal, using the contact details in section 14. Transcription has no separate switch.
Right of access and right of correction
Under section 13 of Israel's Protection of Privacy Law, 5741-1981, every person may inspect, personally or through a representative authorized in writing or a guardian, information about them held in a database. Under section 14, a person who inspected information about them and found it is not correct, complete, clear or up to date may ask for it to be corrected or deleted. Send the request to support@kodkod-hub.com, with details that identify the account. We will verify the requester's identity proportionately and answer within the periods the law sets. A refusal will be given in writing, with its reason and an explanation of the right to apply to the court, as the law requires.
11. Security
- All communication between the app and our servers is encrypted in transit (HTTPS and secure WebSocket). Our servers accept only encrypted connections from the internet.
- SMS codes and session tokens are stored only as hashes, and a session is bound to the device that created it.
- Media files are served only to signed-in users, through short-lived signed links, and only to participants of the conversation.
- Access in the web consoles is limited by role and by organization.
- Messages are not end-to-end encrypted. Our servers process message content, which transcription, summaries and the control room need.
No system is perfectly secure.
12. Minors
KODKOD allows minors to use the service, subject to applicable law, and does not set a blanket minimum age. We do not ask for a date of birth or an ID document, and we do not know which users are minors.
The service includes sensitive features: private and group messages, recordings and automatic transcription, location sharing, contact with other users, and organizations' control-room tools. This information can reveal where a minor is, their daily routine, who they are in contact with, and their voice. Group and organization managers who work with minors must limit access to their location and content to people who need it for a permitted purpose, and must avoid excessive monitoring.
AI and minors. Google's Gemini API terms allow use only from age 18. So the Gemini analysis runs only in organizations' groups: the organization is responsible for declaring that it has no members under 18, and we may mark an organization "may include minors" — then none of its conversations is sent to Gemini. In private conversations and in groups that do not belong to an organization there is no AI analysis at all.
"Last seen" (section 3.13) can reveal a minor's daily routine to whoever talks with them in a private conversation. The display is deliberately coarse, and hiding is available to every user.
A minor's acceptance of the terms of use is not necessarily sufficient consent for every kind of processing. If a specific activity requires a parent's or guardian's consent, or a proportionate age-assurance measure, it will be enabled only after that requirement is actually implemented. For requests from minors and parents, see section 10.
13. Changes
We may update this policy. The updated version will be posted at this address, with its version number and date at the top. Every version is also kept at its own permanent address, so what was published at any time can be seen. A material change to how information is processed will also be shown in the app, and we will ask for fresh consent where the law requires it.
14. Contact
An organization that uses the control room and decides what the information it sees is used for may have its own or a joint responsibility for that information, depending on the law and its actual role.
Yair Maimon, a private individual, the operator of KODKOD, identification number 043425081
Official address: Ma'ayanot 507, Tekoa, Israel
Email: support@kodkod-hub.com