Hankkirang

Effective October 1, 2026 · Version 2026-10-01.2

What changed from the previous version (2026-09-30.2) is in the change history at the end of section 8.

Hankkirang Privacy Notice

This is a beta draft for a planned South Korea, EU and US launch. It must not be used as a public-launch notice until operator contact details and possible EU representative obligations are finalised and the data processing agreements with the providers in section 6 are confirmed.

1. Contact

Hankkirang individual developer. Privacy request contact: wshji31800@gmail.com.

2. Device-local use

Your calorie goal and logs, foods, meals, recipes, supplements, medication, real name, display nickname, status message and preferences are stored on your device by default. Signing in does not upload these records. Clearing browser/app data may erase them. You can download a backup and delete local records in Settings. Only if you connect a folder or NAS and turn on automatic backup in Settings is a password-locked backup file kept there; it is never uploaded to Hankkirang’s servers, and the password is not stored.

3. Account data

If you choose Google sign-in, Supabase Auth processes your Google account ID, email, display name, profile photo and authentication session to operate your account and friend connections. We also record the versions and time of your Terms/privacy acceptance, language and minimum-age confirmation. These records are retained until account deletion, unless a specific legal retention duty applies and is disclosed. When the account was last used (a sign-in or the app checking the account, noted at most every 12 hours), when it became inactive and which notices were e-mailed (kind, planned date, when sent) are kept until the account is deleted, to make inactive accounts inactive and delete them with notice 30 days ahead (section 8); the notices are deleted as soon as you use the account again. Friend invitations and connections are kept until you disconnect or delete your account. Friend requests (sender, recipient, when sent, and whether and when refused) are kept to deliver them and to stop the same request for 30 days after a refusal; a request is deleted when accepted or cancelled, and otherwise when the regular clean-up runs 60 days after it was sent. The consent history of per-friend health sharing, which ended on October 1, 2026, is kept to prove consent for 5 years from each entry, or deleted at once if you or the recipient delete the account first. You appear under one name everywhere—among friends and in the public space: your nickname if you set one, otherwise a random default nickname given when you sign up (for example “든든한 김밥 4821”). The name of your Google or Apple sign-in account is never shown to others. Public mode needs a nickname you chose. The real name in your profile stays on this device and is never sent. In cloud mode your nickname, one-line bio, profile photo and visibility settings (activity numbers, followers, who may send friend requests) belong to your account, so every device signed in to it shows the same; in local mode they stay on this device. They are kept until account deletion, and a photo or bio is deleted as soon as you remove it. Your profile photo is cleaned of location and other photo details before upload and shown only to friends and people with public mode on when you are too (unless either blocked the other). The server checks who may see it and gives them a photo ticket that works for 15 minutes. Your space shows each viewer only the posts they may already see, and, if you allow it, numbers counted over those posts (posts, recipe cards, likes received, saves) and your followers. Declining account processing does not prevent device-local use. Google's own processing is described in the Google Privacy Policy.

4. Sharing health information with friends · ended October 1, 2026

Sharing health information with named friends (meal names, daily calorie and macronutrient totals, supplement names and taken status) ended on October 1, 2026. Everything that had been published on the server was deleted, and nothing is published or shown to friends any more. Copies left in disaster-recovery backups are deleted after the backup period in section 8. Friend connections remain for posts shared with friends and for groups. Only the history of turning sharing on and off (categories and times) is kept, to prove the consent and answer related enquiries: it is deleted five years after each entry (the period in which a fine can be imposed), or at once if you or the recipient delete the account before then.

5. Community posts · changed October 1, 2026

The community is available only after sign-in and acceptance of the community notice (version 2026-09-30.2), which you accept together with the terms when you sign up; the two acceptances are recorded separately. Only what you write or choose is stored on Supabase, and each post is visible only to the people you chose for it: all your friends, your groups and friends you pick, or people with public mode on. Posts for friends and groups are shown only to people who are your friends when they read them, and ending a friendship hides them both ways. From October 1, 2026 shared groups that people joined by invitation no longer exist; the groups that existed then, and the posts, photos and comments in them, were deleted.

