Privacy Policy

Ichigo Ichie Technologies Inc. | Kairo | Effective October 28, 2026

1. Scope and accountable organization

Ichigo Ichie Technologies Inc. (French legal name: Technologies Ichigo Ichie inc.), a corporation incorporated under the Canada Business Corporations Act and registered in Quebec (NEQ 1182333485), operates Kairo. Website: joinkairo.ca. General support: support@joinkairo.ca. Legal, privacy and copyright notices: contact@joinkairo.ca.

This Policy describes Kairo's practices as of the effective date above. The Company is accountable under Quebec's private-sector privacy law and PIPEDA where applicable. Privacy inquiries go to the organizational role "Privacy Officer" at contact@joinkairo.ca.

2. Authentication and account data

Member accounts are created exclusively through Sign in with Apple or Sign in with Google. Kairo receives an account identifier and an email address from the provider, plus the provider claims required for authentication. For Sign in with Google those claims also include the name and the picture address of the Google account, which the authentication service keeps in the record it holds for the account; the claims of Sign in with Apple carry neither. Kairo does not show that stored name or picture to other members and does not copy the picture into a profile. Kairo does not issue a password to members. Account creation by any other method is refused by the authentication service before an account exists, so a member account is always an Apple or Google account.

At sign-in the app can receive the member's given name from the provider, so that the name step of creating a profile can offer it as a starting point. Apple provides it only the first time an Apple account is authorized for Kairo, when the app asks for it; Google provides the given name of the Google account at each sign-in. For a member with an Apple account, the name step is optional when the sign-in offers no name (section 3). For that suggestion the app reads the given name only, never the family name. It keeps the suggestion only in the app's memory, does not save it on the device and sends it nowhere. Separately, the sign-in session that the app keeps on the device, so that the member stays signed in, contains the account details the provider sends to the authentication service: for a Google account, the name and the picture address of the Google account, and for an Apple account neither (section 7). Nothing of the suggestion is saved until the member presses Continue on the name step, which saves what the field then holds, changed or not, as the name on the member's own profile (section 3); where the name is optional and the field is empty, Continue saves nothing. When the field shows a name from Apple or Google, the step tells the member that it comes from their Apple or Google account and that it can be changed; where the name is optional, the step says that a name can be added later in Edit Profile. Until a member chooses a name, other members see a generated code that starts with KA- in its place; a member who finishes without a name keeps it until adding one in Edit Profile.

Platform attributes can include storefront country and age-range/age-assurance information where available.

3. Profile and sensitive information

To finish creating a profile in the app, a user must do five things:

Consent to the Terms of Use and this Privacy Policy.
Enter a name; a member with an Apple account may leave it out when the sign-in offers no name.
Add at least three photos.
Enter a date of birth.
Provide a city.

Kairo asks for three photos because members meet in person: three photos reduce impersonation and help members recognize each other at the meetup. Kairo uses the photos to show a member to other people (sections 3 and 6), to check that the required photos are present before a member finishes signing up or hosts, and to keep and delete them with the account and list them in the data export. Kairo does not analyse what a photo shows, sends photos to no image-analysis service, and weighs the minimization of what it asks for against that safety purpose. A person at Kairo may open a photo of a member or an activity that a report concerns, to handle that report and for nothing else, and does not send it anywhere. Kairo may check stored photos for embedded location data, to confirm it was removed.

Every other part of the profile is optional and is collected only when the user adds it: more photos, a bio, gender, Kairo mode, interests, languages, profile responses, school, occupation, height and hobbies. While a profile is being created, Kairo invites the user to add a gender, a short bio and hobbies; each of them can be skipped, and the user can add or change any part of the profile at any time. Gender includes a "Prefer not to say" option. Joining a community is also optional.

Earlier versions of the app also asked for the genders of the people a user is interested in. Kairo no longer asks for this information, and where a profile still holds it, Kairo does not show it to other members.

A member who views a profile can see its name, age, city, bio, hobbies, occupation, gender, languages, interests, Kairo mode, profile responses and photos. Age is worked out from the date of birth, and neither the date of birth nor the email address is part of a profile. A profile can be viewed only by a signed-in member, once its owner has finished creating it, and not between two members when one has blocked the other. The name is also shown on the member's activities and in chats.

Gender and the genders a user is interested in can reveal sexual orientation or other intimate information, and so can membership in an identity community, such as a 2SLGBTQIA+ community or a BDSM/kink/fetish community. Joining an identity community requires express consent on a separate screen. Kairo records a separate consent for each community a user joins, with the version of this Policy in force at the time. Kairo mode is what a member says they are here for. The choices Kairo offers are New friends, Good company, Don't know yet and Trying new things, and none of them concerns the sex, gender or orientation of the people a member wants to meet or states a romantic or sexual intent. Kairo no longer offers an earlier choice that stated a dating intent; where a profile still holds it, the app does not show it and does not count it toward points.

