1. Scope and status
Astra Home is a personal, locally operated engineering project owned and used by Finley Greenfield. Astra V0 is not currently offered as a public or commercial service. This website provides information about the project and its Google Calendar integration; it does not provide an Astra account, Calendar connection or assistant service.
2. Google user data Astra accesses
After the Google account holder gives consent, Astra’s desktop application can access Google Calendar data using the Google Calendar API.
Data accessed
- Calendar-list metadata, including calendar identifiers, names, access roles, time zones, colour metadata and whether a calendar is primary.
- For the two calendars selected locally for Astra: event identifiers, titles, status, start and end information, and whether an end time is unspecified.
- Free/Busy information for the selected calendars, used to calculate intervals that are not marked busy.
Purpose
Astra uses this information to answer the owner’s requests about upcoming events and calendar-free time, such as “What am I doing tomorrow?” or “When am I next free this week?” Calendar titles and event contents are treated as data, not as instructions to control devices.
Permissions and Calendar changes
The current Google authorization requests Calendar event access, Free/Busy access and read-only calendar-list access. The Calendar event permission can permit creating, updating and deleting events. Separate development utilities previously used this permission to create, move, verify and delete specifically marked temporary test events. Those utilities keep a restricted local test journal so uncertain writes are not repeated.
The current Astra V0 conversational assistant exposes Calendar reading and availability queries. It does not currently expose creating, changing or deleting Calendar events through conversation.
3. Local storage and retention
- Google access and refresh tokens are stored in the owner’s macOS Keychain.
- The Google OAuth desktop client configuration is stored in a restricted local credentials file.
- Calendar discovery and selection files store Calendar identifiers and setup metadata locally with restricted file permissions. They do not contain OAuth tokens.
- Calendar query results and conversation context are held in memory for the current bounded session. Astra does not intentionally write normal conversation transcripts or ordinary Calendar query results to a conversation database.
- Development write-test journals can store the identifier and planned details of Astra’s marked temporary test events.
Information shown in a terminal may remain in terminal scrollback, and information spoken aloud is audible in the room. Operating-system backups or user-created copies may also retain local files outside Astra’s direct control.
4. AI and speech processing
Default local mode
Astra’s default conversational model runs through Ollama on the owner’s Mac, bound to the local loopback interface with cloud features disabled. Calendar results needed for an answer are provided to that local model during the conversation. Speech recognition uses a local Whisper model. Astra does not automatically fall back to a cloud AI provider.
Optional OpenAI mode
If the owner explicitly selects the optional OpenAI provider, conversation messages, tool results requested during that conversation—including relevant Calendar results—and microphone recordings submitted for transcription are sent to OpenAI. Astra asks the OpenAI Responses API not to store the response by setting store to false, but OpenAI’s own terms and privacy practices govern its processing. The OpenAI API key is kept in a restricted local configuration file.
5. Diagnostic logs
Astra writes bounded, rotating diagnostic logs on the owner’s Mac. They record operational metadata such as timestamps, component and action categories, latency, verification status, success state and recognised error codes.
The application logger is designed not to record raw conversation text, event titles or times, OAuth tokens, API keys, full device responses or complete tool payloads. Log files and their directories use owner-only permissions.
7. This website
This is a static informational website. It does not include an account system, contact form, advertising, analytics scripts or deliberately set tracking cookies. The site host may process ordinary request information—such as IP address, browser details, requested page and timestamps—to deliver and secure the website under its own terms and privacy practices.
If you contact Finley by email, the email provider processes and retains your message according to the settings and policies of the relevant email services.
8. Control, revocation and deletion
The Google account holder can revoke Astra’s Google access from their Google Account permissions at any time. They can also stop using Astra, delete its local Calendar selection and test-journal files, remove its local credentials and ask the project owner about the local data described in this policy.
Revoking access prevents future API access, but does not itself delete local configuration files or information retained by Google, OpenAI, the website host, email providers or operating-system backups under their respective controls.
9. Changes to this policy
This policy will be updated when Astra’s data access, AI providers, storage or public availability materially changes. The effective date at the top identifies the current version.
10. Contact
For questions about Astra or its use of Google user data, contact:
Finley Greenfield
fin.greenfield1@icloud.com