Privacy · Avenday

This policy describes how Avenday (“Avenday”, “we”) handles information in the Avenday mobile app and on this website. It applies to everyone who uses Avenday.

The short version

We collect what the app needs to run your family’s day, and not more.
We do not sell your information, and we do not serve advertising.
We do not use your family’s content to train our own or anyone else’s AI models.
If you connect Google Calendar, Avenday lists your calendars so you can choose which ones to bring in, then reads and writes the events on those, and touches nothing else in your Google account.
You can see everything Avenday believes about your family, correct it, or delete it.

What we collect

Information you give us

Account details: your name, email address, and the credentials or sign-in provider you use.
Family members: the names, colors and roles you set up for the people in your household, including children.
Your content: calendar events, plans, lists and list items, tasks, and the durable facts you record on the What Avenday knows screen.
Conversations: messages you send to Avenday AI, along with anything you paste, forward or attach to them.
Forwarded email: messages you or an approved sender forward to your family’s Avenday email address, including their attachments. Avenday keeps the message with your family’s files and reads it to pull out the dates, tasks and facts it contains.
Correspondence: what you write to us for support, and the email address you give us to join the early-access list.

Calendars you connect

If you connect Google Calendar, you authorize it through Google’s own sign-in, so we never receive or store your Google password. iCloud calendars work differently: Apple offers no such sign-in, so you create an app-specific password at appleid.apple.com and give it to Avenday. We store it encrypted, use it only to read and update your calendars, and it stops working the moment you revoke it at Apple. We access either calendar only with the permissions you grant, and only to show and organize your plans inside Avenday.

Google Calendar: the access we ask for. Avenday requests two Google OAuth scopes and no others:

https://www.googleapis.com/auth/calendar.calendarlist.readonly: read-only access to the list of calendars you are subscribed to. This returns their names, identifiers and colors, and none of the events on them.
https://www.googleapis.com/auth/calendar.events: permission to read and write events.

Why two. Avenday does not assume which of your calendars belong in your family’s week. After you connect, it shows you the calendars on your Google account, such as your own, a partner’s shared one, or a school or team calendar you subscribe to, and you tick the ones you want. The first scope exists to draw that list and does nothing else. The second does the actual work, on the calendars you ticked.

We use the access in both directions, and only in these ways. Reading: Avenday reads the events on the calendars you selected (their titles, times, locations, attendees, descriptions and recurrence) so your week appears in the app alongside your other calendars, and so the daily briefing knows what is already scheduled. Writing: Avenday creates, updates and deletes events on those calendars on your behalf, after you confirm the change in the app.

What these scopes do not allow. Neither scope lets Avenday create, delete or share a calendar, change who a calendar is shared with, or alter your Google Calendar settings. Neither gives us any access to the rest of your Google account: not Gmail, not Contacts, not Drive. We request no Google scope beyond the two named above.

One limit is ours rather than Google’s, so it is worth stating plainly: the events scope is not confined to the calendars you picked, but Avenday confines itself to them. We do not read or write events on a calendar you left unticked, and unticking one stops Avenday touching it.

Google Calendar: how the connection is stored. Connecting returns an OAuth access token and a refresh token from Google. The refresh token is what keeps the connection alive without asking you to sign in again. We store the refresh token encrypted at rest, and decrypt it only when Avenday makes a calendar request on your behalf. It is never shown in the app, never written to our logs, and never sent to any third party, including our AI provider.

You can disconnect Google Calendar at any time from within Avenday. Doing so deletes the stored access and refresh tokens and stops all further access. You can also revoke Avenday’s access directly from your Google Account at myaccount.google.com/permissions. What then happens to the events Avenday had already read is set out under How long we keep it.

Information collected automatically

Device and app data: device model, operating system version, app version, language, and time zone.
Diagnostics: crash reports and error logs, used to fix defects.
Basic usage: which screens are opened and which features are used, in aggregate, so we can tell what is working.

This website is a static marketing site. It sets no advertising or tracking cookies. The only information it collects is an email address, and only if you type one into the early-access form.

How we use it

To operate the app: to show your plans, keep your lists in sync, and share them across your family.
To write your daily briefing, which requires reading your upcoming events, open tasks and recorded facts together.
To answer what you ask Avenday AI and to carry out the actions you confirm.
To keep the service secure, prevent abuse, and diagnose failures.
To reply when you contact us.
To comply with the law.

AI processing

Avenday uses large language models to write briefings and to answer what you ask. The model provider is Anthropic, PBC, which operates the Claude models Avenday runs on and processes what we send it on our behalf, under contract, as our processor.

Your calendar event text is sent to Anthropic. When Avenday writes your briefing, answers a question about your week, or drafts an event for you to confirm, the text of the events relevant to that request (their titles, times, locations, attendees and descriptions, including events read from Google Calendar) is sent to Anthropic as part of the request. The same is true of the tasks, list items, recorded facts and messages needed for that request, and of the text of an email forwarded to your family’s Avenday address when Avenday reads it. We send only what that specific request needs, and we send no OAuth tokens or account credentials.