4. Location and place information

When enabled, the device obtains a position and Kairo rounds latitude/longitude to two decimals before storage. At Montreal's latitude the resulting grid cell is about 1.11 km north-south by about 0.78 km east-west; at Toronto's latitude, about 1.11 km by about 0.81 km. Kairo does not store the raw precise coordinate in application tables, and no Kairo server receives it.

Kairo uses the rounded location to rank activities by how close they are and to show how far away each one is, which other members see only as a rough band (nearby, about 5 km, about 10 km or farther away) and never as an exact figure, and to place the activities a member hosts, which carry the host's rounded location and city label so that members near them can find them.

Apple and Google platform geocoders do receive a raw, unrounded coordinate or the text of a place query, and only when a member's act, or the app's refresh described below, asks the operating system's own geocoding service. That happens when a member searches for a place to explore, including when the search opens with the member's saved city, or the city they are exploring, already in its field, in which case that city's name is sent as the query; when a member drops a pin on the explore map; and when the app turns a device position into a city name, which it does when the member allows location during sign-up, when the member taps a control to share their location in the feed or in Settings, when the member chooses to use their approximate location when the app asks whether to keep their city, and, once the member has chosen the device's position for their location (see below) and the device still allows it, when the app returns to the foreground, at most once every six hours and without a tap. When a share control finds a city, or the app finds one after the member chooses to use their approximate location when the app asks, the app saves it as the member's profile city, in place of a typed one. When that refresh finds a city that differs from the profile city, the app saves it in the same way. The refresh never runs over a city the member chose (see below). These are Apple's and Google's services, used for their own purposes; Kairo neither stores nor receives the raw value. The app does not send a typed or saved city to either service on its own.

A city typed or saved on a profile is matched on the device against a list of Canadian places built into the app, on both platforms, without a permission and without a network geocoder. Place names and approximate locations contain data from GeoNames (geonames.org), licensed under CC BY 4.0 (creativecommons.org/licenses/by/4.0/). Modified: filtered to Canadian places, coordinates rounded.

When a member types a city instead of sharing a position, for example after declining the operating system's prompt, and then continues past the location step, the app looks the city up in that built-in list. If the list names the place, the app records the member's location consent and stores the centre of that place, on the same two-decimal grid, as the member's location cell. That cell comes from the typed city and never from a device position, and Kairo uses it in the same ways as a cell from the device. A city the list does not name gives no cell. Withdrawing location consent clears it (section 13). While the member's location consent is in effect, the member can also choose a city later: in Settings, in Edit Profile if their location already comes from a city, or when the app asks whether to keep their city. The app then stores that city's centre as the member's location cell, or, if the list does not name the city, removes the stored cell. Choosing a city this way records no new consent.

Kairo also keeps a record of whether the member chose the device's position or a city for their location, and of when that choice last changed. The record changes only when the member makes that choice: by tapping a control that shares their location, by choosing to use their approximate location when the app asks, or by choosing a city, either as described above or by entering one in Edit Profile while no location cell is stored. The refresh never changes it. While the record says the member chose a city, Kairo's server refuses to store a cell that the app takes from the device's position, unless the member chooses the device instead. A member who has made neither choice since Kairo began keeping this record has none. The app can ask such a member whether to keep their city or use their approximate location. The record is kept with the member's profile and is included in the member's data export. Withdrawing location consent does not change it (section 13). It is never shown to other members.

Hosting/platform logs may contain IP-derived city, postal code, region, country and timezone.

5. Activities, interactions and communications

Kairo collects activities, join requests and responses (including the time taken to respond), choices on activity cards, blocks, chats/messages, share-link records, post-meetup reviews, reports, legal acceptances, community consent records, subscription entitlement records, push-notification tokens and delivery records, deletion records, moderation records, ban-evasion fingerprints, age-assurance events, the Trophy records and tokens described in section 9, and the records of points, gifts, quests and Recommended For You described in the same section. Operational ledgers record read, explore and location-change activity — the surface used, the number of rows returned, and the fact and time of a location change — and are pruned on a short rolling window. Response timing feeds host reputation (section 9).

Kairo stores the text of each message on its servers so it can be delivered to, and shown to, the people in the conversation. Messages are not end-to-end encrypted. Each message is checked by an automated text filter when it is sent. A sent message cannot be edited. When either person leaves a one-to-one conversation, the conversation and its messages are deleted for both.

A user can report an activity as well as a person. When a user reports an activity, Kairo records who hosts it so the report can be reviewed, and records a pass for that user on that activity so it leaves their Feed. The user's data export includes each report they filed; on a report about an activity it leaves out the host, whom Kairo identified and the user did not provide.

Kairo does not currently operate a ticketing or support-communications system; correspondence sent to the published addresses is handled as ordinary email.

