Privacy Policy

1. What data ASAKI accesses

With your explicit Google sign-in consent, ASAKI accesses the following on your device to assemble your morning briefing:

• Google Calendar events for the current day (titles, times) — read on-device through Android's CalendarProvider.
• Gmail metadata — the subject, sender, and short snippet of recent messages. ASAKI does not read, request, or store the body of your emails.
• Tasks you type into ASAKI — stored only on your device.

ASAKI does not access your contacts, location, photos, or any Google data beyond what is listed above.

2. Gmail metadata scope

ASAKI requests a single, restricted Gmail scope:

https://www.googleapis.com/auth/gmail.metadata

This scope grants access to message metadata only — headers such as subject and sender, plus a short snippet — and cannot retrieve message bodies or attachments. ASAKI uses it solely to produce an at-a-glance email summary inside your morning briefing. We do not use Gmail data for advertising, profiling, or any purpose other than presenting your briefing to you.

3. Where your data goes

Your calendar and email data are processed on your phone. Your Google OAuth tokens are stored on-device in the Android Keystore and are never transmitted to us.

ASAKI's email triage and briefing assembly run locally using rule-based, on-device logic. In cases where a short text snippet (for example, a list of email subjects) is sent to ASAKI's self-hosted summarization service to improve a summary, only that minimal snippet is transmitted — never your message bodies, your full inbox, or anything that identifies you. That request carries no user account or identity, and the snippet is deleted immediately after processing. We use no OpenAI, no Google AI, and no third-party AI provider.

4. No accounts, no server-side storage

ASAKI has no user accounts and no login on our servers. We do not create a profile for you, and we hold no database of users. Because there is no server-side identity, your briefing data is not associated with you anywhere off your device.

5. Data retention & deletion

• On your device: calendar/email data exists only transiently while a briefing is being built; tasks persist locally until you delete them or uninstall the app.
• On our service: any snippet sent for summarization is deleted immediately after the response is returned. Nothing is logged or retained.
• Uninstalling ASAKI removes all on-device data, including stored tasks and your Google tokens.
• You can revoke ASAKI's access at any time from your Google Account permissions.

6. Sharing & third parties

We do not sell or rent your data. We do not share your email, calendar, or briefing content with any third party — the only exception is the minimal, immediately-deleted text snippet sent to ASAKI's own self-hosted summarization service, described in section 3. To keep ASAKI free we display ads through Google AdMob (section 7); AdMob does not receive your email or calendar content.

7. Advertising

ASAKI is free and supported by ads served through Google AdMob. We serve non-personalized ads — ads that are not based on your past behavior or an advertising profile.

To show ads, Google AdMob (acting as an independent third party) may collect and process standard advertising data from your device, such as your Advertising ID (a resettable identifier), IP address, general device information, and basic ad interactions (for example, that an ad was shown or tapped). Even for non-personalized ads, a limited amount of data is used for frequency capping, aggregated reporting, and fraud/abuse prevention. This data is handled by Google under the Google Advertising and Google Privacy policies.

Your Gmail and Google Calendar data are never shared with AdMob, never used to target or personalize ads, and never combined with advertising data. The advertising system and the briefing system are kept separate.

You can limit ad tracking or reset your Advertising ID at any time in your Android settings (Settings → Privacy → Ads). Where the law requires it (for example in the EEA, the UK, or certain US states), we will request your consent or offer the choices those laws require before showing ads.

8. Device permissions

ASAKI requests the minimum Android permissions needed to function as an alarm: scheduling exact alarms, posting the alarm notification, running over the lock screen, and microphone access for the spoken wake phrase. Voice is recognized on-device; audio of your wake phrase is not recorded to a file or sent off the phone.

9. Google API Services User Data Policy

ASAKI's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used only to provide and improve the user-facing morning-briefing feature, is not transferred to others except as necessary to provide that feature (the minimal, immediately-deleted snippet in section 3), is not used for advertising, and is not read by humans except with your consent or as required for security or law.

10. Children's privacy

Because ASAKI is not a child-directed app, ads are treated as general-audience; we do not knowingly serve ads to, or collect data from, children.

ASAKI is not directed to children under 13 (or the minimum age in your jurisdiction) and we do not knowingly collect their data.

11. Changes to this policy

If this policy changes, we will update the effective date above and post the revised policy at this URL. Material changes will be reflected before they take effect.

12. Contact

Questions about privacy, or a data request? Email [email protected].