DataPurposeRetention
The names of groups you make and the friends in them, and who you chose for each post (all friends, groups, friends you pick)Choosing who sees a post and reading your group’s friends’ posts together (only you can see your groups; friends you add are not told)Until you delete the group or post, or your account. Ending a friendship takes that friend out of your groups and the people you picked at once
Post text, a meal you pick (dish name, meal slot, calories if you add them) or recipe (name, cooking time, ingredients, steps, calories per serving and each ingredient’s weight and nutrition), photos, comments, likes and bookmarksSharing meals and recipes with the people you chooseHidden from everyone and deleted from the server as soon as you delete it or your account; for photo files see “When you delete a post” below
Report reasons and times, a copy of the reported post or comment as it was when reported (for operator review), block list, rate-limit countersSafety and preventing spam and abuseUntil the reported item or the account is deleted, or the limit window ends
Posts you hid and when, and when a post was editedLeaving hidden posts out of your lists (nobody is told) and marking edited postsDeleted immediately when you show the post again or the post or account is deleted
In-app notifications (kind, related post, sender, when received, read and pushed)Telling the recipient about community activityDeleted automatically 30 days after they arrive, or at once when the recipient removes them, the related post is deleted, or the recipient or sender deletes the account

The community server does not accept medication, dose, side-effect or body-measurement records, and rejects meal or recipe fields outside the allowed list. Location (EXIF) and other photo details are removed on your device before upload, and the server rejects photos that still contain them. Other people never see your e-mail or sign-in account details. A post or comment with three reports is hidden from everyone except its author. Only authors delete their posts, and you can delete comments on your own posts. “Save recipe” copies a post, with its recipe photo, calories and ingredient nutrition, to this device only.

Post photos are shown with a photo ticket that works for 15 minutes, given after the server checks that the viewer may see the post. So when you delete a post, narrow its audience, block someone or turn public mode off, no new ticket is given from that moment, but someone who received a ticket before can still fetch that photo until the ticket ends (at most 15 minutes).

When you delete a post (including when it goes with your account), nobody else can see it from that moment. At the same time the server deletes its text, the photo details (the hash used to check the upload, file size, width and height, and the blurred preview), comments, likes, bookmarks, hidden-post records, in-app notifications about it and any report-review copy. Photo files are deleted from photo storage (Cloudflare R2), usually within minutes, and deleted once more a day later so that none is left behind. The following remain only for the periods shown:

  • (1) Rate-limit record (your account, when you posted, how many photos, the posting request number): used to count the daily photo limit; deleted 24 hours after posting.
  • (2) Posting request number: used so that a device resending an old request after a lost connection cannot publish the deleted post again. Only the random number your device created and the date are kept; once (1) is deleted it is not linked to your account or the post’s content. Deleted 30 days after the post is deleted.
  • (3) Photo deletion record (file name and size): kept until the second deletion is done, usually a day. It holds no account information.
  • (4) Server access and error logs and disaster-recovery backups: deleted after the periods in section 8.

Push notifications already delivered to someone’s phone, and copies someone saved to their own device with “Save recipe”, may stay on that device; Hankkirang cannot delete copies on other people’s devices. Deleted posts cannot be restored. Notifications about posts you can no longer see, because you blocked someone or ended a friendship, are not shown in your list and are deleted after the period in the table.

5-1. Public mode · public mode notice version 2026-10-03.2

Public mode is off by default and cannot be turned on without signing in. Only when you set a nickname and read the public mode notice in Settings or the Popular tab can you and others with public mode on see each other’s public posts and follow each other. Without it you post only to your friends and the people you pick. Posts for friends and groups, and your groups, are never made public. The public space shows your nickname, profile photo and one-line bio.

DataPurposeRetention
Public mode status, the notice version you accepted and whenRunning the public space and recording consentUntil account deletion (hidden while off, restored when turned on again)
Title, text and photo of public posts, a meal, recipe or exercise (type, name, minutes, calories burned), comments, likes and bookmarksSharing between people with public mode onHidden from everyone and deleted from the server as soon as you delete it or your account; for photo files and what remains, see “When you delete a post” in section 5
FollowsBuilding the Following tabUntil you unfollow, block, or delete your account

Turning public mode off hides your public posts, comments, public name and follows from others at once (nothing is deleted) and closes the public space to you. If you are offline, it is hidden on this device right away and shown as “turning off” until the server is told. Public posts and comments cannot contain links, and text matching a list of abusive or advertising terms is refused. Blocking someone hides both people’s public posts and comments from each other and ends follows. A public post or comment with three reports (spam or advertising, abuse or harassment, exposed personal information, false health information, other) is hidden from everyone except its author and reviewed by the operator; contact details are in section 1. Medication, dose, side-effect and body-measurement records, including weight, are never accepted in public posts.

