Privacy policy
The operator, contact details, response times, and retention policies have not been finalized. Check the information below for the effective policy and whether requests are being accepted.
App: Day in Four (com.fourfold.journal)
Operator: To be confirmed
Privacy and deletion inquiries: Contact details coming soon
Effective date: To be confirmed before launch
This policy explains how the Day in Four app and its website handle personal information. Optional Google sign-in, Plus payments, and Google Drive backups apply when these features are offered in the released version and you choose to use them.
1. Information, purposes, and storage
| Category | Information | Purpose and storage |
|---|---|---|
| Diary and photos | Selected or captured photos, diary text, dates, moods, weather, tags, favorites, editing details, drafts, and recovery records | Creating, finding, displaying, and exporting entries. Stored by default in app-specific storage on your device. Diary content is not uploaded to the developer’s server. |
| Settings | Theme, language, reminders, app lock, and display settings | Remembering your preferences. Stored on your device. |
| Plus account | Google authentication identifiers and provided basic profile details, such as email, name, and profile image; app user ID; authentication sessions | Google sign-in, Supabase authentication, and linking subscription access. The information provided depends on the Google consent screen. |
| Subscription | Purchase tokens, product and plan IDs, subscription status, expiry and verification times, and account-linking identifiers | Verifying Google Play purchases and managing Plus access. Tokens are encrypted when stored on the server. The app does not directly process card numbers. |
| Optional backups | Diary entries, photos, and related metadata included in a backup | A file location you select or your own Google Drive app data area. Drive access is used for backups. |
| Support and deletion requests | Reply email address, account identifiers you provide, and the content of your request | Verifying identity and handling your request. Do not include passwords, verification codes, or original diary entries. |
2. Sources and optional permissions
Photos come from items you select in the system photo picker or capture with the camera. Optional notification permission is used for diary reminders. The current app does not request contacts, location, or microphone permissions. Google sign-in and Drive connections require separate consent.
3. External services and data processing
Google handles sign-in, Google Play payments, and Drive backups you connect. Supabase supports server processing for Plus authentication and subscription verification. Diary entries and photos are not sent to the Plus authentication or payment server. If you share images or PDFs or store backups with another service, that service’s policies apply.
Processing countries, regions, and international transfer details: To be announced once the operating environment is finalized. Processors, destination countries, data categories, purposes, transfer methods, retention periods, and related procedures must be confirmed before launch.
See the Google privacy policy, Supabase privacy policy, and GitHub privacy statement.
4. Retention and deletion
You manage records stored on your device. Deleting an entry may leave trash or recovery data. To remove all app data on a device, clear the app’s storage in Android settings or uninstall the app. Separately saved photos, PDFs, backup files, and Drive data are not removed by this action.
Retention of account, payment, and support records and residual data after deletion: The operating policy is not yet final. Retention periods for each data category, deletion timing, server backup removal, and the basis, scope, and duration of any legally required retention will be specified in the final policy.
Drive backup is designed to retain up to three recent snapshots per device. Older photo fragments may remain, so replacing a snapshot does not necessarily completely delete all original data. See the deletion guide for removing Drive app data.
5. Access, correction, deletion, and withdrawal of consent
You can view and edit on-device diary entries in the app. Use the privacy contact above to request access to, correction or deletion of, or restrictions on processing account information and support records. Limited identity verification may be needed. See account and data deletion for instructions by data type.
6. Safeguards
Account, payment, and Drive communications use HTTPS. Authentication sessions and purchase tokens are protected according to their storage mechanisms. Diary data is managed in app-specific storage. Exported backups, PDFs, and images may contain personal records, so choose where you share them carefully.
7. Advertising, analytics, and this website
The free version includes Google AdMob banner ads and limited full-screen ads after a diary entry is saved. Ads are not shown while Plus is active. For advertising, measurement and fraud prevention, the advertising SDK may process IP addresses (which may be used to estimate general location), advertising/app identifiers, interactions and diagnostic information. The app does not add diary text, photos or tags to ad requests. Where required, consent is collected before requesting ads; an Ad privacy options entry in Settings lets you update applicable choices. You can also reset or delete your advertising ID in Android settings. Refer to Google’s privacy policy for its data handling. This website does not use advertising scripts, visitor analytics scripts, or tracking cookies. GitHub may process connection information, such as IP addresses, when hosting the site on GitHub Pages. Text entered in the deletion request form is not sent to or stored on this site’s server. It is processed by your email service and the recipient only if you actually send it from your email app.
8. Policy changes
Material changes to data categories, purposes, or external services will be announced on this page and, where needed, in the app. Any necessary consent procedures will be followed. Refer to the version with a confirmed operator and effective date.