Photos are re-encoded before upload, so source EXIF GPS and capture-time metadata is not carried through. Photos other than album photos are served from a public-read content-delivery path; a person who obtains a valid image URL may be able to fetch it, without signing in.

A user-created share link exposes, to anyone holding the link and without authentication: the sharer's display name and first profile photo, the activity's title, category and interest tags, its start time, its city label, and the activity's cover photo, which the host uploaded. It does not expose the venue. Link-preview crawlers fetch those images automatically when a link is forwarded, so a forward can cause a third party to retrieve the photos without anyone opening the app. A share link stops working 24 hours after the activity's start time, can be revoked by the sharer at any time, and can be disabled by the host; the link record itself is retained after it stops working. Separately, the share text a user sends alongside the link can include the exact venue address, because it is composed from the activity's location field.

Album. Kairo has a private photo album for the activities a member takes part in. Kairo keeps one album for each activity a member hosts and each activity they are approved to join. It is created when the member posts the activity, or when the member's request to join it is approved, and the app shows it to the member once the activity has started. For activities that already existed when Kairo added the album, the album was created then. Once the activity has started, the member can add up to five photos from the phone's photo library, write a private note of up to 500 characters, choose which photo is the album's cover and hide the album. Hiding can be undone, and a hidden album stays the member's, listed as hidden. With each album, Kairo also keeps a link to the activity, the activity's category and start time, whether the member hosted or joined it and when the album was created. The activity's title, city and cover photo are not copied into the album but read from the activity itself. For each photo, Kairo keeps its file name, its place in the album and when it was added.

Album photos. Like other photos, an album photo is re-encoded on the phone before upload. The app then removes from the file its Exif data, which is where a photo's GPS location is kept, its XMP and IPTC data and any comment. A file the app cannot check this way is not uploaded. With each photo, the app uploads a smaller copy, 400 pixels wide, made the same way. Just before an upload, Kairo's server gives the app a name for each photo. The name carries no identifier of the member or the activity, and it works for 15 minutes, for an upload by that member to that album. The server deletes its record of a name once the photo is added. The record of a name that lapses unused is deleted the next time the member adds photos to an album, or with the album or the account. Album photos are kept in private storage, not on the public path described above. The app shows a member their album photos through links made in the member's own session, and each link works for one hour. Anyone who holds such a link can fetch that photo until the link expires or the photo is deleted from storage. Kairo does not scan or analyse what album photos show.

Who can see an album. No other member, including the host of the activity, can see a member's album, its photos, how many photos it holds, its note or which photo is its cover. Kairo's own systems read an album to show it to its owner, to save the owner's changes to it, to build the owner's data export, to remove or de-link it as described below and to delete its photos. A person at Kairo with access to those systems can technically read an album and open its photos as well.

How long an album is kept. An album is removed when the activity is cancelled or deleted before it starts, or when the member's place ends before it starts, and every album is deleted with the account. Once the activity has started, the album stays until the account is deleted, and its photos stay until the member deletes them or deletes the account. The end of the member's place, a cancellation, a ban or Kairo switching the album off does not delete them. Kairo can switch the album off for everyone. While it is off, the app shows no album and no photo can be added. If an activity that has already started is deleted, for example because its host deleted their account, each other member's album stays, with its photos, its note and the activity's category and start time, but with no link to the activity. The album then no longer shows the activity's title, city or cover photo. A member cannot delete an album itself. Deleting all of its photos leaves it empty.

Deleting album photos. A member can delete one photo, or all of their photos in an album, from the album. Kairo deletes the records of the deleted photos at once, and the app then deletes each photo and its smaller copy from storage straight away. Every ten minutes, Kairo's server also checks for such files that remain and deletes them, together with any album file that was uploaded but never added to an album. Deleting the account deletes from storage every album photo the member added, with its smaller copy, and Kairo checks that they are gone before it deletes the account.

Album export. A member's data export lists every album Kairo keeps for that member, including the albums of activities that have not started yet. For each album, it gives the activity it belongs to while the activity exists, whether the member hosted or joined it, the activity's category and start date, the note, which photo is the cover, whether the album is hidden and the date the album was created. It lists each of the member's album photos by its file name, with its album, its activity, its place in the album and the date it was added. The photo files themselves are not in the export. As the Download my data screen says, a member can ask for copies of them by writing to contact@joinkairo.ca. Other members' albums and the records of the names described above are not in the export.

7. Device, diagnostics and platform logs

Operational systems can record IP, user agent, request path/time and authenticated user ID, and IP-derived coarse geography. Other technical fields recorded by the hosting platform may include network/operator and device fingerprint data.