6. Service providers and international transfers · changed October 1, 2026

Features you use on this device without signing in (food search, records, calculations, backup export) do not involve the providers below. Mobile advertising is different: Google processes it whether or not you sign in, as described in section 6-1. Only when you sign in and use account features (friends, community, cloud sync, push notifications) do we engage the providers below, and your personal data may then be transferred to, or accessed from, other countries.

  • Korean law: Article 26 (outsourcing) and Article 28-8(1)(iii)(a) of the Personal Information Protection Act (outsourcing and storage abroad necessary to perform our contract with you, disclosed in this notice). We do not ask for separate consent.
  • Safeguards: each provider processes data under the data processing terms that form part of its service agreement. These terms prohibit processing for other purposes and require technical and organisational security measures, advance notice of new sub-processors with a right to object, breach notification, and deletion or return at the end of the service. Each provider’s liability follows its own terms. All transfers are encrypted in transit (TLS).
  • EEA, UK and Swiss users: the transfer mechanism for each provider is listed below. You can ask for a copy of the relevant safeguards using the contact in section 1.
  • Complaints: we handle questions, complaints and objections about international transfers ourselves, through the contact in section 1, and ask the provider to act where needed.
  • Changes: we update this section without delay when a provider or country changes, and if a new provider or country is added we also tell you in the app.

(1) Supabase Pte. Ltd. (Singapore): sign-in and server database

Contact and sub-processors
privacy@supabase.com. Amazon Web Services, Inc. (hosting), Supabase, Inc. (US, support) and others: full list with countries
Location
Stored in the Republic of Korea (AWS Seoul region). It may be accessed and processed from Singapore, the United States and other countries where Supabase and its sub-processors operate, for operations, incident response and support. Requests may pass through Cloudflare’s network.
Data
Everything sections 3–5, 6-2, 6-4 and 6-6 describe as kept on the server except photo files and encrypted sync files, which are kept in Cloudflare R2 under (2), plus IP addresses and request records
When and how
Each time you sign in or use an account feature, over an encrypted connection
Purpose and retention
Sign-in, and running and storing the server database. Kept for the periods in those sections; deleted with your account and at the end of the contract.
Transfer mechanism
Standard Contractual Clauses (Module Two) in Supabase’s Data Processing Addendum
How to refuse, and the effect
Choose “Use on this device without signing in” on the first screen and nothing is transferred; every personal record feature still works. If you are signed in, delete your account in Settings to stop. Friends, community, cloud sync and push notifications are then unavailable.

(2) Cloudflare, Inc. (US): storage and delivery of photos and encrypted sync files

Contact and sub-processors
dpo@cloudflare.com. Sub-processor list
Location
Photo files are stored in R2’s Asia-Pacific region; Cloudflare chooses the country within that region and does not guarantee it. Who may see a photo is checked by Supabase in the Republic of Korea under (1), which gives a photo ticket. Photo uploads and sync files are set to run in the Cloudflare data centre closest to the AWS Seoul region; Cloudflare decides the actual location, which can change. The Cloudflare data centre that delivered a photo may keep a temporary copy of it for up to 15 minutes. Requests pass through data centres Cloudflare chooses among the countries where it operates, including the United States. Security and operations logs are processed in the United States and the European Union. Data centre locations
Data
Community post photos (WebP or JPEG with location and other photo details removed, and resized copies); profile photos (two sizes, cleaned the same way); with cloud sync on, your encrypted change logs and snapshots and the photos attached to your records (files encrypted on your device, which Cloudflare cannot read); photo identifiers, sizes and dimensions; post and upload identifiers; the photo ticket sent to fetch a photo (photo identifier, size, storage location and expiry; nothing about your account); your sign-in token (it contains your account ID, e-mail and Google or Apple profile name; checked, never stored); IP address and request time
When and how
When you post a photo or open a post with photos, when you change your profile photo or a profile photo appears on screen, and when cloud sync sends or fetches records or photos, over an encrypted connection
Purpose and retention
Storing and delivering photos, checking who may see them, stopping abuse. Temporary copies of delivered photos are gone within 15 minutes. Photo files are deleted, usually within minutes, when you delete or replace the photo or delete the post or your account, and deleted once more a day later. Sync photos follow section 6-2. The photo server’s error log (error type and status and the request address; never your sign-in token or account) is kept for up to 7 days. Connection data is processed for the limited period Cloudflare sets for security and operations.
Transfer mechanism
Cloudflare’s certification under the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework; Cloudflare’s Data Processing Addendum also includes the Standard Contractual Clauses.
How to refuse, and the effect
Posting without photos and without a profile photo sends none of your photos. Opening a post with photos sends connection data through Cloudflare. Without cloud sync on, no record or record photo is sent. Not using the community, or switching to local mode, means no transfer. Only community and profile photos are then unavailable.