Anthropic may use what we send only to return a result to us. Under our agreement it is not permitted to use it to train its models, and it retains it only for the limited period its terms allow for serving the request and meeting its own safety obligations. We do not use your family’s content to train models of our own.

Avenday’s output can be wrong. It is an assistant, not a source of truth, and it is not advice of any professional kind. Confirm anything that matters.

Who else sees it

We share information only in these situations:

Your family. Plans, lists, tasks and recorded facts are visible to the people you have added to your household. That is the point of the app. A list or a task you mark as private is the exception: it is visible only to you.
Service providers. Companies that host our infrastructure, deliver our email, report our crashes, and provide the AI models described above, which is Anthropic, as set out in AI processing. When you look up a place, the words you type are sent to Google Maps Platform to find it; to show how long the drive is, the location of your family’s home and of that place are sent to Google Maps Platform too. PostHog receives usage events from the app (which screens are opened and which features are used) so we can tell what is working. Our early-access list is held by Loops, which stores the address you submit and sends the messages you have asked for. They act on our instructions and may not use your information for their own purposes.
Legal requirements. When we are compelled by valid legal process, or where disclosure is necessary to protect someone’s safety or our rights.
A change of ownership. If Avenday is acquired or merged, information may transfer as part of that transaction. This policy would continue to govern it until you are told otherwise.

We do not sell personal information, and we do not share it for cross-context behavioral advertising.

Google user data

Avenday’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

We use the Google Calendar data we read only to provide and improve the user-facing features described in this policy: showing your week, writing your briefing, and creating or changing the events you confirm.
We do not transfer it to others except as necessary to provide those features (our hosting provider, and the AI processing described above), to comply with applicable law, or as part of a merger or acquisition as described above.
We do not use it for advertising of any kind, and we do not sell it.
We do not use it to develop, improve or train generalized AI or machine-learning models. It is sent to Anthropic solely to produce a result for you, and Anthropic is contractually barred from training on it.
No human at Avenday reads your Google Calendar data, except where you give us explicit consent for a specific issue (for instance, support you have asked us for), where it is necessary for security purposes such as investigating abuse, where the law requires it, or where the data is aggregated and de-identified.

The specifics live in the sections above, and this is where each one is: what we access and what we use it for under Calendars you connect; who we share it with under AI processing and Who else sees it; how we protect it under Security; and how long we keep it and how it is deleted under How long we keep it.

Children

Avenday is designed for parents and guardians to run a household, and it necessarily holds information about children: their names, their schedules, their allergies and routines. That information is entered by an adult account holder, not by the child.

Avenday accounts are for adults. We do not knowingly create accounts for, or collect information directly from, children under 13. If you believe a child has created an account, write to support@avenday.app and we will remove it.

How long we keep it

We keep your content for as long as your account is active. When you delete a fact, a list item or an event, it is removed from the app immediately and purged from backups on our normal backup cycle. When you delete your account, we delete your content within 30 days, except where we are required to retain records for legal or accounting reasons.

Google Calendar data specifically. While a Google calendar is connected, Avenday keeps a copy of the events it has read so the app works when your phone is offline. When you disconnect that calendar, or revoke Avenday from your Google Account, we delete the stored access and refresh tokens immediately and delete our copy of that calendar’s events within 30 days. Deleting your Avenday account deletes both on the same 30-day schedule. Events that Avenday itself created in your Google Calendar stay in your Google Calendar. They are yours, and deleting Avenday does not reach into your Google account to remove them.

Your choices and rights

See it. Every durable fact Avenday holds is listed on the What Avenday knows screen.
Correct it. Edit any fact in place; Avenday acts on the corrected version from then on.
Delete it. Forget individual facts, or delete your whole account from the app.
Export it. Ask us for a copy of your data and we will send it.
Object or restrict. Where the law gives you these rights, you may exercise them.

Depending on where you live (the EU and UK under the GDPR, California under the CCPA/CPRA, and a growing list of US states) you may have additional rights, including the right not to be discriminated against for exercising them. Write to support@avenday.app and we will honor any request the law entitles you to.

Security

Your data is encrypted in transit and at rest. Access by our staff is limited to what is needed to operate and support the service, and is logged. That applies to everything we hold from Google: the calendar list and the event data we read travel over TLS and are encrypted at rest, and the OAuth refresh token is encrypted on top of that, as described under Calendars you connect. No system is perfect; if we discover a breach that affects you, we will tell you as promptly as the law requires and as promptly as we can.

Where your data is processed

Avenday is operated from the United States, and your information is processed there. If you use Avenday from outside the US, you understand your information will be transferred to and processed in the US, and we rely on appropriate safeguards for those transfers where required.

Changes

We will update this page when our practices change, and we will change the date at the top. If a change materially affects how we handle your information, we will tell you in the app or by email before it takes effect.

Contact

Questions, requests, or anything that looks wrong: support@avenday.app.