Sentry receives crash and error events and performance-tracing samples, together with a device-context block produced by Sentry's own software — typically model/manufacturer, OS/build, screen, memory/storage, battery, orientation, locale, timezone and boot time. Kairo configures Sentry to identify events only by an account identifier, and removes the request block and the diagnostic "extra" block before an event is sent, so profile fields, message bodies and community membership are not sent through those channels. Session replay, screenshots, view-hierarchy capture and profiling are switched off. Two limits are stated plainly: native crash reports and the breadcrumbs collected by Sentry's platform-level software are assembled outside Kairo's filter, and error titles and stack frames can contain technical identifiers, file paths, internal record identifiers such as a chat or activity identifier, and vendor error text. The device's IP address reaches Sentry's ingest endpoint by virtue of the connection; whether it is retained is a Sentry account setting.

Push notification tokens, the device platform and the device language are stored so notifications can be delivered. What a notification carries to the push relay is described in section 10.

The app stores the following on the device itself: the sign-in session and authentication material; language and appearance preferences; an unsent activity draft, which includes the venue text the user typed; travel-explore state, being the currently selected city and up to three recent cities with their rounded coordinates; safety check-in reminders; a record of which activities' review prompts have been answered or dismissed; a record of which features, communities, join requests and conversations have already been seen, which includes the identifiers of those requests and conversations and the last-known status of each request; which Trophies this device has already celebrated; which reward notices this device has already shown, being the names of at most four rewards for each account that has signed in on it; the last day Kairo was opened on this device and the number of days in a row, being one day and one number and not a log; a per-account record of which subscription offers the user has dismissed; and a per-account record of when the age-assurance explanation was shown and what the last attempt returned. The app never sends the records of celebrated Trophies, of reward notices shown and of days in a row to Kairo. Like other app data, a device's own backups may include them. All of it is deleted when the user signs out, along with any notifications Kairo had scheduled on the device. While the user adds photos to an album or to their profile, or chooses a cover photo for an activity, the app also keeps temporary files of them in its cache on the device: a copy of each original photo, with any location data it carries, and the versions it makes for the upload. It erases them when that addition of photos ends, or, for the cover of an activity being created, when the activity is published or the cover or the draft is discarded, or, if the app was stopped before then, the next time the app starts.

8. Purposes

Provide accounts, profiles, activities, join requests, chats, sharing, notifications and support.
Provide each member's private album of the activities they host or join (section 6).
Apply the 18+ age requirement and age-assurance rules.
Rank activities using imminence, proximity, shared interests and host trust/safety signals.
Provide Trophies, quests, points (XP), the level, gifts, Journey and memories: record the activities and profile steps that count, work out and record each award, and show each member their own progress, level, gifts and memories.
Decide, from the host's answer about a member in the questions the app asks after an activity, whether that member's first activity attended counts for points and quests.
Suggest quests to a member who has turned Recommended For You on.
Tell a member who has turned reward notifications on the points they earned when a host approves their first request to join an activity.
Prevent abuse, fraud, spam, ban evasion and security incidents; investigate reports and enforce rules.
Diagnose errors and maintain reliability/security.
Comply with law, preserve evidence and establish/defend legal claims.

9. Profiling and automated processing

Kairo uses algorithmic scoring to order activities. A relevance score is built from how soon the activity starts, how close it is, and how many of the viewer's declared interests it shares. That score is then multiplied by a per-host trust figure computed from five signals about the host: moderation actions recorded against them in the last 90 days; whether they have used the app in the last 7 days; whether they answered at least 80% of their join requests within 48 hours over the last 28 days; their cancellation ratio over the last 28 days; and a small bonus for a host whose first activity is less than 14 days old and who has never had a moderation action recorded against them at any time. Activities are then ordered by that product, with start time and identifier as tiebreakers.

Only the viewer's declared interests are used on the viewer's side. Kairo does not build a behavioural profile of the viewer from their choices on activity cards; a viewer's choices on activity cards are used only to avoid showing the same activity twice. This is profiling of hosts in the ordinary privacy-law sense. It is used for ranking and safety and is not represented as an exclusively automated decision that independently produces legal effects. Kairo currently has no third-party generative-AI provider and no AI or machine-learning software of any kind processes member data.

Trophies

Trophies and profiling. Trophies are part of Kairo. Once you have finished setting up your profile and have accepted a version of this Policy that describes Trophies as part of Kairo, Kairo records your activity participation and works out your Trophies from that record: each activity you post, and each group activity you are approved to join; for each one, its category, scheduled start and number of places, whether it was cancelled or you left it before its start, and opaque tokens standing for the people approved into it before its start while your place stood (you included, for an activity you joined; for an activity you host, everyone you approved before its start), never their names. The record keeps no location, no venue and no message. For the Trophies that go with the quests described under Quests below, Kairo also uses the information described there. Doing quests is optional, and nothing about them changes what you can do on Kairo. This is profiling: Kairo uses personal information to evaluate aspects of your activity behaviour. No setting turns Trophies off for one member, and your record is deleted with your account.

