Remiora Privacy Policy v1.3-android (Android Pro, Google Play)

Date of enactment: August 4, 2026 Date of revision: November 6, 2026 Planned effective date: November 6, 2026

1. Scope

This Policy sets forth the handling of information in the Android app of Remiora, which is provided by the Remiora operator (the “Operator”; Remiora is referred to below as the “Service”).

2. Information We Handle

The Service may handle the following information:

• Email address used for authentication
• User identifier issued by the authentication service
• Authentication method, authentication date and time, authentication status, session information, and other information necessary to create, log in to, and maintain an account
• A nickname (up to 30 characters) that a user optionally sets on the account screen, and its association with the account's user identifier
• Photos, images, colors, products, works, drafts, editing history, and other information that a user registers on the device
• The post image, brand name, product name, item number, color name, texture category, color information, a record of the version of the Community Guidelines that the user confirmed and when, and the account association, explicitly submitted by a user to Community Palette
• Information necessary for reports of posts, reports of users, blocks, deletion requests, submission review, and actions such as hiding a submission
• Email address, subject, body, attachments, and other information that a user sends when making an inquiry
• Information about the purchase of the paid plan (Remiora Pro): whether a subscription exists, its expiry date and other subscription status, and the association with the account's user identifier. In the Android app, Pro is purchased through Google Play, and the app checks the subscription status through the SDK of RevenueCat, which manages purchase and subscription information. This SDK may keep the subscription status on the device (a cache). In addition, the Operator's server may query RevenueCat for the subscription status in features that check the Pro entitlement. The account's user identifier is passed to RevenueCat as the purchaser identifier (the Android app does not pass your email address to RevenueCat). The payment method, billing details, and other information that you enter with Google Play during purchase are handled by Google, and the Operator does not obtain or store payment information such as credit card numbers. Because of past operation, a record of subscription status may remain in the Operator's database
• IP address, User-Agent, access date and time, use environment, error information, and other information necessary to provide the Service, manage security, and prevent unauthorized use

3. Information Not Required for Uniform Registration

The Service does not uniformly require users to register their name, address, telephone number, or similar information when using the application.

An email address is used to create an account and log in. Information that a user voluntarily sends, such as when making an inquiry, is handled to the extent necessary to respond to the inquiry and for the purposes set forth in this Policy.

4. Processing and Storage on the Device

Photos, images, colors, products, works, drafts, editing history, and other data relating to a user's creations are, in principle, processed and stored in the application storage area on the user's device.

During native file selection, backup, or restoration, a file may be temporarily stored in the application's storage area.

The function that reads text from photos such as product labels (OCR) uses Google's ML Kit text recognition running on the device. The photo and the recognized text are not sent to the Operator's servers or to any other external party for OCR. However, in accordance with Google's terms, the ML Kit SDK may send performance and diagnostic information to Google, such as the device model and OS version, the app package name and version, per-installation identifiers, processing times, and error codes. The content of your photos is not included in this information.

In the initial version, the Service does not provide functionality to automatically send photos, works, or other data relating to a user's creations registered on the device to the Operator's servers or Supabase Auth, cloud synchronization, automatic backups by the Operator, or cloud backups.

The Android app is configured so that data inside the app is not included in Android's standard backup (Auto Backup) or in automatic device-to-device transfer. We do not guarantee the handling of data by mechanisms the Service cannot control, such as features specific to a device manufacturer. To keep data on the device, you can use the Service's manual backup (exporting a backup ZIP).

Information and images explicitly submitted to Community Palette are handled separately from device data and are processed and stored on servers and in private storage on Supabase to provide the Service, make them available to other users, handle reports, blocks, and deletion requests, and review or hide submissions. Before a submission is published, its image and its text information such as the brand name, product name, color name, and item number are sent to Microsoft Azure Content Safety for determination, in order to detect inappropriate submissions and prevent their publication. Block information is also stored on the server for display control.

5. Accounts and Authentication Information

The Service uses Supabase Auth for one-time password authentication using an email address and for sign-in with a Google account.

Supabase Auth may process or store the authentication email address, user identifier, authentication method, authentication date and time, authentication status, session information, and other information necessary for authentication.

A nickname set by a user is stored in Supabase in association with the account's user identifier. Setting a nickname is optional, and it can be changed on the account screen.

Authentication sessions stored in the native application are managed using protection functionality provided by the OS or encrypted storage.