(3) Google LLC (US): Firebase Cloud Messaging (Android push notifications)

Contact
Google privacy contact form
Location
The United States and other countries where Google operates data centres; Google chooses the country and it cannot be selected. Locations
Data
The push token; when a notification is sent, the items in section 6-4 (notification type, sender’s nickname, post identifier, a short account tag). No health records or post content.
When and how
When you turn on community notifications on Android, and each time a notification is sent
Purpose and retention
Delivering push notifications to your phone. We limit delivery attempts to one day. When you turn notifications off or delete your account, the token is deleted on your phone and its registration on our server. Retention within Google’s systems follows Google’s Firebase privacy information.
Transfer mechanism
Google LLC’s certification under the EU-U.S. Data Privacy Framework; the Firebase Data Processing and Security Terms also include the Standard Contractual Clauses.
How to refuse, and the effect
Turn notifications off in Settings or on your phone. Only phone push stops; in-app notifications remain.

Community push notifications (Apple Push Notification service) are not offered on iPhone and Mac yet, and no notification token is collected there. Before we offer them, we will add Apple to this section and tell you in the app.

The e-mail provider for the notices about unused accounts (section 8) has not been chosen yet. Before sending starts we will add the provider, its country and what it receives (your sign-in e-mail address, the kind of notice and its date) to this section. Until then no notice is e-mailed, and no account is made inactive or deleted.

Sign-in uses Google OAuth, Sign in with Apple and Supabase Auth; there is no e-mail or phone sign-up. Google and Apple process information during sign-in under their own privacy policies. No Google or Apple account connection occurs when you use the app without signing in.

6-1. Mobile advertising · addendum September 27, 2026

The iOS and Android apps use Google AdMob. Google may process IP addresses, device and app identifiers, ad impressions, clicks, video interactions, and diagnostic and performance information for advertising, fraud prevention and measurement. Development builds also connect to Google’s advertising service.

Hankkirang does not provide personal meal or health records, real names, searches, photos, backups or authentication sessions for ad targeting or analytics. The Android app does not request advertising ID permission, and the iOS app does not request tracking authorization. These settings do not mean that all device-data processing or tracking is absent. Where required, advertising privacy choices are presented, with a settings button to revisit available choices.

See Google’s advertising privacy information and its iOS and Android data disclosures. Cross-border processing, retention and rights-request details must be verified and included before public launch.

6-2. Optional encrypted cloud synchronization · Updated September 28, 2026

Devices synchronize personal record changes and deletions only after you turn on cloud data linking and consent for that account and device. Food and calorie records, meal plans, recipes, supplements, medications, weight, preferences and profiles are encrypted on your device before upload. The server database stores account and device IDs, consent status, synchronization and key versions, times, and the names and sizes of the encrypted files; the encrypted change logs, per-device snapshots and record photos are kept in Cloudflare R2 (section 6). To keep the per-account storage limit and daily sync allowance, it also records each account’s daily write count and bytes read, deleted after at most 2 days. Photos attached to records are stored once as separate encrypted files, and the server learns only their size and an identifier derived from your account key. While the photo server is under maintenance, files wait on your device. Encrypted files kept in the server database before are moved to R2 as they are, still encrypted. Devices first check whether anything changed and download only changed content.

In standard security, a randomly generated account key is stored encrypted in Supabase Vault and provided after your sign-in and device linking consent are verified. No separate synchronization password is needed, but the operator can technically decrypt your records.