Tokens in other members' records. Until you have accepted a version of this Policy that describes Trophies as part of Kairo, Kairo keeps no Trophy record for you and works out no Trophy for you. Once you have, when you are approved into an activity, an opaque token standing for that approval, never your name, can be kept in the Trophy record of its host and of other members who have a record for that activity, so the activity can count for them.

How a result is determined. An activity counts once it has started, if it was not cancelled before it started and, when you posted it or were approved to join it, you had finished setting up your profile and accepted a version of this Policy that describes Trophies as part of Kairo. An activity you host counts when, before it started, you had approved at least two different people. A group activity you joined counts when, while your place stood, at least two people, you included, had been approved, unless you left it yourself before it started. Activities with individual chats count only for their host. No activity counts more people than it has places, and people who leave or delete their account afterwards still count. A person is counted only from an approval recorded after they had accepted a version of this Policy that describes Trophies as part of Kairo.

The Explorer. You earn your first Trophy, The Explorer, when you finish setting up your profile. Kairo works it out from the moment you finished, which it already keeps on your profile. The points it is worth are recorded as described under Points, the level and gifts.

Automated Trophy results. Kairo determines your Trophies solely through automated rules applied to your participation record and, for the quests described under Quests, to the information described there; every result it shows you was determined automatically. You can ask which personal information was used, the main reasons, factors and parameters behind a result, and the correction of inaccurate personal information, and you can submit your observations to a member of Kairo's team who can review the result, by writing to contact@joinkairo.ca.

Export. Your data export includes your Trophy progress, the Trophies you have earned and your memories. It also includes your own share of each participation record: whether you hosted the activity, whether you left it before it started, the date it was scheduled, its category and whether it was cancelled before it started. It leaves out the record's internal key, its link to the specific activity, its number of places and every opaque token, and it says whether you had turned Trophies on before they became part of Kairo. If Kairo switches Trophies off for everyone, recording continues, but progress, Trophies, Journey and memories are neither shown nor included in exports until Trophies are switched back on. Your records of points, gifts and quests, described under Points, gifts and quests below, stay in exports whether or not Trophies are switched on. Your data export also lists your albums and each of your album photos by its file name, as section 6 describes. The photo files themselves are not in it.

Retention. Kairo keeps Trophy-related personal information only for as long as it is needed to operate Trophies, to answer your requests about a result, or to meet a legal requirement, and deletes your record with your account, subject to any retention required by law and to what section 12 describes as remaining de-linked. If Kairo permanently discontinues Trophies, it deletes the information kept only for them.

Points, the level and gifts

Points and the level. Kairo gives points (XP) for certain steps and keeps one record for each award: the step it was for, the number of points and the time. The steps are completing your profile, having your first request to join an activity approved, your first activity attended, publishing your first activity, and finishing a quest. Completing your profile means filling in the twelve items that the Complete your profile card in the app counts: a first, a second and a third photo, your birthdate, your city, a name you chose, your bio, what you are here for, two vibe tags, a language, two answered prompts and your hobbies. Your gender and your occupation are optional and are not counted. Each step is rewarded once for each account. Kairo treats an approval as your first when its records show no earlier approved request of yours at the moment a host approves it, so an earlier approval whose record is gone (for example, because its chat was left) is not counted. Kairo sets the number of points for each step, and each record keeps the number it was given at. Your total is the sum of your records and your level is the level that total reaches; neither is stored as a figure of its own, and points are never taken back. Only you can see your points, your level and your streak.

When points and gifts are given. Points, gifts and quests, and the records Kairo keeps of them, begin only once you have accepted this version of the Policy or a later one. Kairo gives points and gifts only to a member who has finished setting up their profile and has accepted that version, and only for a step finished once that is so and once Kairo has turned points on. A step finished earlier earns nothing afterwards, even though it can still count toward a quest you finish later. Kairo checks the profile steps, completing your profile and the profile quests, only on a profile you have finished setting up, so a step that your profile already meets at the moment you finish setting it up counts as finished at that moment. For completing your profile (the twelve items described under Points and the level), Kairo records the first time it sees the profile complete, whether or not points are switched on for you, so that the reward is given once; once that is recorded, clearing a part of the profile and filling it in again earns nothing. Kairo gives no points, gifts or quest credit for turning on location or notifications, for answering an operating-system permission prompt or for joining a community. Kairo can switch points, each kind of gift and the quests off for everyone; that stops new awards, deletes nothing and takes nothing back. If points are switched off and later back on, points for a step or quest that you finished before they came back on, and that had not been given by then, are not given afterwards.