6. Handling of Inquiry Information

Inquiry emails are received in Gmail via Cloudflare Email Routing.

Inquiry information is used to respond to inquiries, verify identity, respond to account deletion requests, respond to service disruptions or other issues, prevent unauthorized use, and take action required by law.

When a user requests deletion of inquiry information, the Operator will review the contents and respond individually, except where retention is necessary for legal compliance, security management, prevention of unauthorized use, or other reasons.

7. Purposes of Use

The information handled is used for the following purposes:

• Providing, maintaining, and improving the Service
• Creating accounts, verifying identity, and logging in
• Sending and verifying one-time passwords
• Maintaining and securely managing authentication sessions
• Managing and deleting accounts
• Displaying and managing the nickname on the account screen
• Storing and publishing submissions to Community Palette
• Detecting inappropriate submissions and preventing their publication
• Handling submissions, reports of users, blocks, and deletion requests, and taking action such as hiding a submission
• Displaying and managing information that users store on their devices
• Responding to inquiries, service disruptions, and other issues
• Preventing and investigating unauthorized access, unauthorized use, and other security issues
• Confirming Remiora Pro purchases, checking subscription status, restoring purchases, and reflecting Pro activation, expiry, and refunds
• Responding to inquiries about purchases, subscriptions, and refunds
• Taking action required by law

8. Cookies and Access Information

Remiora itself does not set cookies for advertising or tracking users' behavior.

Supabase and other external services may process IP addresses, User-Agent, access date and time, authentication information, and other access information to the extent necessary for authentication, access control, security management, or prevention of unauthorized use.

For Pro purchases, subscription status checks, and purchase restoration, Google Play and RevenueCat may each process device information, IP addresses, and other information, according to their respective roles (Google Play: purchase process, payment, and billing; RevenueCat: confirmation and management of purchase and subscription information), to the extent necessary for processing the purchase, preventing unauthorized use, and similar purposes.

9. External Services

The Service uses the following external services:

• Supabase: email authentication, issuance of user identifiers, management of authentication sessions and accounts, and storage of Community Palette submission data and images
• Microsoft Azure Content Safety: determination of the image and text information of Community Palette submissions, to detect inappropriate submissions and prevent their publication
• Google: sign-in (authentication) with a Google account
• Google ML Kit: an SDK for performing text recognition (OCR) of product labels and similar items on the device
• Google Play (Google Play Billing): providing the Pro purchase screen, payment and recurring billing for Pro, restoration of purchases, and the subscription management and cancellation screen
• RevenueCat (RevenueCat, Inc.): confirmation and management of Pro purchase and subscription information, management of the Pro entitlement status, provision of subscription status to the app's SDK, and responses to queries about subscription status from the Operator's server
• Cloudflare Email Routing: forwarding of inquiry emails
• Gmail: receipt and handling of inquiry emails

The handling of information by each service is also subject to the terms of use, privacy policy, and other conditions established by each provider. Information that a payment provider obtains in connection with a Pro purchase is handled according to that provider's own terms.

10. Outsourcing and Provision to Third Parties

The Operator may outsource the handling of information to external service providers to the extent necessary for providing the Service, authentication, inquiry response, security management, and other operations.

Except where required by law or otherwise permitted by law, the Operator will not provide personal data that it handles to a third party without the person's consent.

Information may be processed to the necessary extent in cases of outsourcing operations, succession of business, or other cases that do not constitute provision to a third party under applicable law.

11. Processing Outside Japan

Because the Service uses the infrastructure of providers such as Supabase, Cloudflare, Google, Microsoft, and RevenueCat, information concerning the Service may be processed by facilities or operators located outside Japan.

Specific storage and processing locations may vary depending on the service used, the selected region, incident response, security measures, and other circumstances.

The Operator will implement necessary security management measures and review service providers in accordance with applicable laws and regulations.

12. Retention Period

Authentication email addresses, user identifiers, and other account information are, in principle, retained for as long as the account exists, for authentication and account management.

Inquiry information will be deleted by an appropriate method when it is no longer necessary for responding to inquiries, verifying identity, responding to service disruptions or other issues, preventing unauthorized use, or other necessary purposes.

Where there is a legitimate reason, such as security management, prevention of unauthorized use, a legal obligation, or responding to a dispute, information may be retained only to the necessary extent and for the necessary period.