Enhanced security keeps the decryption key only in secure storage on your mobile devices; since September 29, 2026 it cannot be newly turned on, and accounts that already use it can keep it or switch to standard security. A new device signs in with the same account and connects with a one-time link key created on an already linked device. A link key expires one hour after it is created and becomes invalid once used or regenerated. The server stores only a verification hash, the encrypted key being transferred, and its expiry and use status; the secret and the plaintext key are never sent. If you lose every linked device, signing in alone cannot recover your cloud records. Enhanced security does not retroactively protect earlier server copies or data that was already exposed.

Account deletion removes the latest encrypted copy, the encrypted photos and the server-managed key. Turning linking off stops further transfers. Choosing Delete cloud copy in My data deletes the server copy, encrypted photos, server-managed key and link keys at once without deleting your account, and turns off cloud linking on every device. Records on your devices are not deleted; if the request fails, it is retried when you are back online. The encrypted files of photos you delete from your records also stay on the server and count toward your account’s storage limit. Hankkirang does not delete a photo because it left your records; deleting the cloud copy, changing the security mode or deleting your account removes every photo (the files are deleted, usually within minutes, and once more a day later). Changing the security mode re-encrypts records and photos with the new key before the previous copies and key are discarded. Earlier manual backups remain until you delete them or the account. A copy protected by an earlier synchronization password is converted after you enter that password once. Initial linking and conflicting changes require your choice after reviewing categories and counts. Signing in or purchasing does not turn on synchronization. Local records remain available offline.

6-3. Health app connection · Added September 28, 2026

Only when you connect it yourself from Settings or the Diet tab, the app reads weight, body fat percentage, BMI (Apple Health), workout duration and active calories from Apple Health on iPhone or Health Connect on Android (including values written by Samsung Health and InBody). The values are saved as diet records on this device only after the app shows you what it will import and you choose to import.

Values from the health app are not sent to Hankkirang servers, are not used for advertising or analytics, and Hankkirang does not write to the health app. Imported records are included only in the folder sync or cloud data linking you have turned on, like other personal records. After you disconnect, records already imported stay until you delete them, and you can revoke read access in Apple Health or Health Connect settings.

6-4. Community push notifications · Added September 29, 2026

Only when you turn on ‘Community notifications’ in Settings for a signed-in account in cloud mode, the app stores your phone’s push notification token, a random app installation identifier and the platform (currently Android only) with that account. They are used only to tell your phone when an in-app notification (section 5) arrives. Since eating together ended on October 1, 2026 no community notifications are sent, so notifications cannot be newly turned on; if you turned them on before, you can turn them off in Settings. Without an account or in local mode, no token is created or sent.

On Android, notifications pass through Google Firebase Cloud Messaging (iPhone and Mac push is not sent yet; see section 6) and carry only the kind of notification, the sender’s nickname, the post identifier and a short hash that tells accounts apart. Health records such as meals, calories, supplements, doses and body measurements, and post contents, are never sent; the text is written on your phone. Notifications from people you blocked or about hidden posts are not sent.

The server deletes the token when you turn notifications off, another account turns notifications on on the same phone, the push service reports the token as no longer valid, or you delete your account. Switching to local mode does not contact Hankkirang servers: your phone stops showing notifications at once and deletes its push token, so the server's next attempt fails and its registration is deleted too. If deletion on the server fails, your phone stops showing notifications at once and deletion is retried in cloud mode. You can turn off Hankkirang notifications in your phone settings at any time.

6-5. Supplement and dose reminders · Added September 29, 2026

Only when you turn them on in Settings, your phone itself schedules reminders for the next seven days at the times set for your supplements and the scheduled times of your doses. Their contents and times are stored on this device only and are not sent to Hankkirang servers or any push service. By default they show no names, for example ‘Time for your supplements’ or ‘You have a dose due today’; supplement and medicine names appear only if you turn on ‘Show names in reminders’. Turning reminders off removes every scheduled reminder.

6-6. Sign in with Apple · Added September 29, 2026

If you sign in with Apple in the iPhone app, Supabase Auth receives your Apple account identifier, your email (the relay address Apple creates if you choose ‘Hide My Email’) and sign-in session information, and processes them for the same purposes as Google sign-in (sign-in, account identification and friend connections); they are deleted when you delete your account. Your name is not requested. Google and Apple accounts are never merged automatically, even when the email is the same; a second sign-in method joins an account only when you link it yourself, confirming with that provider while signed in.