Gifts. Completing your profile (the twelve items described under Points and the level) and publishing your first activity each also give one gift, which is one priority request. Kairo keeps a record of each gift given and each gift used, with the time. A priority request marks a request you have sent to join an activity: its host sees that the request is marked, though not how the mark was paid for, and it is listed ahead of unmarked requests for the same activity; the host still decides. You use a gift when you mark a request that way and the weekly priority requests your subscription gives you, if you have one, are used up, and the record of the use names the request. A gift does not expire, a gift you hold stays usable if Kairo stops giving new ones, and a used gift is not given back if the request is later deleted. Your gift balance is not stored: it is the gifts given minus the gifts used.

Attendance. Kairo counts an activity as attended by you, for the points for your first activity attended and for the attendance quest, when you were approved to join it no later than its end (three hours after its start time), it was not cancelled, and the host has not answered no to "Showed up" about you in the questions the app asks after an activity. Kairo decides only once 36 hours have passed since the activity's start time, so that the host has had time to answer, and an activity whose approved place you no longer held by then (for example, because its chat was left) does not count. An answer the host gives, or a cancellation, after Kairo has counted an activity changes nothing already given. Kairo takes your first activity attended to be the earliest of those it counts as attended that its records of your approved places still show, whenever it took place; if that activity ended before points were switched on for you, it is recorded for the attendance quest and no points are given for it. To decide attendance, Kairo reads only that one answer, the host's answer about you, and never reads your own answers or what one participant answered about another. Nobody receives points or anything else for answering, and an answer is shown only to the person who gave it. The app does not tell you whether a host's answer was the reason an activity did not count. Kairo keeps no reliability score, label or category for anyone from these answers.

Reward notifications. Reward notifications are off until you turn them on in Settings, and the operating system's permission for notifications also applies. When they are on, Kairo sends one kind of reward notification: when a host approves your first request to join an activity, it tells you the points you earned for it. What it carries is described in section 10. Kairo keeps the setting with your profile, and nothing in Kairo depends on turning them on.

Quests

Quests. A quest is a goal that Kairo lists for members to browse, such as completing profile steps, being approved to join an activity, attending an activity or hosting. Kairo assigns no quest to you. You choose which quests to keep track of, up to three at a time, and Kairo keeps your choices with the time you made each; a quest leaves your choices when you stop tracking it or finish it.

What Kairo records for quests. Some quests are worked out from the Trophy record described above. Others Kairo works out from your own information: for the profile quests it counts the photos and the interests on your profile and checks that the bio is not empty, without analysing what any of them says or shows, and for the quests about a first approval and a first activity attended it reads your own approved join requests and applies the attendance rule described above. No quest uses your location, your contacts, what a photo shows or any other app. When you finish one of these quests, Kairo records that you did, with the time of the event that finished it, and gives the quest's points once. For a profile quest that time is the time of the change that met the condition, as Kairo sees it: a change to your photos, your bio or your interests on a profile you have finished setting up, or the moment you finish setting it up, if the profile already meets the condition then. Where Kairo records a profile quest for a condition that your profile, which you had already finished setting up, met before the change it is looking at, or that Kairo finds met when it works out your quests, the time it records is a time before points began, because Kairo had not recorded when you made the change, and no points are given. Kairo records a profile quest whether or not points are switched on for you. It records the quests about a first approval and a first activity attended only while quests are switched on, from the approved requests and approved places it still holds when it works them out; where points are not switched on for you, no points are given. A quest whose time is before points were switched on for you or before you accepted this version is recorded and earns nothing. A record is never withdrawn, so removing a photo later does not undo a finished quest.

Recommended For You. Kairo can suggest up to three quests to you, but only if you turn Recommended For You on from the Quests screen after reading a notice. It is off until you do, and you can turn it off at any time. Kairo records each time you turn it on, with the version and language of the notice you were shown, and each time you turn it off, with the time. The suggestions are worked out automatically from your own quest records only: which quests you have finished or are tracking, which are locked behind another quest, how far along you are, and each quest's difficulty and place in the list. They never use your communities, your location, your messages, any permission or any information about other members, only you see them, and Kairo does not store them. This is profiling: Kairo uses personal information to evaluate aspects of your behaviour on Kairo. The full list of quests is always open to you, with or without it, and nothing depends on it.

Points, gifts and quests: results, export and retention

Automated results. As with Trophies, Kairo determines your points, level, gifts and quest results solely through automated rules applied to your participation, your profile and your requests; every result it shows you was determined automatically. You can ask which personal information was used, the main reasons, factors and parameters behind a result, and the correction of inaccurate personal information, and you can submit your observations to a member of Kairo's team who can review the result, by writing to contact@joinkairo.ca.

Export. Your data export includes each award (the step, the quest it was for if any, the points and the time), each gift given or used (what, how many and when), the time Kairo first saw your profile complete (the twelve items described under Points and the level), the quests Kairo recorded as finished and when, the quests you are tracking and when you chose each, your Recommended For You record, and your reward-notification setting. It leaves out the internal keys that make a record impossible to write twice. Your total, level and gift balance are not in it because they are not stored; they are worked out from these records. What Kairo suggested to you is worked out when you ask and is not stored, so it is not in the export.

