Attadiary Privacy Policy
Version: Launch draft v0.1
Effective date: November 14, 2026
FABLELAB (페이블랩, the “Operator”) processes personal information as described below to provide Attadiary. This policy applies to the app, customer support, and account and data deletion requests.
1. Information and purposes
| Feature | Information processed | Purpose |
|---|---|---|
| Google sign-in and accounts | Google account identifiers and email, service user identifier, authentication and session information | Account verification, sign-in, account separation and security |
| Registration and required documents | Date of birth, language, consent document types, versions, timestamps and request identifiers | Confirm eligibility at age 14, provide localized documents and maintain consent history |
| Profile and settings | User-selected nickname, introduction, profile appearance and app settings | Display profiles and apply preferences |
| Records, synchronization and statistics | User-entered titles, bodies, dates, moods, keywords, activities, templates and related change/deletion information | Store, display, search, synchronize and restore records and provide the user's own statistics |
| Photo attachments and backup | Selected photos, attachment associations, Google Drive backup information and permissions, and the backup encryption key the server creates and keeps for each account | Display photos and provide backup and restoration, and encryption of backup data |
| Notifications | Notification preferences, push registration tokens and delivery/processing status | Deliver requested notifications and apply preferences |
| Customer support | Submitted inquiries, replies, handling status and account associations | Answer inquiries, resolve issues and handle disputes |
| External deletion requests | Google Forms verified email, submission time, selected reason and confirmation, request/processing status | Match the account and process deletion, cancellation and completion |
| Diagnostics | App and operating system versions, device information, installation identifier, error type, stack, error identifier and limited state information | Diagnose errors and improve reliability |
Required information is processed only as needed for the relevant feature. You may choose not to use optional features or change supported settings. Declining information processing or permissions necessary for a feature may limit that feature.
Records contain content freely entered by users. Avoid unnecessarily recording other people's personal information. The Operator does not ask for sensitive information such as health conditions or collect it as a separate item. Content you write in your records is processed only to store, synchronize and back it up and to show you your own records, search results and statistics. It is not used for advertising or user profiling and is not disclosed to other users.
2. Collection and storage
Information is processed through Google sign-in, app use, direct entry, photo selection, synchronization, backup, support requests and deletion form responses.
Records are stored on the device and processed through server synchronization. When using Google Drive backup, backup data is stored in the connected Google account's app-specific space. Photo files are stored on the device and included when using Drive backup. Photo identifiers and attachment metadata associated with records are processed separately through record functions. The record database and photo files are encrypted on the device, and the service server does not store photo files. Drive backup data is encrypted with a per-account key before it is stored. The key is kept on the service server for each account and deleted when account deletion is completed. After the key is deleted, backup data remaining in Drive can no longer be restored.
Deletion form responses are collected in a private Google spreadsheet managed by the Operator and checked by the server. Public Notion pages provide this policy and service information; diary content and raw deletion responses are not published there.
The primary service database is located in the Sydney, Australia region.
3. Error diagnostics
The Operator automatically collects diagnostic information using Firebase Crashlytics. This may include app version, device and operating system information, installation identifiers, error time, stacks and predefined state categories.
The app removes or limits diary titles and bodies, actual mood values, search terms, account emails, authentication tokens and server response bodies in error reports. Record processing necessary for service features is separately described in section 1.
Under Google's policy, the relevant Crashlytics diagnostic data is retained for 90 days before removal from live and backup systems begins. Processing suspension and other rights requests may be submitted through the contact below. Diagnostics are processed on the basis of the Operator's legitimate interest in finding and fixing failures (Article 15(1)(6) of the Personal Information Protection Act of Korea), limited to what diagnosis requires. Diagnostic data does not contain your account email or service account identifier, so the Operator cannot single out the diagnostic data of a particular user. On request, the Operator reviews the request and tells you what can be done and the result. Uninstalling the app stops new diagnostics from that device.
4. Retention and destruction
| Information | Retention and deletion |
|---|---|
| Accounts, profiles, service records and preferences | Processed while needed for the purpose; destroyed without delay upon completed account deletion or fulfillment of the purpose, with legally required records handled separately |
| Accounts awaiting deletion | Until deletion is completed following a 72-hour waiting period from the request; signing into the service before completion cancels the request |
| Google Forms/Sheets deletion submissions | Form responses and the matching sheet rows are deleted within 30 days after the deletion is completed |
| Consent history (document type, version and time) | Kept separately with the link to the account removed; destroyed 5 years after completed deletion (proof of consent and dispute handling) |
| Free-trial duplication check value | A one-way transformed value of the Google account identifier; deleted automatically 365 days after completed deletion |
| Deleted-account check value | A one-way transformed value of the service account identifier, used to link transaction records; destroyed 5 years after completed deletion |
| Drive backup encryption key | Deleted when account deletion is completed |
| Diagnostics | Provider retention and deletion policy in section 3 |
| User Google Drive backups | Managed in the connected Google account; deleting the service account does not automatically delete existing Drive files |
Where law requires retention of transaction records, only the relevant information is retained for that purpose. For transactions covered by Korean electronic commerce law, contract/withdrawal and payment/supply records are retained for five years, consumer complaints/disputes for three years, and advertising records for six months. The free beta is not treated as generating paid transactions that did not occur.
Electronic information is destroyed using methods that prevent recovery or reproduction. Where database backups are operated, data remaining in a backup is removed when the backup retention cycle (up to 7 days) ends. Data remaining in processors' systems is deleted under each processor's deletion procedure; diagnostics follow the period in section 3 and push registration data follows Google's policy (up to 180 days after removal begins).
5. Processing providers and external services
The Operator entrusts the following processing tasks to provide the service.
| Processor | Entrusted task | Information processed |
|---|---|---|
| Supabase, Inc. | Authentication, service database and server functions | Information stored on the server, such as account, profile, records, settings, consent history, support requests, notification tokens and the backup encryption key |
| Google LLC (Firebase Crashlytics, Firebase Cloud Messaging) | Diagnostics and push delivery | Diagnostic data, installation identifiers and push registration tokens |
| Google LLC (Google Forms, Sheets and Gmail) | External deletion intake and support email | Form responses (email, submission time, reason) and support email content |
| RevenueCat, Inc. | Entitlement and subscription status integration | Service account identifier, app and device information, subscription status |
| Plus Five Five, Inc. (Resend) | Sending service emails such as app-lock reset | Email address and email content |
| Vercel Inc. | Hosting of the operator administration website | Information an operator views to handle support and account requests |
| Cloudflare, Inc. | Domain and public web delivery, support email forwarding | Access records (such as IP address) and support email |
Google sign-in and Google Drive are services you use directly with your own Google account and are subject to Google's policies. The Operator does not pass users' personal information to Notion, which hosts the public documents. Entrusted processing is not treated as third-party provision, and the Operator does not provide users' personal information to third parties. If third-party provision becomes necessary, the basis and items will be explained separately and any required consent obtained.
6. International transfers
The Operator transfers personal information overseas as follows, for entrusted processing and storage necessary to perform the service contract (Article 28-8(1)(3) of the Personal Information Protection Act of Korea).
| Recipient (contact) | Country | Information | Purpose | Timing and method | Retention |
|---|---|---|---|---|---|
| Supabase, Inc. (privacy@supabase.com) | Australia (Sydney) | Supabase items in section 5 | Authentication, service database and server functions | Sent over the network at sign-up and during use | Until completed deletion or the end of the entrustment; separately retained items follow section 4 |
| Google LLC (contact guidance at policies.google.com/privacy) | United States and other countries with Google data centers | Diagnostic data, installation identifiers, push registration tokens, deletion form responses, support email | Diagnostics, push delivery, deletion intake, support email | Sent over the network when the feature is used | Diagnostics 90 days; other items follow section 4 |
| RevenueCat, Inc. (compliance@revenuecat.com) | United States | Service account identifier, app and device information, subscription status | Entitlement and subscription status integration | Sent over the network when the app runs | Until completed deletion or the end of the entrustment |
| Plus Five Five, Inc. (support@resend.com) | United States | Email address and email content | Sending service emails | Sent over the network when an email is sent | Delivery processing and the provider's log retention period |
| Vercel Inc. (privacy@vercel.com) | United States | Support and account information viewed by an operator | Hosting of the operator administration website | Sent over the network when an operator views it | During the request; not stored separately |
| Cloudflare, Inc. (privacyquestions@cloudflare.com) | United States and countries with Cloudflare locations near the user | Access records (such as IP address) and support email | Public web delivery and support email forwarding | Sent over the network on access or when an email is sent | Forwarding and the provider's log retention period |
If you do not want the transfer, you can refuse it by deleting your account or by not using the relevant feature (notifications, support requests and so on). In that case all or part of the service cannot be used. Google Drive backup stores data directly in your own Google account, and the service can be used without it.
7. User rights
Under applicable law, you may request access, correction, deletion, suspension of processing, withdrawal of consent and, where applicable, transmission of personal information. Use the app to manage information supported by its edit/delete features. Other requests may be submitted through the contact below.
The Operator verifies identity only as necessary and follows applicable procedures and deadlines. If a request must be limited, for example because another law requires retention, the reason will be explained. Information beyond what is needed to exercise rights is not requested.
8. Safeguards and automatic collection
The Operator applies the following safeguards: encryption in transit; account-level access control so that users can read and change only their own data; encryption of the on-device record database, photos and Drive backups; storage of sign-in information in the device secure storage; two-step verification and least-privilege access for operator accounts; limits on failed sign-in attempts; and retention and review of operator activity records.
The app does not use the Firebase Analytics SDK for advertising analysis. Public documents are provided as public Notion pages. When you open them, Notion may process cookies and access records under its own policies, and you can refuse cookies in your browser settings (Notion Cookie Notice). The Operator's introduction website does not use analytics or advertising cookies; the hosting provider processes access records such as IP addresses for delivery and security.
9. Privacy contact
Privacy officer or responsible team: FABLELAB privacy contact
Email/contact: support@attadiary.com
You may use in-app support or the contact above if you cannot access the app. For counselling or remedies regarding privacy infringement, you may contact the following Korean authorities.
- Personal Information Dispute Mediation Committee: 1833-6972, www.kopico.go.kr
- Personal Information Infringement Report Center: 118, privacy.kisa.or.kr
- Supreme Prosecutors' Office: 1301, www.spo.go.kr
- Korean National Police Agency: 182, ecrm.police.go.kr
10. Policy changes
When this policy changes, the effective date and the changes are announced in the in-app notices and public documents at least 7 days before the effective date. Changes with a significant effect on users' rights are announced at least 30 days in advance, and consent is obtained where the law requires it. Previous versions will remain available through history links.
- November 14, 2026 — First publication.