This is the previous Privacy Policy, in effect from October 10, 2026 through October 13, 2026. View the current Privacy Policy

Plantri

Privacy Policy

Revision announced: October 10, 2026 · Effective: October 10, 2026

Plantri (the “App”) values your privacy and complies with the applicable laws of the Republic of Korea, including the Personal Information Protection Act. This policy explains what information the App collects and how it is used, stored, and deleted.

What changed in this revision (announced and effective October 10, 2026)
1. We added what Plantri reads when you connect Google Calendar directly, how it is used, stored, shared, disconnected and deleted, and our compliance with the Google API Services User Data Policy, including the Limited Use requirements (Section 1.10).
2. We corrected the device calendar permission entry: Plantri reads events from your device calendar and keeps timed events as schedule items on the device and, if you are signed in, in the cloud (Section 1.3).
3. We now state that the schedule context sent to AI features can include events imported from your device calendar or Google Calendar (Sections 1.8 and 5.2).
Reason: this revision explains in more detail how the existing Google Calendar connection and AI features already process data. What we collect and how we use it do not change, so it takes effect on the day it is announced (see Section 11).

1. Personal information we collect

1.1 Sign-up and sign-in

Email address provided by your Google or Apple account
Name, if provided by your Google or Apple account
Unique user identifier (UID) randomly assigned by Firebase Authentication

1.2 Information you enter

Schedules and to-dos: titles, times, categories, notes, completion status, and ratings
Journal entries and quick notes: text, ratings, mood emoji, automatically extracted tags, and photos you choose to attach
Memos: text, categories, and photos you choose to attach
Schedule backgrounds: background photos you select
Goals: core goals, subgoals, and action items
App settings: preferred form of address, character, font/theme, notification times, and similar settings

1.3 Device permissions

Permission	Purpose	Storage
Photos/Camera	Select photos for memos, journals, and schedule backgrounds	Stored on the device by default; backed up to Firebase Storage only after separate consent
Calendar	If you turn on “Calendar sync”, read events from your device calendar (including Google and other accounts added to your device) and show them on your timetable and calendar	We read each event’s title, start and end time, and all-day status, and calendar account names so you can choose which accounts to import. Timed events are saved as your schedule items on the device (SQLite) and, if you are signed in, synchronized to Firebase Firestore under `users/{uid}`. All-day events are only displayed unless you add one to your schedule. We never change events in your device calendar.
Notifications	Deliver morning briefings and schedule alerts	Only notification tokens are stored on the device

1.4 Automatically collected technical information

App version, device type, OS version, and language setting collected by Firebase
Authentication and App Check tokens used for security verification

1.5 Firebase Analytics

To operate and improve the App, Firebase Analytics measures users and sessions, screen and feature journeys, exits, and execution success or failure. Before continuing to use the App, you must freshly acknowledge and consent to the operational analytics and minimal crash-diagnostic scope. An old optional choice or refusal does not automatically grant this new scope.

Under Settings → Analytics, crash and ad measurement consent, you can withdraw consent on this device. This stops reporting and returns to the required-consent screen without deleting your account email, schedules or memos. These are not fully anonymous counts: Analytics uses an app-instance identifier and a signed-in account’s pseudonymous Firebase UID.

We collect app/device information and language/country. We do not send raw email, names, written journal/schedule/memo/goal content, search text, or advertising identifiers to Analytics.

We do not collect advertising identifiers (IDFA or Android advertising ID), and we do not display Apple’s App Tracking Transparency permission prompt. However, as described in Section 1.9, we share install, open and purchase information with Meta to measure Plantri ads.

1.6 Crash diagnostics (Firebase Crashlytics)

Release builds use Firebase Crashlytics for minimal diagnosis of crashes and application errors only after the fresh operational acknowledgement above. This is not controlled by the legacy optional-detail flag. Crash consent is applied independently even if the Analytics SDK is temporarily unavailable.

Error types, stack locations and relevant application state. Dart reports sent by the App omit raw exception messages and redact emails, user home paths and URL queries from stacks. Native SDK reports may contain native exception diagnostic information.
App version and device information such as model, OS version, memory, storage, and screen orientation
Event timestamp, Crashlytics installation UUID, and Firebase installation ID
When Firebase Analytics is enabled, screen and feature-use events immediately preceding the error

We do not set email address, name, or Firebase UID as a Crashlytics user identifier, and we do not intentionally attach the body text of journals, schedules, memos, or goals to crash reports.

1.7 Optional profile survey