Retention. Kairo keeps these records for as long as your account exists, because your total, your level and your gift balance are worked out from them, and deletes all of them with your account; none of them remains de-linked.

Journey and memories

Journey shows a level, points (XP), the gifts you hold and a streak. Kairo's server keeps the record of your points and works out your total and your level from it each time you look, as described under Points, the level and gifts. The streak counts the days in a row you opened Kairo and is kept only on your device (section 7). No other member can see your level, points, gifts, streak or Trophies.

Memories are the activities you hosted, or held an approved place in, once they have started and were not cancelled before they started: for each, its date, title, category and city label, and the Trophies earned with it. Kairo works them out when you ask, from records it already keeps, shows at most your 200 most recent, and stores nothing new for them. While the album is switched on, each of your memories opens your album for that activity; Kairo keeps that album as section 6 describes. No other member can see your memories.

10. Service providers and transfers outside Quebec

Supabase provides database, authentication, storage, server functions and realtime services in the AWS us-west-1 region (Northern California), and is the recipient of essentially all server-side information, including the account email address and, where one exists, the password hash. Photographs other than album photos are served from Supabase's storage content-delivery layer, which is unauthenticated: it receives the requesting IP address and the object path for every photo view. Album photos are kept in private storage at Supabase and are shown through links that work for one hour (section 6). Supabase receives the requesting IP address and the object path for each such view as well.

Other recipients:

Sentry (United States ingest) receives the diagnostic events described in section 7.
Expo operates the push-notification relay and the build service. Every notification passes through Expo in clear text before Apple or Google deliver it. A new-request or join-approval notification carries the recipient's push token, the device language, and a title containing the activity's title, which its host wrote. A new-request notification additionally carries, in its routing data, the activity identifier. A join-approval notification additionally carries, in its routing data, the conversation's identifier and kind (group or one-to-one), the activity's identifier and title, and a header title, which is the activity's title for a group conversation and the host's display name for a one-to-one conversation. A reward notification, sent only to a member who turned reward notifications on, carries the recipient's push token, the device language, and a title stating the points the member earned for joining their first activity; its routing data holds only its type, and it contains no activity title and no name. Message bodies are not sent in notifications.
Apple provides Sign in with Apple, the App Store, push delivery, maps, the geocoding service described in section 4, and the declared age range. When a member who signed in with Apple deletes their account, the app takes a one-time authorization code from Apple's own sheet and Kairo's server sends it to Apple so that Apple revokes the Sign in with Apple tokens it holds for that account with Kairo; Kairo keeps neither the code nor Apple's tokens, and records only whether that succeeded, in the deletion record.
Google provides Sign in with Google, Google Play, push delivery, maps, the geocoding service described in section 4, Play age signals, and — solely to read the store's country code — the Play billing library.
RevenueCat manages subscription entitlements on Kairo's behalf. It receives a per-user identifier, subscription/purchase events from Apple and Google, and the entitlement status derived from them (which tier is active); it does not receive payment card details, which Apple and Google handle directly. RevenueCat also receives the device's IP address with each request, and its software automatically reports the device's App Tracking Transparency setting (for example, "not determined"); Kairo does not use that setting and does not ask for permission to track.
Vercel hosts joinkairo.ca, including the page that re-serves a shared activity card; it receives the requesting IP address, user agent, path, coarse IP-derived geography, and the share token carried in the URL. The card itself is generated by Kairo's own server function.
Link-preview services and the recipients a user forwards a link to are independent third parties, not Kairo service providers.

Kairo does not currently use a separate transactional email or SMTP provider. The only email the product can cause to be sent is a password-recovery message dispatched by the authentication service described above.

Information can therefore be processed outside Quebec and Canada and subject to foreign law. Kairo maintains processor/service terms and a Quebec s.17 cross-border assessment.

11. Advertising and tracking

The app has no advertising SDK, attribution SDK or third-party analytics SDK and does not use an advertising identifier for tracking; no tracking-permission prompt exists because nothing tracks. The website does not intentionally set advertising cookies. Operational logging, diagnostics and platform services still process technical identifiers as described here.

12. Retention and deletion

Account deletion removes the account and profile from ordinary use, and deletes the user's photographs from storage. When a host deletes their account, the activities they hosted are deleted with it, together with those activities' conversations, including the messages other members sent in them.