When you delete your account, the app asks you to confirm with Apple once more, revokes the Sign in with Apple connection (token revocation) and then deletes the account. The one-time authorization code and Apple’s tokens are used only for the revocation and are not stored. Apple’s own processing is described in the Apple Privacy Policy.

7. Your rights and security

Settings offers account deletion, local record deletion and backup, and a server account-data export; you can delete community posts and comments at any time, and download the community data you created together with your account data. Without accepting changed terms you can still disconnect from friends, delete your posts, comments and groups, turn off public mode, and turn off cloud sync and delete the server copy; only posting and sharing anew wait for your acceptance. Contact us at the address in section 1 to exercise applicable access, correction, erasure, restriction and objection rights. Authentication and row-level access controls let only people with permission read server data. Material policy changes will be announced before they take effect. Account features are available only to users aged 18 or older.

8. Deletion · added October 1, 2026

We destroy personal data without delay when its retention period ends or its purpose has been achieved and, unless there is a good reason, within five days.

  • Procedure: when you delete something or your account, we delete it as the request is processed. Data with a set period is removed by an automatic clean-up that runs every hour once the period has passed, for example in-app notifications 30 days, a deleted post’s request number 30 days, rate-limit records 1–2 days, expired invitations 7 days, and the consent history of ended friend sharing 5 years.
  • Method: rows are deleted from the server database; photo files are deleted from storage and deleted once more a day later. Electronic files are deleted so that they cannot be recovered. We do not create paper records containing personal data.
  • Access and error logs: server request logs and the photo server’s error log are kept for up to 7 days under our providers’ settings and then deleted automatically.
  • Backups: deleted data may remain in disaster-recovery database backups for up to 30 days. Backups are encrypted, access to them is restricted, they are used only to recover from failures, and they are deleted when the period ends.
  • Retention required by law: none at present. If that changes, we will state the legal basis, the data and the period here.
  • Unused accounts: an account not used for a year (no sign-in and no use of the account in the app) becomes inactive. After two years inactive, the account and its server data (friend connections, posts, comments and photos, profile, cloud sync copies) are deleted as when you delete your account. Each step is announced to your sign-in e-mail 30 days ahead, and a step whose notice could not be sent does not happen. Signing in meanwhile keeps the account. Records on your devices are not deleted. For an account made with Sign in with Apple the Apple link cannot be removed at that point; you can remove Hankkirang under Sign in with Apple in your iPhone settings.

Change history

  • Version 2026-10-01.2, effective October 1, 2026 (accepted again by every account)
    • Sections 3, 5 and 6: post and profile photos are shown with a photo ticket that works for 15 minutes, given to those the server has checked may see them. After a post is deleted, its audience narrowed or someone blocked, a ticket received before still fetches the photo for at most 15 minutes. The Cloudflare data centre that delivered a photo may keep a temporary copy for up to 15 minutes.
    • Sections 6 and 6-2: cloud sync’s encrypted change logs and snapshots are also kept in Cloudflare R2 instead of the server database, which keeps only file names and sizes.
    • Sections 3, 6 and 8: unused accounts become inactive after a year and are deleted after two years inactive, with an e-mail notice 30 days before each step, and the last use and notice records this needs.
    • Section 6: previously said only that providers and transfer details would be stated before public launch. It now lists each provider’s countries, data, timing, purpose, retention, how to refuse, and the EU transfer mechanism.
    • Sections 5 and 8: now state what remains after a post is deleted and for how long, the 30-day retention of in-app notifications, and how data is destroyed.
    • Section 6-2: previously said photos deleted from your records are deleted from the server when synchronized, which was not the case; it now says they are deleted with the cloud copy, a security mode change or the account, and that sync photos are kept in Cloudflare R2.
    • Section 3: retention of the consent history of ended friend sharing was reduced from “until account deletion” to “5 years from each entry”. A random default nickname, not your sign-in account’s name, is shown when you set no nickname.
    • The end of friend health sharing (section 4), the change to groups (section 5) and the end of eating together were reflected on the same day.
    • Section 6-2: each account’s daily sync write count and bytes read are recorded for at most 2 days to keep the sync limits. Otherwise no new data or purposes.
    • Sections 6 and 6-2: profile photos and record photos are kept in Cloudflare R2 instead of the server database, and photos kept in the database before are moved there unchanged. Photos may be stored as WebP. No new data is collected.
  • Previous version: effective September 30, 2026 (version 2026-09-30.2)