We may optionally ask for your age range and gender to understand service use and improve features. You may skip the survey without losing access to any feature. Responses are stored only as Firebase Analytics user properties and in your own account data under users/{uid}, can be edited under Settings → Profile Survey, and are deleted with your account.

1.8 AI feature request data (separate consent)

Only when you invoke an AI assistant, goal-planning, coaching, or insight feature and separately consent, we send your request and the limited schedule, goal, or journal context needed for that feature to the OpenAI API. The schedule context can include the titles and times of events imported from your device calendar or Google Calendar (for example, for AI assistant answers and the morning briefing). We do not send your email address or Firebase UID.

1.9 Ad measurement (Meta)

We use the Meta App Events SDK to measure whether Plantri ads on Facebook, Instagram and Threads led to installs and Pro purchases, and to optimize who sees those ads. It runs only after you confirm the required consent together with the operational analytics and crash diagnostics scope in Section 1.5; nothing is sent before that.

What we share: that the App was installed and opened, when, and how long it was used; first Pro purchases, free-trial starts and conversions, and subscription renewals, with product ID, amount and currency (purchases confirmed by the store are sent to Meta by the servers of our payment provider RevenueCat); app version, OS version, device model, language/country, time zone, screen size and similar technical information, and IP address; a random identifier the Meta SDK creates inside the App; and a one-way hashed version of your account identifier (Firebase UID) used to link purchases to that information.

What we do not share: advertising identifiers (IDFA, Android advertising ID), email address, name, raw Firebase UID, or the text of your journals, schedules, memos or goals. We do not show the iOS App Tracking Transparency prompt.

You can withdraw consent for this device under Settings → Analytics, crash and ad measurement consent; sending to Meta stops immediately and the Meta identifier stored with RevenueCat for purchase reporting is deleted.

1.10 Google Calendar connection (optional)

Only if you tap Settings → Calendar → Integrations → Google Calendar → Connect and grant access with your Google Account, Plantri uses the Google Calendar API’s read-only scope (calendar.readonly) to read the information below. Plantri never creates, changes or deletes anything in your Google Calendar.

What we read

Your calendar list and whether each calendar is turned on (shown) in Google Calendar
For the calendars you have turned on and the period you are viewing: each event’s title, start and end time, and all-day status (with the event identifier used to show each event only once)
Other fields Google returns, such as description, location and attendees, are not stored or used.

How we use it: only to show your events on your own timetable, monthly calendar and home-screen widgets, and to bring timed events into your Plantri schedule so you can plan your day.

Where it is stored

Requests go directly from your device (or your browser on the web) to Google. Your Google access token is managed by Google’s sign-in library on your device and is never sent to Plantri servers.
Timed events are saved as your schedule items on your device (SQLite) and, if you are signed in, synchronized to your own path (users/{uid}) in Firebase Firestore (Google LLC, United States). Other users cannot access them.
All-day events are only displayed and are stored only if you add one to your schedule. To keep events you deleted or hid in Plantri from coming back, only their event identifiers are kept on your device.

Sharing and AI features

We do not sell Google user data, use it for advertising (including personalized or retargeted ads), or send it to Meta (Section 1.9) or Firebase Analytics (Section 1.5). Analytics records only whether a connection succeeded and how many events were imported.
Only if you separately consent to AI features (Sections 1.8 and 5.2) and use them, for example the AI assistant or the morning briefing, the titles and times of imported events in the schedule context for the requested date are sent through Plantri’s server to OpenAI, L.L.C. (United States), solely to create the response you asked for. OpenAI does not use API data for model training (Plantri has not opted in) and may keep it in abuse-monitoring logs for up to 30 days. You can withdraw AI consent at any time under Settings → AI Data Sharing Consent.
No one at Plantri reads your Google Calendar data unless you allow it for a specific support request, it is needed for security, or it is required by law.

Protection: all transfers are encrypted with HTTPS. Under Firestore security rules, other users cannot read or write your cloud data, and Google Cloud encrypts it at rest.

Disconnecting and deleting

Tap Settings → Calendar → Integrations → Google Calendar → Disconnect and Plantri stops reading your Google Calendar. To also remove the access you granted, remove Plantri in your Google Account’s third-party access settings.
Events already imported stay as your schedule items and can be deleted one by one. Deleting your account under Settings → My Account → Delete Account deletes both the cloud and device copies, and deleting the App also removes the device copies.

Google API Services User Data Policy
Plantri’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Plantri does not use data received through Google Workspace APIs, including Google Calendar data, to develop, improve or train generalized (non-personalized) AI or machine-learning models.

2. Why we use personal information