Community Palette submissions, post images, reports, and block information are retained while the account exists or until they are deleted. A submission that has been hidden is not published but may be retained until it is deleted.

The minimum processing record needed to complete an account deletion (information identifying the account and the time deletion was requested) may be retained temporarily until the deletion process is completed.

Logs, backups, and other information held by external service providers may remain for the retention period established by each provider or for the period technically necessary.

Information about Pro subscription status (such as the expiry date) recorded in the Operator's database is retained while the account exists and is deleted when the account is deleted. Purchase, payment, and billing records held by Google Play may be retained after account deletion for the periods set by Google and under accounting, tax, and other laws. The retention period of customer information and of purchase and subscription records held by RevenueCat, and their handling after account deletion (including whether and when they are deleted), depend on RevenueCat's terms and the Operator's operations.

13. Deletion of Accounts and Information

Users may request deletion of their account through the account settings screen provided by the Service or another designated method.

If the application cannot be used, users may request account deletion by contacting contact@remiora.app from their registered email address. The Operator may verify the user's identity as necessary.

When account deletion is completed, information on the server associated with the account, including the authentication email address and user identifier, will be deleted except for information that must be retained for reasons such as legal compliance, security management, prevention of unauthorized use, or other legitimate reasons.

When an account is deleted, the account's Community posts and the post images associated with those posts are deleted. Community product information that was associated only with those posts is also deleted. Reports concerning deleted posts are deleted. Reports that the account filed on other posts, block information, and posting restriction information are deleted as part of account deletion. Other deletion scope is subject to the above description of server information and exceptions for retention required by law or other legitimate reasons. Final deletion of Community post images and similar data may continue after the account is deleted, and it may take some time for the deletion of related data to be completed. During this period, the minimum processing record needed to complete the deletion is retained temporarily and is deleted once the process is completed.

When a user uses "Delete account" within the app and the account deletion is completed on the server, photos, colors, works, drafts, editing history, and other data tied to that account, stored on the device on which that operation was performed, are also deleted. Data stored on that device without signing in (local data) is separate from the account and is not deleted.

If deletion is requested by email, or for any device other than the one on which the deletion was performed, deletion of data on that device is not guaranteed to happen automatically.

Deleting an account does not automatically migrate data tied to the account into local data that is not associated with an account. Users who want to keep their data should, before deleting their account, perform a manual backup of the Service (exporting a backup ZIP) and store it in a location such as outside the device. Restoring a backup ZIP is applied to the storage the app is using at the time of restoration (the data of the account you are logged in to, or the data on this device used without signing in). Restoring a backup ZIP replaces the current colors, trash, and editing history at the restoration destination (and the works album, when the backup includes one); it is not merged automatically. A deleted account cannot be recovered, and restoring a backup ZIP does not bring back the account or the Pro purchase entitlement.

If, after server-side account deletion is completed, deletion of data on the device cannot be completed for any reason, the Service does not treat that operation as a fully successful deletion.

Deleting an account does not automatically cancel a Pro Google Play subscription, and the Operator's account deletion does not delete the purchase and billing records held by Google Play. The handling of customer information and purchase and subscription records held by RevenueCat is as described in the retention provisions above. Users can cancel their subscriptions through Google Play's subscription management screen.

14. Disclosure, Correction, Suspension of Use, Deletion, and Other Requests

With respect to information about themselves handled by the Operator, users may, in accordance with law, request notification of the purposes of use, disclosure, correction, addition, deletion, suspension of use, erasure, or suspension of provision to a third party.

To make a request, please contact contact@remiora.app. The Operator will respond in accordance with law after verifying the user's identity.

Details of the procedure, identity verification methods, and other necessary matters will be provided according to the contents of the request.

15. Security Management Measures

The Operator takes necessary and appropriate security management measures, including access control, protection of authentication information, management of the minimum necessary permissions, and review of service providers, to prevent unauthorized access, leakage, loss, or damage to handled information.

Specific details of security management measures will be provided in response to a request from the person concerned to the extent that doing so does not interfere with security management.

16. Personal Information Handling Business Operator and Contact

Personal information handling business operator: Remiora Operator

The name, address, and telephone number will be disclosed without delay upon request.

Contact for requests, inquiries, and account deletion: contact@remiora.app

17. Revisions

The Operator may revise this Policy as necessary.

For important changes, the Operator will provide notice on the Service or by another appropriate method and will request agreement to the revised Policy as necessary.