PRIVACY POLICY

Privacy Policy

Orange Memo provides the features you need to manage your records. This document describes only the data processing found in the current app code.

Effective: August 25, 2026

1. Information stored on your device

Orange Memo stores the following information that you enter or add in your device’s SQLite database and app storage, not on Orange Memo’s own servers.

• Notes, tasks, events, projects, and related titles, content, dates, and status information
• Attachments, photos, and voice memos that you add or share
• App settings, backup-folder location, Google Calendar connection, and sync status

The current app has no separate server account database and does not sync or transmit this local data to Orange Memo’s own servers.

2. Optional sign-in

If you choose Google or Kakao sign-in, the provider identifier, user ID, email address, display name, and sign-in time received from the provider are stored in the device’s secure storage. This information is used as a local session for optional in-app features.

The current app code does not send this sign-in information to Orange Memo’s own servers or create an account there.

3. Google Calendar

Only when you choose to connect and sync Google Calendar does the app request Google Calendar permissions through Google OAuth. The app may find or create an Orange Memo–dedicated calendar and exchange event titles, notes, start and end times, all-day status, and app-identification metadata with the Google Calendar API.

The connected account ID and email, calendar ID, and sync status are stored on the device. You can disconnect Google Calendar in app settings.

4. Email and backups

When you choose to email, the app passes the selected record’s body and attachments to the compose screen of the mail app installed on your device. You send the message from that mail app.

Full backups are saved to the device folder you choose when you create them. They are not automatically uploaded to Orange Memo’s servers. Whether that folder is synced by an external cloud service depends on that provider’s policies and settings.

5. Attachments

Files added through the camera, photo picker, file picker, or device sharing are copied into the app’s storage. They are passed elsewhere only when you choose device export or email, and only as needed for that feature.

6. Advertising

The Android app uses the Google Mobile Ads SDK to display banner advertising and provide ad-privacy choices and consent flows. Information handled by ad requests and the advertising SDK is governed by Google’s policies.

The app code does not show use of a separate analytics SDK such as Firebase Analytics, Sentry, or Amplitude.

7. External transmission

External communications found in the app code are optional Google or Kakao sign-in, Google Calendar integration, the device mail app, and the Google Mobile Ads SDK. Supabase schemas and environment examples exist, but no actual Supabase sync or API call is connected in the current app.

8. Privacy inquiries

For questions about this policy, privacy processing, or account and data deletion, email us below.