Purpose	Information used
User identification and sign-in	Email address and UID
Cloud synchronization	Schedules, journals, memos, goals, and related settings
Photo backup and restoration	Selected photos, UID, generated filename, and upload time
Showing and importing device and Google Calendar events	Calendar information described in Sections 1.3 and 1.10, when you turn on sync or connect
Requested AI assistant responses, goal plans, coaching, and insights	Request and relevant context described in Section 1.8 after separate consent
Notifications	Notification token and time settings
Abuse prevention	App Check and authentication tokens
Analytics and feature improvement	Analytics information and optional profile survey responses
Error diagnosis and stability improvement	Crash diagnostic information described in Section 1.6
Ad measurement and ad delivery optimization	Install, open and purchase information and technical information described in Section 1.9

3. Retention periods

Data	Location	Retention
Schedules, journals, memos, and goals	Firebase Firestore under `users/{uid}`	Deleted immediately when the account is deleted
Consented photo backups	Firebase Storage under `users/{uid}`	Until the photo is deleted, consent is withdrawn, or the account is deleted
On-device cache and images	SQLite and App-only folders	Deleted when the account or App is deleted
Authentication data	Firebase Authentication	Deleted immediately when the account is deleted
Analytics data	Firebase Analytics	Automatically deleted under Google’s retention policy, generally within 14 months
Crash diagnostic data	Firebase Crashlytics	Retained for 90 days before Google begins deletion from live and backup systems
Ad measurement data	Meta Platforms, Inc.	Retained and deleted under Meta’s Business Tools Terms and data policy
Purchase and subscription records	RevenueCat, Inc.	Kept while you use the service for purchase restoration, refunds and support; deleted on request after account deletion

You may delete your account and data at any time through Settings → My Account → Delete Account.

4. Processors

Provider	Services	Country
Google LLC	Firebase Authentication, Firestore, Storage, App Check, Google Sign-In, Firebase Analytics, Firebase Crashlytics, and push notifications	United States
Apple Inc.	Sign in with Apple and App Attest	United States
OpenAI, L.L.C.	AI comment generation; submitted text is not used for model training	United States
RevenueCat, Inc.	In-app purchase and subscription management; with ad measurement consent, forwarding purchase information to Meta	United States

We do not send identifying information such as your email address or UID to OpenAI. Required text is sent only after you invoke an AI feature and separately consent. OpenAI API inputs and outputs are not used for model training unless Plantri separately opts in, and may be retained in abuse-monitoring logs for up to 30 days.

5. Overseas transfers

5.1 Cloud photo backup

Photos are transferred and stored overseas only after you separately consent to cloud photo backup. Without consent, photos stay on the device and cannot be restored after the App is deleted or the device is lost.

Item	Details
Legal basis	Article 28-8(1)(1) of Korea’s Personal Information Protection Act
Information	Attached photos, schedule backgrounds, Firebase UID, generated filename, and upload time
Recipient	Google LLC (Firebase Storage); privacy contact
Destination	United States (US-EAST1)
Timing/method	Encrypted HTTPS when a photo is attached or connectivity returns
Purpose	Backup and restoration after reinstalling or changing devices
Retention	Until deletion, withdrawal of consent, or account deletion
Withdrawal	Settings → Cloud Photo Backup; server backups are deleted on withdrawal

5.2 AI feature request data

Only when you invoke an AI feature and separately consent, the required text is transferred overseas as follows.

Item	Details
Data transferred	Your AI request and limited schedule, goal, or journal context needed for the feature; email address and UID are excluded. Schedule context can include the titles and times of events imported from your device calendar or Google Calendar
Recipient	OpenAI, L.L.C.
Destination	United States
Timing and method	Encrypted HTTPS through Plantri servers when you invoke an AI feature
Purpose	AI assistant responses, goal plans, coaching, and insights
Retention and training	Not used for model training; may be retained in abuse-monitoring logs for up to 30 days
Refusal and withdrawal	Withdraw under Settings → AI Data Sharing Consent. Refusal limits only AI features

5.3 Ad measurement data (Meta)

Item	Details
Data transferred	Install, open and purchase information, technical information, IP address, Meta SDK random identifier and hashed account identifier described in Section 1.9 (advertising IDs, email and raw UID excluded)
Recipient	Meta Platforms, Inc., Meta Privacy Policy
Destination	United States
Timing and method	After required consent, sent over encrypted HTTPS by the Meta SDK when the App is opened and by RevenueCat’s servers when a purchase, trial or renewal occurs
Purpose	Measuring installs and purchases from Plantri ads and optimizing ad delivery
Retention	Under Meta’s Business Tools Terms and data policy
Withdrawal	Settings → Analytics, crash and ad measurement consent. Because this is part of the required scope, withdrawing returns you to the consent screen