What can remain, de-linked from the account: messages the user sent in conversations other people are still part of, with their text intact; reports and post-meetup reviews, including their free text; legal acceptances, recording which version was accepted and when; age-assurance events, including the age in years the user declared; records of non-sensitive community consent; in other members' Trophy records, the opaque tokens that stood for the user's approvals, never their name, each a pseudonym Kairo could recompute while it holds the user's account identifier; in other members' albums of activities the user hosted that had already started, those activities' category and start time, with no link to the user or to the activity (section 6); and, for activities the user hosted, the category, scheduled start, number of places and cancellation status, with no link to the user, for as long as another member's Trophy record relies on them. Consent records for a sensitive identity community are an exception: they are destroyed outright, both when the user leaves that community and when the account is deleted, because the existence of such a record is itself the sensitive fact. A ban-evasion fingerprint — a keyed hash of the account's email address or provider identifier, from which the original cannot be read — is created when a banned account is deleted, and is not removed by anything. Moderation records are never linked to the account identifier and are unaffected by deletion.

The records of points, gifts, quests, quest choices and Recommended For You, and the record of when Kairo first saw the profile complete (the twelve items described under Points and the level), are deleted with the account, and none of them remains de-linked.

Platform and authentication logs, caches and backups follow provider and system cycles and are not removed by deleting the account. Kairo's own notification-delivery records are deleted along with the requests they relate to.

Text that has merely been de-linked from an account is not described by Kairo as anonymous.

Kairo does not currently operate a technical legal-hold mechanism. Where litigation, valid legal process or a serious safety investigation requires preservation, deletion of the affected records is suspended by procedure rather than by a system control.

13. Rights and choices

Subject to law, users may request access, rectification, withdrawal of consent, deletion, portability of computerized information they provided, and cessation of dissemination/de-indexation where statutory conditions apply. Location consent can be withdrawn in the app, which clears the stored location cell and the rounded location of the activities the member hosts. A city name previously saved to the profile is not cleared by that action and can be changed separately. The record of whether the member chose the device's position or a city for their location (section 4) is not cleared by that action either. An activity's city label and venue text are not cleared by that action; the activity can be cancelled separately. Sensitive communities can be left, which deletes the membership and its consent record. A Trophy, points, level, gift or quest result can be reviewed on request (section 9). Requests: contact@joinkairo.ca. Identity can be verified before disclosure.

Each of the following is asked for separately and applies only to the member who gives it. Giving one does not give another.

Terms and Privacy Policy. Accepting them is asked on a screen of its own before the app asks for any profile information on its own screens or saves any; the suggestion built from a given name that Apple or Google offers at sign-in is kept in the app's memory only until then (section 2). Acceptance is needed to use Kairo. A member who does not accept cannot continue, and a member can delete their account at any time.
Location. Kairo explains why it asks on a screen of its own. It records the member's consent when the member continues from that screen and the operating system allows location, whether it asks the member or had already allowed it, and when the member later taps a control to share their location in the feed or in Settings; or, when the member chooses a city instead of sharing a position, when the member continues with a typed city that the app's list of places names (section 4). A member who declines can type a city and keep using Kairo either way. Consent can be withdrawn in Settings, which clears the stored location cell. Withdrawing it does not clear the record of whether the member chose the device's position or a city (section 4).
Identity communities. Joining one requires express consent on a separate screen, recorded for that community alone. Leaving the community deletes that record.
Age range. When Apple or Google offers to share an age range, the member decides on the operating system's own sheet. Kairo explains it first, and a member's date of birth is required in any case.
Notifications. The operating system asks for permission at a moment of use, and a member can decline or change it in the device's settings.
Reward notifications. Off until the member turns them on in Settings, and the operating system's permission for notifications also applies. They can be turned off at any time, and nothing depends on them.
Recommended For You. Off until the member turns it on from the Quests screen, after reading a notice, and recorded when the member does. It can be turned off at any time, which stops the suggestions, and nothing depends on it.

Trophies, points, the level, gifts and quests are part of Kairo and are not a separate consent. A member who does not want a Trophy, points or quest record kept can delete their account, which deletes the records.

14. Security

Kairo uses row-level security that is enabled and forced on every table holding personal information, restricted server-side functions as the only route to another member's data, encryption in transit and provider encryption at rest, photo re-encoding, diagnostic scrubbing, access controls and incident response. No system is risk-free.

15. Minors

Kairo is 18+ and is not intended for minors. Age is self-reported: a user enters a date of birth, which the system requires to be at least 18 years in the past, and Kairo may additionally receive an age range from Apple or Google. Neither is verification, and Kairo does not describe any account as age-verified. Where a platform age signal indicates a minor, the account is automatically restricted from creating activities, sending messages, requesting to join and joining communities; a record is written where that signal conflicts with a date of birth the account declared. Removing such an account is a manual decision. Suspected minor accounts and CSAM/CSAE matters are handled under the Child Safety Standard.

16. Contact and changes

Material changes are versioned and communicated as required with renewed acceptance/consent where necessary. Privacy Officer, Ichigo Ichie Technologies Inc. (NEQ 1182333485), contact@joinkairo.ca.