Saiki Privacy Policy
1. Who is responsible
Public service brand/operator: Mehayom Digital. Business form: Israeli sole proprietor / osek patur. Country: Israel. Business address: Lotus 88, Nahariya, Israel. Privacy and general support: contact@mehayom.info. Official website: https://saiki.win/.
This policy explains the Saiki iPhone app, associated account and backup services, and communications with us. Website-specific collection is described separately in our Website Privacy Notice. Apple, Google and other independently operated services also provide their own notices. Those notices do not replace our responsibilities for information we control.
2. The important points
Saiki first saves recovery records on your device. After you choose to connect those records to an eligible authenticated account, subsequent saves automatically attempt backup of the recovery categories below. “Saved on this device” does not mean “Backed up”. Personal records linked to an account are not anonymous.
We do not automatically collect your browsing history, visited sites or blocked-domain lists. Screen Time permission and filter status are managed on the device; they are not included in our recovery backup. A website address you deliberately write into a journal is part of that entry, not a collected browsing record.
The current service has no active AI companion conversation service or public community posting. It does not send your journal or recovery records to an AI provider. No recovery-sale or journal-targeted advertising integration was found in the current app code.
3. Information and purposes
Account information. Firebase Authentication processes your account identifier, email address, selected sign-in provider and verification status. Apple or Google can provide identity information permitted by that sign-in flow; Apple may provide a private relay address. Email/password credentials are handled by the authentication service. Firebase also processes network and user-agent information for authentication security and abuse prevention. We use account information for access, recovery, verification, security and connecting the correct backup and purchase entitlement. Do not send passwords or verification codes to support.
Recovery information you choose to record. This includes your chosen profile name and intention, onboarding answers, language, dated check-ins and relapse records, wave/trigger selections and intensity, completed-practice records, personal journal text and saved alternatives, lesson progress, milestone acknowledgements and relevant preferences. We use it to show your records, calculate your recorded progress and observations, and back up and restore your data. A check-in streak is based on what was recorded; it is not a clinical assessment or independently verified abstinence measurement. A migration may preserve older records with incomplete dates rather than invent dates.
Local technical state. The app stores recovery files, integrity and migration information, pending synchronization state, authentication sessions and purchase caches. It also uses temporary drafts, navigation and animation state. Unsaved drafts can be lost when the process closes. Device permissions and actual notification scheduling, where available, are not recovery-backup fields. These local mechanisms support reliability, account separation and operation when the network is unavailable.
Purchases. Apple handles App Store payment. RevenueCat processes purchase history for purchase verification, current access and purchase analytics. Saiki uses the Firebase UID as its RevenueCat App User ID, linking purchase access to the Saiki account. The app requests store offerings and purchase information, and submits purchase or restoration requests. It does not send journal text, profile writing or recovery notes as RevenueCat attributes. Saiki does not provide an in-app payment-card entry form.
Support and technical operations. When you contact us, we process your contact details, message and any attachments you choose to send to answer the request. Avoid sending full journals or sensitive screenshots unless necessary. Service providers may process network identifiers, request times, device/software information and operational/security logs to deliver and protect their services. This is distinct from our recovery records and from advertising tracking.
Authentication and backup exclusions. Sign-in, reauthentication and Apple authorization revocation transmit required credentials/tokens to the relevant authentication providers. They are not recovery-backup fields. Temporary animation state, chat/AI prompts, browsing lists, native Screen Time state and preview-fixture objects are not part of the backup projection. Text deliberately entered in an allowed journal, report or profile field can be backed up, even if it contains a URL or synthetic text; do not enter secrets. RevenueCat is configured with the Firebase UID as its App User ID, and our app sends no journal or recovery-note text to it.
Functions and export. Firebase Functions initialize the user record and perform account deletion/retry. Their checked-in handlers do not explicitly log journal text or credentials, but this does not establish the absence or retention of provider logs. Export shares the saved recovery records currently available on this device, including preserved journal alternatives, as JSON text through the system share sheet. You choose the recipient. It is not a full export of Auth, server-only or purchase-provider records.
4. Personal and potentially sensitive writing
Recovery records can reveal intimate experiences. Journal entries may also contain health or other information requiring special care under applicable law. Please include only information you wish us to handle for the stated purposes; do not upload unnecessary information about other people.
Before attaching previously device-only records, the app explains the backup scope and asks you to instruct the upload. The Privacy Policy is a notice, not a blanket consent request. An upload instruction does not replace any separate notice or consent legally required for sensitive information or international processing. The current app has no independent cloud-only off switch.
5. Recipients and access
Firebase Authentication provides sign-in, Cloud Firestore stores the account-linked recovery backup, and Firebase Functions initializes accounts and performs deletion/retry operations. RevenueCat manages purchase access and purchase analytics. Apple provides App Store services, Apple sign-in when selected, and iOS Screen Time controls. Google also provides Google sign-in when selected. We use their services for the purposes above, not to publish your recovery records.
Cloud recovery data is not end-to-end encrypted. Authorized operator personnel and relevant service-provider personnel may have technically permitted access where necessary for service delivery, security, support or legal duties.
We may disclose the minimum information reasonably required by a lawful obligation or valid legal process, to protect legal rights or address a security incident, or with your specific instruction. A business transfer does not authorize unrelated new uses; users must receive appropriate notice and legally required choices. Exporting or opening an external support link may send information to the selected recipient and service infrastructure; destination/provider processing is not fully established by this audit. External recipients are responsible for their separate processing.
6. Processing outside Japan
The operator is based in Israel. Firebase Authentication processes data in the United States. The inspected development Firestore database and deployed Functions use asia-northeast1 (Tokyo). RevenueCat states that customer data is stored in AWS data centers in the United States. Support correspondence uses Google Workspace mail. These facts do not locate every provider log, backup, support operation or administrator; processing is not limited to Japan.
For questions about recipients, countries and safeguards, contact contact@mehayom.info. Firebase and RevenueCat publish data-processing terms and security information describing contractual and technical safeguards. These do not establish a statutory adequacy finding or a guarantee that all processing stays in Japan. Apple authentication, App Store transactions and OS-owned Screen Time settings are processed under Apple's systems and terms.
7. Storage and security
Saiki uses local account separation and server access rules intended to keep one account's recovery records from another. Network connections to supported cloud services use encrypted transport. Vendor encryption at rest and operating-system protections are different from end-to-end encryption. Saiki's local recovery JSON is not separately encrypted by the application; checksums detect corruption and are not encryption.
Use a device passcode and safeguard your sign-in accounts. Device/OS backups and exports may create copies outside Saiki's deletion controls. No security method is infallible.
8. Retention
Saiki-controlled account and recovery information is retained while needed to provide the account and service, resolve synchronization or deletion operations, meet security requirements and comply with applicable obligations. We minimize what we retain and review the continuing need rather than assign an arbitrary universal period. The current software does not automatically expire old recovery records, journal alternatives or interrupted synchronization snapshots by age or inactivity.
Confirmed account deletion blocks new recovery writes, recursively deletes account subcollections (including legal acknowledgement records), removes the Firebase Authentication identity and removes the user root. The device clears account-bound recovery generations and migration copies through the implemented cleanup. Interrupted deletion can require retry; a pending, failed or uncertain request is not completed deletion. No fixed completion time is guaranteed.
Provider operational/security logs and backups can persist according to provider policies and applicable legal/security requirements. Apple transaction history is outside Saiki's deletion control. RevenueCat transaction and purchase records follow applicable provider/contractual retention obligations; Firebase deletion does not invoke RevenueCat customer deletion or Apple cancellation. We handle appropriate ownership-verified vendor requests separately through support.
Offline copies on devices that never reconnect and user exports cannot be guaranteed remotely erased. Signing out or uninstalling does not delete the cloud account or cancel an Apple subscription. Support correspondence is kept only as long as reasonably necessary to resolve the request, maintain security/audit evidence and satisfy applicable legal obligations.
9. Your requests and choices
You can review your records in the app, edit supported journal/profile fields, export saved recovery data, and initiate account deletion in Settings. Contact contact@mehayom.info to request notice of purposes, access or disclosure, correction, suspension of use, deletion, or cessation of disclosure where applicable law provides those rights, or to raise a privacy complaint. Export is a convenience and does not limit statutory disclosure rights.
Never send passwords or verification codes to support. Requests require proportionate ownership verification and cannot authorize deletion of another person’s data. Data outside Saiki’s control and records independently required by law are distinct. Withdrawing consent does not invalidate prior lawful processing. Necessary account controls, export and deletion do not require a paid entitlement.
10. Age and changes
Saiki is for people aged 18 and over. It is not directed to children below that age. Contact us if you believe a child below the permitted age has supplied personal data so we can investigate and take appropriate action.
We publish the effective date and version of this policy. Material changes will be brought to your attention before new processing where required, and we obtain renewed consent when legally necessary. A silent policy edit does not itself authorize an incompatible new use of existing sensitive records.
Any materially different processing requires an updated policy and any notice or consent required by law. The absence of an integration in the app does not by itself establish every operator or vendor practice.
Legal acknowledgements and sign-in SDK information
Before account creation we ask for an explicit 18+ attestation and Terms agreement, with links to the Terms and Privacy notice. We do not request a date of birth. The account-linked record contains only the Terms version, server timestamp, ageAttested18Plus=true and Privacy notice version shown. Viewing a document does not record agreement. Pre-publication QA acknowledgements are kept separately and never converted into historical contractual acceptance. Existing accounts without a record are invited to acknowledge the current version without fabricated dates or loss of their records. A separate authenticated export can retrieve these legal records; the offline recovery export is unchanged.
Google sign-in uses Google's SDK. The inspected GoogleSignIn 9.2.0 privacy manifest declares linked name, email address, phone number and coarse location for app functionality; user identifiers and other data for functionality and analytics; and device identifiers and usage data for analytics. It declares no tracking. These are SDK/provider declarations, not a claim that Saiki asks for a phone number or location permission. Provider operation can involve technical data beyond the fields in Saiki's recovery backup. Saiki does not send recovery journal text to Google sign-in or RevenueCat.
Provider information: Firebase privacy and security, RevenueCat privacy, Apple privacy, Google privacy.