5.4 In-app purchase management (RevenueCat)

Item	Details
Legal basis	Article 28-8(1)(3) of Korea’s Personal Information Protection Act (processing and storage needed to perform our contract, disclosed in this policy)
Data transferred	Firebase UID, store purchase and subscription history (product, amount, currency, country, transaction ID, purchase and expiry times), technical information such as app and OS version, and, if you consented to ad measurement, the Meta SDK random identifier
Recipient	RevenueCat, Inc., RevenueCat Privacy Policy
Destination	United States
Timing and method	Encrypted HTTPS when the App is opened, a purchase is made, or purchases are restored
Purpose	Verifying purchases, managing and sharing Pro access across devices, and restoring purchases
Retention	Kept while you use the service; deleted on request after account deletion
Refusal	This processing is needed to provide purchases, so there is no separate opt-out; no purchase history is sent unless you buy Pro

5.5 Account and record sync (Google Firebase)

Only when you sign in, your account information and records are transferred and stored overseas as follows so they can be synced across devices and restored. If you use the App without signing in, your schedules, to-dos, memos, journals and goals stay only on your device and are not transferred overseas.

Item	Details
Legal basis	Article 28-8(1)(3) of Korea’s Personal Information Protection Act (processing and storage needed to perform our contract, disclosed in this policy)
Data transferred	Account information in Section 1.1 (email address, name, UID); records in Section 1.2 (schedules, to-dos and routines, journal entries and quick notes, memos, goals) and app settings; and your profile survey answers in Section 1.7, if you gave them. Photos are included only with the separate consent in Section 5.1
Recipient	Google LLC (Firebase Authentication, Cloud Firestore), privacy contact
Destination	United States (Cloud Firestore location: nam5, US multi-region)
Timing and method	Encrypted HTTPS when you sign in, and when you create or change records or open the App while signed in
Purpose	Managing your sign-in account, syncing across devices, and restoring data after reinstalling or changing devices
Retention	Until you delete the records or your account (deleted immediately when the account is deleted)
Refusal	If you use the App without signing in, your records are not transferred overseas; device sync and backup/restore are then unavailable

6. Third-party disclosure

Except for the ad measurement information shared with Meta Platforms, Inc. under Sections 1.9 and 5.3, Plantri does not provide your personal information to outside third parties, except when required through a lawful process such as a valid request from an investigative authority.

Recipient	Purpose	Information	Retention
Meta Platforms, Inc.	Ad measurement and ad delivery optimization	Information described in Section 1.9	Under Meta’s policies

7. Your rights

Access and correction in the App
Deletion of individual items or all data through account deletion
Withdrawal of photo-backup consent and deletion of server backups
Withdrawal of AI data-sharing consent under Settings → AI Data Sharing Consent
Disconnecting Google Calendar under Settings → Calendar → Integrations → Google Calendar → Disconnect, or by removing Plantri’s access in your Google Account
Withdrawal of analytics, crash and ad measurement consent under Settings → Analytics, crash and ad measurement consent (because this scope is required, withdrawing returns you to the consent screen)
Restriction or objection by contacting us below

8. Security measures

HTTPS for all server communications, Android cleartext blocking, and strict iOS ATS
Firestore rules limiting access to each user’s own users/{uid} data
The operator does not view the contents of your records (schedules, to-dos, journals, memos, goals and so on) except when you ask for or allow it to handle your inquiry, when needed for security such as responding to an incident, or when the law requires it
Firebase App Check using Play Integrity and App Attest
Android external backup and device-transfer restrictions
Release code obfuscation, separate debug symbols, and disabled release debug logs

9. Children under 14

Plantri does not knowingly collect personal information from children under 14. If we learn that a child under 14 attempted to create an account, we will delete it immediately.

10. Privacy contact

Business name: Bemony
Privacy officer: Representative of Bemony
Email: bemony.official@gmail.com
Response time: within five business days

11. Changes to this policy

We will announce changes and their reasons in the App or on this page at least seven days before they take effect, or 30 days in advance for changes that materially affect user rights. A change that narrows processing or immediately strengthens privacy and user choice may take effect promptly after notice with the reason stated.

This revision (October 10, 2026) explains in more detail how the existing Google Calendar connection and AI features process data. It does not change what we collect or how we use it, so under the exception above it takes effect on the day it is announced.