Privacy Policy
Zero-Friction Labs ("we", "us"; see section 21 for the operator's details) sets out below how we handle users' information in the app "Primaly" (the iPhone app, which also runs on iPad, including widgets, extensions and any Mac version we offer in the future; the "App") and on this website (primalyapp.com). We comply with Japan's Act on the Protection of Personal Information (APPI) and other applicable laws.
Introduction: the key points
Here is what the App handles, where it goes, when, and how you can stop it. The sections below give the details.
| Information | Where it goes | When | How to stop |
|---|---|---|---|
| Tasks, habits, journal, mind and body records, profile (section 3) | Your device and your own iCloud (encrypted on the device; neither we nor Apple can read it) | Always | Turn off "Settings › Data & backup › Sync with iCloud" |
| Sign-in email address, user ID, display name, Pro status (section 2) | Our authentication provider (Supabase, Tokyo) | When you sign in, purchase or restore | Delete your account |
| What is sent to AI: the task you act on; with "Journal & AI" on, that day's journal, your chat with Prima, that day's body and mind records, the names of the tasks and habits you finished that day, and your one-line notes from the last 30 days (section 10) | Anthropic (United States) via our relay server | Only when you take an action that uses AI | Do not use AI actions; turn off "Journal & AI"; or ask us to block AI for your account |
| Approximate location (about 1 km) (section 7) | Apple Weather | When weather is shown or recorded | Revoke the location permission |
| Your voice (section 7) | Apple speech recognition, only on devices that cannot transcribe on the device | When you use voice input | Do not use the microphone |
| Usage statistics and crash records (section 14) | Our server (Supabase, Tokyo); not linked to your account | On by default | Turn off "Settings › Privacy & security › Send usage statistics"; what was sent is deleted too |
| Feedback and support requests (section 14) | Our server and the email service Resend (United States) | Only when you send one | Do not send |
| Health data, blocked apps and screen time, calendar events, camera images, NFC tags (sections 4 to 7) | Your device only | Never sent | Revoke each permission in iOS Settings |
What we do not do
- We have no server that stores your entries (tasks, habits, journal, mind and body records), and no way to read them.
- We show no ads and include no advertising, analytics or tracking SDKs. We do not track you across other companies' services.
- We do not sell your information. Even anonymised or aggregated, your writing is never shared for research, used to train AI, or sold.
- What you send to AI is not used by Anthropic to train models (section 10).
- Nothing is sent to AI without an action from you (section 10).
- Health data, blocked apps and screen time, calendar events, location history, camera images and your voice never go to our servers.
- We send no marketing email and do not use push notifications (no device tokens).
1. Core principle: your entries live on your device and in your own iCloud
The App has no content server of its own for the entries you create (tasks, habits, journal, mind and body records, profile, avatar and so on). They are stored on your device and in your own iCloud (your Apple account). What goes to iCloud is encrypted on your device, and the key exists only on your devices and in your iCloud Keychain. Neither we nor Apple can read it (section 9).
Separately, the App uses an authentication provider for sign-in (section 2) and Pro status, an AI processor for the AI features (section 10), and Apple's weather service for weather (section 7), sending each the data that feature needs. To improve the App we also send usage statistics (which features were used, never what you wrote) and crash records to a server we manage (section 14). If you send feedback or a support request from the App, we receive it (section 14). What is sent, when, and where is explained below. Apart from these, the entries you create are never sent to or stored on any server, ours or anyone else's.
Each permission and the AI settings are optional. If you decline, only that feature (weather, health data display, Prima and so on) is unavailable; everything else works. However, the App cannot be used without the information needed for sign-in (section 2).
2. Account and sign-in
Using the App requires signing in with either Apple's "Sign in with Apple" or a Google account. Signing in creates an account with our authentication provider, Supabase (Supabase, Inc.), in the space we manage (Tokyo region), where the following is stored:
- Account identifier (the user ID issued by Apple or Google)
- Email address (if you chose Apple's "Hide My Email", the private relay address Apple provides)
- Display name (the name received from Apple or Google at sign-in, used as the default nickname in your profile; not stored if you chose not to share your name with Apple)
- Status of the paid plan (Primaly Pro): product type, expiry, and the purchase identifier issued by the App Store (original transaction ID). The App registers this with our server automatically when you purchase or restore, and when it checks your App Store purchases (for example at launch). Used to decide Pro status and manage AI usage limits (section 16)
- Daily counts of AI calls and characters sent, to manage AI usage limits (section 10)
- The version of the Terms of Service and Privacy Policy you agreed to, and when (at sign-in, or when you agree in the App after a revision; section 20)
Only if you choose to sign in with Google does an exchange of credentials with Google LLC take place to verify your identity. If you choose Apple, nothing is sent to Google.
By the nature of the authentication service, sign-in and sync traffic leaves technical logs (connecting IP address, time and type of call) that are deleted automatically after at most about 7 days. We use them only for troubleshooting and investigating abuse. At launch the App also reads a small configuration from our server (required version, emergency notices, which features are available). No records or information about you are sent at that time (while you are signed in, the request carries your session).
This information is used solely to authenticate, maintain and manage your account, reflect your paid plan, prevent abuse, and respond to your enquiries. It is never used for advertising, profiling, or tracking across other companies' services. The journal entries, tasks and other records you create are never stored on our servers linked to this account. You can delete your account at any time from "Settings › Account › Delete account" in the App (section 16).
3. Your records: tasks, habits, journal, mind and body records, profile
The App creates the following records on your device and syncs them to your iCloud, encrypted on the device as described in section 9. They are not sent to our servers. What is sent when you use the AI features is listed in section 10.
- Profile information (nickname, bio, avatar; the avatar and stamp-card backgrounds are images you pick from your photo library, stored on the device)
- Tasks, habits (habit stamps) and projects, their completion status, today's step and its notes
- Journal text, sleep memo, and records of feelings, body condition, state of mind and sleep rating. Paragraph formatting of journal text is processed on the device (Apple's on-device model) and is not sent anywhere
- Your conversations with Prima (section 10; conversations are stored on the device)
- Settings for alarms, App Block, the focus timer, the launcher and so on
- Task and habit names are added to the on-device search index (Spotlight) so you can open them from iPhone search. Nothing is indexed while the App is locked
Self-reported state of mind, body condition and sleep rating, and the state of mind read from Apple Health (section 4), are handled with the same care as special care-required personal information under Japanese law even where they do not legally qualify as such. We do not collect special care-required personal information unless you write it yourself, for example in your journal. These records live on your device and in your iCloud, and go to AI only through your own action and settings (section 10).
4. Health data (HealthKit)
Apple Health data is handled only with your permission. It is never used for advertising or data mining, and never disclosed or sold to third parties. It is never sent to our servers or to AI.
- Read: sleep duration and sleep stages, steps, workouts (type and duration), time in daylight, mindful minutes, and state of mind recorded in Apple Health by other apps (including the kinds of feelings and associated events). Used to display your daily record and weekly reports. Not saved into the App's own records; used on the device only. However, when you export a week or a month (Markdown, PDF), the exported file includes a sleep summary for that period (average sleep duration, average bedtime and wake time, average deep and REM sleep) (section 8).
- Write: only state of mind (pleasant to unpleasant) and the kinds of feelings. When you close your day, if another app has recorded a "daily mood" in Apple Health, the App reads that value and shows it below your input (it is not used as a default and is not kept in your records). The state of mind you enter, and the feelings you optionally select, are written to Apple Health as that day's mood (including when you close yesterday later). Associated events are not written. On days another app has already recorded a daily mood, nothing is written.
The state of mind and feelings recorded in the App are treated like body condition: as self-reported records you entered and confirmed. Like other records they are encrypted on the device and synced to your iCloud (section 9) and may be included in the AI context (section 10). Values read from Apple Health are never themselves saved to iCloud.
5. App Block and Screen Time
- What you block: handled through Apple's Family Controls / Screen Time framework. The apps and categories you choose are stored on the device as identifiers issued by Apple that do not reveal app names. Neither the App nor we can learn the app names from them. However, for apps that showed the block screen, the App remembers the app's identifier (for example com.example.app) on the device, up to 32 of them, so it can return you to that app after unlocking. Your selection and the blocking status are never sent off the device (not to AI either).
- Screen time: usage time is drawn on the device by a separate Apple mechanism (the usage report extension). The App itself cannot read those numbers.
- What usage statistics include (section 14): only the in-app actions "created a block rule" and "started a quick block (from where)". Which apps, when and how long blocking was in effect, and usage time are never sent.
- Temporary and emergency unlock: verified with an NFC tag, a registered photo, or the camera (section 7). Verification happens on the device, and unlock counts are kept on the device.
- Mac version (if we offer one): macOS has no Screen Time enforcement, so the App's own resident helper (a menu bar icon) hides blocked apps during blocking hours. Blocking websites in Safari uses a Safari extension. The extension has permission to read the address of the page you are viewing, but decides on your Mac only and sends neither addresses nor browsing history anywhere, including to us. The lists of blocked apps (name and identifier) and sites are synced to iCloud encrypted on the device like your other records. Mac blocking time does not appear in your records or reports. The screen for choosing apps reads the list of apps installed on your Mac.
6. Calendars and Reminders
- iPhone calendar: only with your permission, the App reads your device calendar events and shows them in the daily timeline and calendar. You can add, edit and delete events through the standard iOS screens; changes are saved to your device calendar (iCloud Calendar or whichever you use). Event contents are never sent to our servers or to AI. However, if you long-press an event to turn it into a task, its name and due date become a task record, and that task is sent like any other if you use an AI feature on it (section 10).
- Reminders (paid plan): only with your permission and after you choose which lists to import, the App imports the unfinished reminders in those lists as tasks, follows changes made in Reminders, and writes completions back to Reminders. Everything happens on the device; nothing is sent to our servers. When the paid plan ends, syncing stops, but the imported tasks remain.
- Google Calendar (paid plan): only if you choose "Connect Google" in the calendar settings, and after Google's consent screen, the App fetches your calendar list and events read-only. Requests go directly from your device to Google, not through our servers. Login tokens are kept in your device's keychain, and events are used only to display the calendar, the daily timeline and widgets (events for the surrounding months are cached temporarily on the device for widgets). Event contents are never sent to us, to any third party, or to AI. However, if you long-press an event and turn it into a task, its name and date become part of that task's record, and using an AI feature on that task sends them like any other task (section 10). "Disconnect" deletes the data on the device and revokes the permission at Google. Deleting your account does the same thing once; if the permission stays at Google because there was no connection, revoke it in your Google Account settings. Primaly's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
7. Location, camera, microphone, NFC, music and other device features
- Location: used only for weather. Your approximate location (latitude and longitude rounded to about 1 km) is sent to Apple's weather service (WeatherKit) when the day's weather is noted in your record and when today's and tomorrow's weather are shown in the App or a widget ("While Using"; without permission no weather is shown). Location is never sent to our servers or to AI, and we never track your location or build a movement history.
- Camera: used for "photo scan" when stopping an alarm or temporarily unlocking App Block (comparing against a photo you registered), and for the emergency unlock when nothing is registered (recognising the kind of object, such as a sink or fridge, found in any home). Recognition runs on the device; neither the camera feed nor the reference photos are sent anywhere. We never collect, store or transmit biometric identifiers such as facial geometry or fingerprints. Reference photos are encrypted on the device and synced to iCloud like your other records.
- Voice input: microphone audio is used only for transcription; we never store or transmit audio. Transcription runs on the device first. On devices or iOS versions without on-device recognition, audio may be sent to Apple's speech recognition service (processed by Apple). The journal screens show a notice while Apple's service is in use. Text you then send to an AI feature is handled as described in section 10.
- NFC tags: used to stop alarms, temporarily unlock App Block, and register habit stamps. Tags hold a number generated by the App and, for habit stamp tags, a URL on this website containing that number. Scan records stay on the device. If a device without the App taps the tag, its browser opens the URL and the number reaches this website, but the number reveals nothing about you.
- Apple Music: if you play music during a step or focus timer and grant permission, the App reads your library's playlists and plays from the Apple Music catalog. Apple handles playback history under your Apple Music account (per Apple's policies). We receive no playlists or playback history.
- App Store search and launcher suggestions: to suggest apps for the launcher, the App checks on the device whether about 50 common apps are installed (the result is not sent). When you look for an app to add to the launcher, the search term you type and your device's region and language are sent directly from your device to Apple's App Store search. App icons in the results are loaded from Apple. We receive neither the terms nor the results.
- App lock (Face ID, Touch ID, passcode): used to protect your journal and to confirm it is you before signing out, deleting your account or viewing your key. iOS performs the match; the App never receives face or fingerprint data.
- Alarms, notifications, Live Activities, widgets, Siri and Shortcuts: all run on the device. We do not use remote push notifications, so we never receive device tokens. Widget contents (today's step, events, weather, launcher) are shared on the device.
You can change or revoke each OS permission (Health, Location, Camera, Microphone, Calendars, Reminders, NFC, Apple Music and so on) at any time in iOS Settings.
8. Exports and device backups
Exporting is a paid-plan feature ("Export before deleting" on the data reset and account deletion confirmation screens is free). When you export (weekly or monthly reports as Markdown or PDF, or all records as Markdown and JSON), the file goes to the destination you choose (Files, another app and so on). We never receive it. Exported files are not encrypted; keeping them safe is up to you. Weekly and monthly reports include the Apple Health sleep summary (section 4). The all-records export does not include blocking or screen-time records, Prima conversations, Prima's one-line notes, or alarm settings.
Data on your device is protected by iOS data protection. The App's record store is excluded from iPhone backups (iCloud Backup and backups to a Mac or PC). To move to a new device, use iCloud sync (section 9). Records you keep while sync is off can't be restored if you lose the device.
9. iCloud sync and encryption
The App syncs your entries to your own iCloud so they survive a device change or loss. This is your Apple account's storage, not our server. Sync is on by default and can be turned off at any time in "Settings › Data & backup › Sync with iCloud".
Only data encrypted on your device ever leaves for iCloud. Each record is encrypted whole, and encryption and decryption happen only on your device. The key is kept in your iCloud Keychain (an area Apple encrypts end to end). We do not hold the key and have no way to obtain it. Apple holds encrypted data only: it can see management information such as record count, size and modification time, but not the contents. Your last sign-in method (Apple or Google) is also kept in your iCloud Keychain so we can guide you on a new device. It never reaches us, and account deletion erases it.
When you use an AI feature (section 10), only the content for that action leaves the encryption on your device and travels over an encrypted connection (TLS) through our relay server to Anthropic. Neither AI nor we ever read the encrypted data in iCloud itself.
The flip side is that if the key is lost, even we cannot recover your data. Normally iCloud Keychain carries the key between your devices, but as a precaution you can save a copy from "Settings › Data & backup › Recovery key". Turning off iCloud sync leaves already-synced data in iCloud; to remove it all, delete your account (section 16).
10. Data sent externally when using the AI feature "Prima"
Using the AI features is optional. Tasks, records, alarms and App Block work without AI. Prima is an AI, not a human and not a licensed professional (Terms, Article 9). The recipient is our AI processor, Anthropic, PBC (Claude API), reached not directly from the App but through a relay server we manage (on Supabase). The relay passes Anthropic only the text, instructions and settings needed to generate a response; it does not pass your account identifier, email address or IP address, and it does not store or log the text you send or the replies. You can also have AI transmission blocked for your whole account without deleting it; contact us (section 21).
Data is sent only when you actually operate a feature that uses AI. Nothing is sent at launch or in the background. If "Journal & AI" is on, opening the evening chat with Prima sends that day's journal, as described below.
Before anything is sent to AI for the first time, we show what is sent and to whom and ask for your permission (for the evening chat, when you turn on "Journal & AI"; for task step suggestions, the first time you tap "Ask Prima"). If you don't allow it, nothing is sent. Your permission is recorded on your device, and we ask again if we change what is sent.
Journal text is treated separately from everything else. Sharing it is off by default and is enabled only if you choose so in "Settings › Privacy & security › Journal & AI" after reading what it means. While it is off, not a single character of your journal is sent.
Regardless of the "Journal & AI" setting, the following actions send data:
- "Next step", "First move" and "Readjust" for a task (3 free uses, then the paid plan): that task's name, notes, due date, names of unfinished subtasks, the current step, the step you have set for next time, previous steps (date, text and progress notes; up to the last 60), and what you wrote about today's progress. Other tasks are never sent.
Only when "Journal & AI" is on, the following is additionally sent:
- Prima's opening line in the evening chat: when that day's journal (including quick journal entries from the day) has text, opening the chat screen sends the full journal text for the day (up to about 20,000 characters), the names and times of the tasks you finished or worked on and the habits you stamped that day, and that day's body condition, state of mind and feelings, your one-line notes from the last 30 days so Prima can compose its first words. On nights without journal text, the same content is sent if you finished or worked on a task or stamped a habit that day and did not choose a feeling. On other nights, and on nights that start from a question kept from an earlier evening, the chat starts from a set line and nothing is sent at that point. If you keep answering "No" to the set questions and you finished or worked on a task or stamped a habit that day, the same content is sent to compose the next question. When you close the previous day later, opening the chat screen sends it if there is anything to send.
- Evening chat with Prima (3 free evenings, then the paid plan): what you write to Prima and the AI's replies, the recent history of that conversation (up to 40 messages), the full journal text for the day (including quick journal entries; up to about 20,000 characters), the names and times of the tasks you finished or worked on and the habits you stamped that day, that day's body condition, state of mind and feelings, and your one-line notes from the last 30 days. Sent when you send a message. The names of unfinished tasks are not sent. A one-line note is a short summary of about 40 characters the AI makes from that evening's chat when you add the chat to your journal. It is stored like your journal, on your device and in your iCloud. At the same time, if you mentioned plans, the AI also makes a question to ask on a later evening, stored the same way. You can review and delete notes at any time in "Settings › Privacy & security › What Prima remembers".
- Saving the chat into your journal: when you tap ✓ at the top right, the whole conversation plus the journal text you have already written that day (up to about 20,000 characters), for the clean-up.
Prima sees that day's conversation, that day's journal and mind and body records, the names of the tasks and habits you finished that day, and your one-line notes from the last 30 days. It does not see previous days' conversations themselves or other days' records.
In chats with Prima, the App checks on your device only whether what you type contains words suggesting self-harm or suicide, and if so shows a list of crisis helplines. The result of this check is not sent to us or to Anthropic, and no one is notified. The instructions used to generate Prima's replies also tell it to recommend crisis helplines when it receives such words. When you turn off "Journal & AI", no further transmission based on that setting occurs; a request already in progress may complete.
Data read from HealthKit, Screen Time data, calendar events, location, camera images and your voice are never sent to AI. Your self-reported body condition (1 to 7), state of mind and feelings are sent in the evening chat as described above. Sleep ratings and sleep memos are not sent.
To manage AI usage limits, our server records the number of AI calls and characters sent per day, linked to your account (never the text). This is erased when you delete your account. Separately, we keep totals of processing volume and cost per feature as statistics not linked to anyone.
Data sent is never used to train AI models. Anthropic does not use API inputs and outputs for training and deletes them within 30 days of receipt (under its commercial terms). However, inputs and outputs that Anthropic's automated safety systems flag as a suspected violation of its usage policy may be retained for up to 2 years and reviewed by its staff. Deleting your account does not shorten Anthropic's retention of what has already been sent. What you send may appear verbatim in the responses. Responses are for reference and may be wrong. For the AI disclaimer, see Article 9 of the "Terms of Service".
11. Purposes of use
We use the information we obtain or process only for the following purposes:
- Authenticating, maintaining and managing your account; providing the App's features (sync, alarms, task and habit management, journal, App Block, weather, displays based on health data, writing state of mind to Apple Health, calendar and Reminders integration and so on); reflecting and verifying your paid plan
- Providing the AI features you choose to use and managing their usage limits (section 10)
- Handling feedback, support requests, disclosure requests and bug reports, and contacting you as needed (sections 14 and 17)
- Preventing abuse, keeping the service secure, and responding to incidents
- Understanding how the App is used and improving it through usage statistics and crash records (section 14)
If we change a purpose, we do so only within a scope reasonably related to the original purpose and publish the new purpose on this website. Any use beyond that requires your prior consent unless permitted by law. We do not make decisions affecting your rights or interests solely by automated means (automated decision-making within the meaning of GDPR Article 22).
12. Processors and disclosure to third parties
Except where required by law, we never disclose or sell users' information to third parties without your consent. The following transfers are transmissions and processing on our behalf, limited to what the App's features need.
| Processor | For what | What is sent | Location |
|---|---|---|---|
| Supabase, Inc. | Authentication (section 2), paid-plan registration, AI relay and usage counters (section 10), storage of usage statistics, crash records and feedback (section 14) | Account information, paid-plan status, AI counts, statistics, feedback. AI text is relayed only, not stored | Database in Tokyo, Japan; processing functions run worldwide (section 13) |
| Anthropic, PBC | Generating AI responses (section 10) | Text and context depending on the feature used. No account identifier, email or IP | United States |
| Resend, Inc. | Delivering feedback and support requests to our inbox by email (section 14) | The feedback text and the details attached to it | United States |
| Google LLC | Sign-in with Google (section 2); reading Google Calendar (section 6; directly from your device) | Credentials; calendar read requests | United States |
| Apple Inc. | iCloud storage (section 9; encrypted, unreadable to Apple), weather (section 7; location rounded to about 1 km), speech recognition, Apple Music, App Store search (section 7), App Store purchases and paid-plan status notifications (Apple notifies us of refunds, revocations and renewals), and, if you use a beta through TestFlight, sharing of crash and usage records (per Apple's TestFlight terms) | What each feature needs | Per Apple's policies |
| Cloudflare, Inc. | Serving this website | Access logs such as IP addresses when you visit this website, or when the App reads the service and update notices from it because Supabase cannot be reached (processed briefly by Cloudflare) | United States |
When we entrust personal data to a processor, we select it carefully and require, through contracts or published data-handling policies, protection at least equivalent to this policy, and we verify its handling. For services Apple and Google provide to you directly, such as iCloud, Siri, Apple Music and your Google account, please also read those companies' privacy information.
Business succession: if we transfer the App's business to a company (incorporation) or through a sale, merger or similar, we may pass the information we hold to the successor within the scope of this policy (APPI Article 27(5)(ii)). We will require the successor to honour terms at least equivalent to this policy and will announce it on this website.
Legal requests: even when a court or law enforcement agency makes a valid legal request, all we can disclose is the account information, paid-plan status and AI usage counts we hold. Your journal and other records are encrypted on your device and not in our possession, so we cannot disclose them.
13. Cross-border data transfers
Through the transfers and processing above, your data may be processed outside Japan. Our database (account information, paid-plan status, AI usage counters, usage statistics, feedback and support requests) is in Supabase's Tokyo region (Japan). The functions that relay AI requests, send feedback, register purchases and delete accounts run on Supabase's worldwide infrastructure and may pass through other countries; the country varies by connection and we cannot determine it. Anthropic, PBC, Google LLC, Resend, Inc., Cloudflare, Inc. and Apple Inc. are U.S. companies. Where iCloud and other Apple services store data is governed by Apple's policies.
For processors abroad, we have reviewed the personal data protection regime of each country and confirmed, through contracts and published data-handling policies, that each has systems in place to continue taking measures equivalent to those required by Japan's APPI. For an overview of the U.S. regime, see the Personal Information Protection Commission's survey of foreign data protection regimes. If you would like information about a destination country's regime or a processor's measures, contact us (section 21). For residents of the EEA and the UK: Japan has an adequacy decision from the European Commission, and transfers to U.S. processors rely on lawful mechanisms such as the European Commission's Standard Contractual Clauses (SCCs) or the EU-U.S. Data Privacy Framework (section 18).
14. Usage statistics, crash records, feedback, and no tracking
The App uses no third-party analytics tools, crash reporting tools or advertising SDKs.
To improve the App, we send the following usage statistics to a server we manage (on Supabase). This is on by default. However, if your device's region is in the European Economic Area (EEA), the UK or Switzerland, we first ask whether you want to send it, and nothing is recorded or sent until you choose "Allow" (the same applies to crash reports described below).
- What is sent: first launch; app opened (once a day, with the types of widgets on your Home Screen); tabs opened; progress through onboarding and the first-step guide; sign-in method (Apple or Google); where you heard about Primaly (if you answered); step chosen, started or finished; day closed (number of stars and whether it was closed later); journal written (which screen); task created; alarm set or dismissed; block rule created; quick block started; stamp card created (never names or photos); free uses exhausted or lock screen shown; plan screen shown, purchased (plan type and whether it was a free trial) or restored; the reason you chose after canceling (if you answered, with the plan type and whether it was a free trial); app and OS version; device type (iPhone, iPad or Mac); display language; whether you are on the paid plan; and whether the build is production, test or development. Each comes with its date and time and categories such as evening or morning, task or habit, and which screen it came from (never free text)
- Crash records: what iOS recorded about where the App crashed (program location, crash type and code, OS termination reason, seconds frozen, failed launch count) and the App and OS version at the time. Tagged with the same number as usage statistics, stopped by the same setting, and deleted the same way. Never what you wrote or your device model
- What is not sent: what you wrote (tasks, habits, journal, feelings, Prima conversations), health data, location, calendar events, blocked apps or usage time
Usage statistics carry only a random number generated per device and are not linked to your account (email address or user ID); we treat them as information that does not identify you and never match them against account information. They are sent only while signed in; events from before sign-in are kept on the device and sent later. The server can identify the sending account, but uses it only to limit daily submissions and to decide "Pro or not", deleting per-account counts after about 2 days; it is never attached to the statistics themselves. Statistics older than 13 months are deleted automatically.
You can turn this off at any time in "Settings › Privacy & security › Send usage statistics". Turning it off also deletes the statistics and crash records this device has sent (turning it on again starts with a new number). Deleting your account deletes them too. Because the per-device number exists only inside the App, statistics sent before a reinstall or device change cannot be identified from that device; they expire after 13 months.
In-app support requests (bug reports, feature suggestions, other, cancellation reasons) are stored on our server (on Supabase) together with the App and OS version, device model and type (iPhone, iPad or Mac), display language and whether the build is production or test, and the same content is delivered to our support inbox through the email service Resend. No account or device number is attached to what is stored (only the number of submissions is counted per account for about 2 days, to limit daily volume). An email address you optionally provide for a reply is used only to reply. Server copies are deleted automatically after 1 year (emails received in our inbox may be kept as a record of the response).
Neither this website nor the App uses cookies, SDKs, pixels or similar for advertising or tracking, and we collect no data to track users. We do not track across other companies' services (conduct covered by App Tracking Transparency). This website has no mechanism that sends information to third parties. It is served through Cloudflare, which processes access logs briefly (section 12). Because we do not track, the presence or absence of a Do Not Track or Global Privacy Control signal does not change how this website or the App behaves.
15. Security measures
We take the following measures to protect the personal data we handle.
- Organisational and personnel measures: we limit the scope and the people who handle personal data and keep track of how it is handled; those who handle it do so with an understanding of this policy and the law. If we become aware of a breach, we assess the impact, notify affected individuals and report as required by law.
- Technical measures: access to data on our servers is controlled, and all outbound communication is encrypted (TLS/HTTPS). The API key for AI processing is kept only on our server and never included in the App. The AI relay server does not store the text (section 10). Paid-plan registration accepts only purchase information signed by the App Store.
- Device and iCloud: data on your device is protected by iOS data protection. Data synced to iCloud is additionally encrypted on the device, with the key existing only in your iCloud Keychain (section 9).
- Supervision of processors: we check the level of security when selecting processors (section 12). Measures for processing abroad are described in section 13.
No internet transmission or electronic storage is absolutely secure; we take reasonable measures. Details of our security measures whose disclosure would not compromise security are available on request (section 21).
16. Data retention and deletion
| Data | Where | Retention | How it is deleted |
|---|---|---|---|
| Records (tasks, habits, journal and so on) | Your device and your iCloud (encrypted) | Until you delete them | Delete in the App, reset data, or delete your account |
| Account information, paid-plan status, AI usage counters | Our server (Tokyo) | Until you delete your account; not deleted automatically for inactivity | Delete your account |
| Record of a paid-plan entitlement moving to another account, or released by deleting an account (purchase identifier and time; not linked to an account) | Our server | 60 days | Automatic |
| Record of a purchase Apple notified us was refunded or revoked (purchase identifier and time; not linked to an account) | Our server | No time limit (removed if the refund is reversed) | Automatic |
| Per-account counts for rate limiting | Our server | About 2 days | Automatic |
| Authentication technical logs (IP address and so on) | Our server | Up to about 7 days | Automatic |
| Usage statistics, crash records | Our server | 13 months | Turn off in Settings, delete your account, or automatic |
| Feedback and support requests | Our server and our inbox | 1 year (emails may be kept as a record of the response) | Automatic; contact us to delete sooner |
| Text sent to AI | Anthropic | Within 30 days (up to 2 years if flagged by safety systems) | Deleted automatically by Anthropic |
Data on your device is kept until you delete it and is erased when you delete the App (synced data in iCloud remains if you only delete the App). Because usage statistics and feedback are not linked to your account, deleting your account does not delete feedback. Server data disappears from the production database on deletion but may remain briefly in disaster-recovery backups; these are not read in normal operation and expire.
Running "Settings › Account › Delete account" in the App performs the following in order. The confirmation screen offers "Export before deleting", free of charge.
- Deletion of the usage statistics and crash records sent from that device (section 14)
- Erasure of this account's data on the device (journal, feelings, conversations, records and so on)
- Deletion of the copies synced to iCloud. Your other devices on the same iCloud erase this account's records the next time they are opened. For this, only a mark showing the deletion stays in your iCloud (it contains none of your records)
- Destruction of the encryption key (even if deletion in iCloud did not complete, any remaining data becomes undecryptable by anyone. The key is shared by the Primaly accounts in the same iCloud, so while another account's records remain on the device or in iCloud, we keep the key so those records can still be opened. If we can't check because there is no connection, we keep the key and decide the next time a connection is available)
- Complete deletion of your account on Supabase (paid-plan status and AI usage counters are erased at the same time; to prevent one purchase being reused across accounts, only the purchase identifier and time stay for 60 days)
If erasure on the device fails, the process stops there and shows an error. If only the server-side account deletion fails, for example because of a network problem, the App tells you and retries automatically the next time you open it while still signed in to the same account. If you cannot delete from within the App (lost device, unable to sign in), email us from the address you signed in with (section 21). After a confirmation email to that address, we delete the account information on our server. This does not erase the records on your device or in iCloud (we cannot delete your encrypted iCloud data; that follows Apple's procedures).
Data sent to Anthropic for AI processing is not used for training and is deleted after Anthropic's retention period (section 10). Permissions for data managed by the OS, such as HealthKit, can be changed or revoked at any time in iOS Settings. The state of mind the App wrote to Apple Health belongs to Apple Health and is not removed when you delete your account or the App; you can review and delete it in the Health app at any time. Google Calendar is disconnected as part of deleting your account (section 6). An active paid subscription (Primaly Pro) is managed by the App Store and is not cancelled automatically when you delete your account; cancel it in iOS "Settings › Apple Account › Subscriptions".
If you pass away: your records in the App (journal and so on) exist only on your devices and in your iCloud (encrypted on the device). We do not hold them in readable form, so we cannot disclose or hand them to family members or others (sections 1 and 9). Records in iCloud follow Apple's procedures. For the account information (section 2) and AI usage counters on our server, a family member or other representative can contact us (section 21) with a document showing the death and information identifying the account, such as the sign-in email address, and we will delete them after verification (we notify the account's email address before deleting). If you would like to decide in advance whether these should be deleted or provided to someone you designate after your death, contact us (section 21) and we will follow your instructions. Cancellation and refunds of Primaly Pro follow the App Store's (Apple's) procedures.
17. Your rights and how to make a request
You can ask us to do the following with your information. As a rule the App's data is on your device and in your iCloud, and most of it can be viewed, edited and deleted by you within the App.
- Access: data on your device can be viewed in the App at any time and exported (section 8; a paid-plan feature). To request disclosure of the account information we hold (including any records of third-party provision) or notice of purposes of use, contact us. You may choose to receive the disclosure electronically (for example by email) or in writing.
- Correction, addition and deletion: your profile and records can be edited in the App at any time. To correct account information, contact us.
- Deletion: deleting your account (section 16) erases the server-side account, on-device data and iCloud copies.
- Suspension of use and withdrawal of consent: journal sharing with AI, iCloud sync and usage statistics can each be turned off in Settings at any time (turning off usage statistics also deletes what that device sent). Other transmission to AI happens only when you operate an AI feature. You can also have AI transmission blocked for your whole account by contacting us (section 21) without deleting the account. HealthKit, location, camera, microphone, calendar, Reminders and other permissions can be revoked in iOS Settings.
- Other requests under applicable law (suspension of use, erasure, cessation of third-party provision and so on) are also honoured.
Send requests by email to the address in section 21 (or from "Settings › Contact" in the App). After confirming, to the extent necessary against the information we hold, that the request comes from you or a lawful representative (for a representative, we check a power of attorney or similar), we respond within one month as a rule (we will tell you if a complex case needs longer). We may ask for information needed for verification and advise how we will reply. We charge no fee for disclosure or notice of purposes of use. If we cannot fulfil a request, we tell you why; if you disagree, write to the same address and we will review it again from a different angle and tell you the result and where to turn in your region. Records on your device and in iCloud are not held by us in readable form and are therefore outside the scope of disclosure or correction by us. Information that cannot identify you, such as usage statistics and AI usage counts, is also outside that scope.
18. For users outside Japan (GDPR, U.S. state laws, and similar)
The App is also offered outside Japan. The controller of your personal data is the operator described in section 21. We have not appointed a Data Protection Officer because the law does not require one; please use the contact in section 21.
Residents of the EEA and the UK (GDPR / UK GDPR): our legal bases for processing your personal data are:
- Performance of a contract: sign-in, iCloud sync, paid-plan management (sections 2, 9 and 16), and the AI features you ask to use (section 10). The App cannot be used without the information needed for sign-in
- Consent: sharing journal text with AI, and each permission such as location and HealthKit (sections 4 to 7 and 10). Because state of mind, body condition, sleep rating and HealthKit data may be health data (special categories), the features that send them to AI and the Apple Health integration run only on your explicit consent (turning the setting on and granting the permission). You can withdraw consent at any time
- Legitimate interests: preventing abuse, keeping the service secure (section 15), and improving the App through usage statistics (section 14; not linked to your account and can be turned off in Settings at any time)
What you must provide, and what happens if you don't: sign-in information (account identifier and email address) is required to perform the contract; without it you cannot use the App. Providing all other information is optional; if you don't, only the features that use it (weather, Health or calendar integration, the AI features and so on) are unavailable. There is no statutory obligation to provide any of it.
In addition to the rights in section 17, you have the right to restriction of processing, to data portability, to object to processing based on legitimate interests (Article 21), and to lodge a complaint with the supervisory authority in your country. Sources of your data are you, Apple Health (records made by other apps) and Google (calendar). International transfers rely on the mechanisms in section 13. We do not carry out automated decision-making (Article 22).
U.S. residents: we do not sell your personal information and do not share it for targeted advertising (section 14). Sensitive personal information (health, precise location and so on) is handled only to the extent needed for the features you have permitted. For how we handle health-related information such as your mind and body records, see also our "Consumer Health Data Privacy Policy", written for Washington's My Health My Data Act and similar laws. To exercise rights of access, deletion or correction, contact us (section 21). We will not discriminate against you for exercising them. Primaly is not a healthcare provider and is not a covered entity under HIPAA; this policy, not HIPAA, applies.
Residents of Australia and Canada: if a matter is not resolved through the contact in section 17, Australian residents may complain to the OAIC (Office of the Australian Information Commissioner) and Canadian residents to the Office of the Privacy Commissioner of Canada. The person accountable for personal information at our business is the operator named in section 21. The person responsible for our handling of personal information is the responsible person named in section 21.
19. Children's privacy
The App is intended for users aged 16 or older, and we do not knowingly collect personal information from anyone under 16. If we learn that we have, we delete it promptly. Parents and guardians can contact us (section 21).
For users aged 16 or 17, the App observes the following: it discloses that Prima is an AI (section 10), lists crisis helplines in the Terms and on this website, shows crisis helplines in the App when a chat contains words suggesting self-harm or suicide, keeps journal sharing with AI off by default, shows no ads and does no tracking, and follows our AI processor's policies on users who are minors.
20. Changes to this policy
We may revise this policy in response to changes in the law or new features. When we do, we set an effective date and announce it on this website. For material changes that substantively alter how data is handled, we announce them at least 30 days before the effective date and ask for your renewed consent within the App. Clarifications and changes that are not to your disadvantage take effect on the announced date.
21. Operator and contact
- Business operator handling personal information: Zero-Friction Labs
- Person responsible for personal information: the responsible person at Zero-Friction Labs
- Address: provided without delay on request
- Enquiries, complaints and requests (disclosure and so on) concerning personal information: support@primalyapp.com (also from "Settings › Contact" in the App; section 14)
- Accredited personal information protection organisation: we are not a member of any. Please direct complaints to the contact above
Operator: Zero-Friction Labs