Privacy Policy

1. General principles

ODDDAY handles only information needed to provide a service. Records that remain on the device differ from information sent to servers or other providers. Please check each service's section for data accessed, collected, used, shared, retained and deleted, and for any applicable third-party services.

If features that transfer data externally are added, ODDDAY will describe their purpose and practices, and provide notices or request consent where required. This shared page is not a complete disclosure for an app that has not yet been documented here.

2. DAY.zip — D-Day, anniversaries and expiration dates

Applies to: DAY.zip for Android and Web · Based on the currently published app features

2.1 Information stored locally and its uses

Dates, titles, notes, card colors, ordering, language, and appearance settings that you enter are saved in the app or browser storage on your device. They are used to display, sort and customize date records and home screen widgets. There is no feature that sends these records to the developer's server or synchronizes them to a server. No account or login is required.

2.2 Android app data and permissions

Under its currently published policy, the Android app bundles its interface and functions locally and does not request internet access or contain advertising or usage analytics SDKs. It does not request access to the camera, location, contacts, photos, or broad file access. For importing and exporting backups, it accesses only files that you choose through the system file picker. Automatic Android app-data backup is disabled.

Home screen widgets use a local copy of date records and the display settings you select; selected titles and day counts may appear on widgets. Notifications are not currently offered and notification permission is not requested. Widget display updates are requested following device restarts and changes to date or time zone.

2.3 Website and hosting providers

The web version loads application and installation files from a hosting provider. Technical connection information may be processed under the provider's connection and security practices. The web version does not synchronize date records to the developer's server and does not use advertising or usage analytics tools. Browser and Android local records do not sync automatically.

2.4 Retention, security and deletion

Local records remain until you delete them or clear the app or browser's stored data. You may delete individual records or clear the app data in Android settings. For the web version, clear the corresponding browser site data to remove its records.

Exported backups may contain dates, notes and settings. They are saved to the location that you select without additional encryption. If you use cloud storage, that service's policies apply. Exported files are not automatically removed when app records are deleted, and you must delete them separately.

Access controls and the security of the device and storage provider also affect the protection of locally stored information and exported backup files.

Advertising notice: The current DAY.zip closed-testing version does not contain advertising SDKs. If Google AdMob advertising or analytics is introduced, this policy and the app's Google Play Data safety declaration will be updated before activation to explain relevant SDK data practices, third parties, purposes and consent requirements.

3. Rough-log — Notes and diaries

Rough-log section updated: November 1, 2026

3.1 Information handled and its uses

Anonymous or Google sign-in uses a service account identifier, authentication information supplied by Google such as email and name, and login sessions for account identification and synchronization. Original notes, revision history, events and transactions, AI analysis, diaries, Best selections, reflections, and user edits are used to display records, calculate statistics, and generate diaries and reflections. Notes may include personal information about people, places, spending, feelings, or exercise. Profiles and preferences maintain your settings; AI call and token usage records manage processing and usage limits.

A daily photo you select is stored in private Supabase storage for display across devices. The browser resizes it and the server removes metadata such as EXIF and GPS; the original file is not stored. Photos are not analyzed by AI or sent to the AI provider. Personal information visible in a photo can remain in its image content.

AI task types, times, status, token usage and server error codes support processing, usage limits and troubleshooting. Search terms are not stored as a separate server-side search history. The Android ad-preparation version includes Google Mobile Ads and UMP for privacy choices. Production advertising is currently disabled. Ordinary web pages and diary-writing screens do not request or display ads. Authentication and hosting providers may process connection information such as IP address and user agent to operate their services.

3.2 External services

Google OAuth provides sign-in. Supabase provides authentication, databases, private photo storage and server processing. Netlify hosts the current website. The previous Vercel website remains available for compatibility with earlier app versions. When you request AI analysis, a diary or a reflection, the necessary notes and organized information are sent to the OpenAI API. Generation requests currently use store:false; this does not mean that all provider technical logs or backups are immediately deleted. GitHub Pages hosts this notice and Gmail receives support inquiries.

The operator is still verifying providers' exact retention periods, processing locations and applicable international-transfer terms and disclosures. Unverified countries, durations or legal obligations are not presented as established facts.

3.2.1 Preparation for optional rewarded ads

In an Android version with advertising enabled, a rewarded ad is shown only after you choose and confirm viewing on a separate reward screen. Writing, editing and reading records do not require viewing ads. UMP checks privacy choices before an ad request. Where offered by the applicable region and message, you can change choices or withdraw consent through the reward screen's ad privacy options. Test ads also use the advertising SDK.

When the advertising SDK is used, Google may process IP addresses (including to estimate general location), app/ad interactions, diagnostics and device/account identifiers such as advertising IDs and app set IDs for ads, analytics and fraud prevention. Applicable identifiers and ad handling depend on device settings and privacy choices. See Google's SDK data disclosure and Google's Privacy Policy.

The app does not send diary text, photos or email to AdMob as ad-personalization or reward-verification data. It sends a random server-issued request identifier for reward verification. The server verifies the transaction identifier, ad unit, reward and time in Google's signed callback and links the result to the app account's credit. These records support granting and tracking credits and preventing duplicate grants. Production reward granting is currently disabled.

3.3 Account deletion and data deletion

Account deletion removes the Rough-log account, profile, preferences and related records. Data deletion keeps the account, Google sign-in, profile and preferences while removing records for selected dates or all records. Neither action deletes your Google account.

These pages explain the in-app paths and how to request deletion by email without signing in. You can delete directly through account or data management in Settings, or email if you cannot sign in. An email address alone is not sufficient: ownership is verified separately through the account's verified mailbox.

3.4 Retention and deletion

The service account and records are retained to provide features until you delete them. Data-only deletion preserves the account, profile, preferences and sign-in link. Date-specific, all-data and account deletion include photos and associated records within that scope. Photos can also be deleted individually from Today or Calendar. Completed server deletion jobs remove user identifiers and target lists; minimal completion receipts are removed by a daily cleanup after seven days. Failed requests retain minimal identifying information and status until processing is completed.

Data-only deletion retains account-linked, content-free AI usage, cost and reward-use records so that deleting notes does not reset usage limits; references to deleted source notes are removed. Account deletion removes account-linked usage and reward records, retaining only daily totals by task type and model for calls and costs, without account identifiers or note content, for service budget management. Credit expiration is separate from deletion of operational records; the operator is still verifying their specific retention and automatic expiration periods.

You must delete exported files yourself. Actual retention or expiration of support emails, provider backups, connection and security logs, and any separate legal retention requirements are still being verified. No uniform email-request completion deadline has been established. We explain confirmed scope, timing and retention exceptions after receiving a request, without presenting unverified periods as legal requirements or promising immediate complete erasure.

4. Contact and updates

Developer and operator: ODDDAY
Privacy inquiries: team.oddday@gmail.com

When a service changes how it handles data, ODDDAY will update the relevant parts of this policy and provide in-app or in-service notices where required. New ODDDAY services will be added only after their data collection, use, sharing and deletion processes have been confirmed.