Privacy

Privacy Policy

Effective 27 August 2026.

Holico is a private system built and run by one person, Hank Holiday, trading as Holiday Ventures, in San Francisco, California. This policy covers two separate things: this website, and the Holico application. They handle data very differently, so they are described separately below.

1. What this website collects

Nothing. holico.app is three static pages. There are no accounts, no sign-ups, and no forms, so there is no way to submit information through the site and nothing to store. No cookies are set. Nothing you do here is recorded or associated with you.

The pages load web fonts from Google's font service. That is a request to a Google server, and it shows Google the IP address and browser making it, in the same way any request to any server does. Google's font service sets no cookies. No other third-party resource is loaded: no trackers, no embedded content, no scripts from anyone else.

There is no analytics on this site today — nothing counts visits, records sessions, or builds a profile of anyone. If analytics is added later, this page is updated before it goes live, and the update will name the provider and say plainly whether it sets cookies. Nothing that identifies a person across other websites will be used here.

The company hosting these pages keeps its own standard server logs, which typically record an IP address, a timestamp, and the page requested. Those logs are the host's, generated by the act of serving a page. They are not read, analyzed, exported, or used for any purpose.

2. The application is a different thing

Everything below this line describes the Holico application, not the website. The two share a name and a domain and nothing else.

Holico is a personal assistant system that runs on the operator's own Google Cloud project and works with the operator's own files, calendar, and messages. It has exactly one user, who is also the person who built it and the person whose data it handles. There are no other users. There are no accounts to create. Nobody else can sign in, and there is no mechanism by which anyone else's data would enter the system, except where another person appears inside the operator's own messages, files, mail, or calendar.

3. Which Google APIs the application uses, and why

Holico calls the Google Drive API. It requests the scope https://www.googleapis.com/auth/drive. It uses this to read, create, and update files inside a single folder called Holico/ in the operator's Google Drive, and to poll for changes to those files roughly once a minute. The full Drive scope is requested rather than a narrower one for a specific reason: the narrower drive.file scope only shows an application the files that application created, and Holico must also see files the operator adds to the folder by hand. Holico's own code confines its reads and writes to the Holico/ folder.

Holico calls the Google Calendar API. It requests https://www.googleapis.com/auth/calendar.readonly and https://www.googleapis.com/auth/calendar.events. It reads events and free/busy times from the operator's primary calendar to understand the shape of the week, and it keeps that read in a fifteen-minute cache. It writes calendar events only after the operator has explicitly approved that specific write. The code enforces this: the function that writes to the calendar refuses to run without an approved record attached to it.

Holico will call the Gmail API when email handling is added to the system. It will request https://www.googleapis.com/auth/gmail.readonly and https://www.googleapis.com/auth/gmail.compose, across two of the operator's own mailboxes. The read scope is used to sort incoming mail by how much it matters and to surface the few messages that need attention. The compose scope is used to write draft replies, which sit as drafts until the operator reads one and confirms it. Nothing is sent without that confirmation, and the confirmation is a deliberate typed act, not a tap. Holico does not delete mail and does not empty anyone's trash.

Holico requests no other Google scopes. It does not request Contacts, Photos, Tasks, Chat, or anything else.

4. What the application does with data

Holico turns the operator's own notes, projects, tasks, calendar, mail, and messages into a working record: project files, task files, summaries, weekly briefs, and a list of decisions waiting for the operator to make. Content is sent to a language model to be summarized, classified, scored, or shaped into one of those outputs, and the result is written back into the operator's files.

Chat message content reaching the application comes from the operator's own messaging accounts through a program running on the operator's laptop, not from any Google API. That program is read-only against those accounts, apart from marking a message as read.

Holico is not a product. It is not sold, licensed, offered to anyone else, or run on anyone else's behalf. It produces nothing for anyone but the operator.

5. Where data is stored

Files live in the operator's own Google Drive. Structured records live in Google Cloud Firestore. Audio, generated speech, and backups live in Google Cloud Storage. All of the Google Cloud resources sit in a single Google Cloud project controlled by the operator, in United States regions. Credentials live in Google Secret Manager and appear in no file, log, or backup.

Backups run nightly to Google Cloud Storage and are kept for 30 daily and 12 monthly copies.

6. How long data is kept

Retention is enforced by expiry timestamps written when a record is created, not by a manual cleanup.

Message and email text from close and regular contacts is kept 90 days. Anything escalated to the operator's attention is kept 90 days regardless of who sent it. Other message and email text is deleted at the point it is scored, within minutes of arriving; a stub record with no content is kept 30 days so the same message is not processed twice. Short one-line summaries persist as part of the operator's working record.

Mail itself is not copied into a second archive. It stays in the mailbox it arrived in, under Google's own retention, and Holico keeps only what this section describes.

Raw inbound audio is kept 90 days. Synthesized speech is kept 14 days. System events and job runs are kept 90 days, with weekly aggregate counts kept beyond that.

Files in Google Drive — projects, tasks, notes, knowledge — are the operator's own working documents and are kept until the operator deletes them.

7. Who can access the data

One person: the operator. Nobody else has credentials, and there is no support team, no contractor, and no shared account. Firestore denies all direct client access; only the operator's own cloud services can reach it. Each component of the system runs with the minimum permissions it needs.

Because the operator is also the only person whose data this is, a human reading this data means the operator reading his own files and his own mail.

8. Google API Services User Data Policy — Limited Use

Holico's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically: data obtained from Google APIs is not sold to anyone. It is not transferred to third parties except to the service providers named in section 9, and only as needed to operate the application for its single user. It is not used for advertising of any kind, including retargeting, personalized advertising, or interest-based advertising. It is not used to train, fine-tune, or improve generalized or non-personalized artificial intelligence or machine learning models. It is not read by any human other than the operator, whose own data it is.

9. Service providers

Holico is built on other companies' services. Data passes through the following, and no others.

Google — Google Drive, Gmail, Google Calendar, Firestore, Cloud Run, Cloud Storage, Cloud Speech-to-Text, and Cloud Text-to-Speech. Google both supplies the data through its APIs and hosts the system that processes it.

Anthropic — the language models that summarize, classify, and shape content are called through the Anthropic API. Content sent to a model may include the operator's own file, mail, and message content. The operator has configured the account so that Anthropic's retention of that content is minimized, and Anthropic does not use data submitted through its API to train its models. Anthropic is the only model provider Holico uses.

Signal — the operator talks to Holico over Signal, using a phone number that belongs to the system rather than to the operator. Signal messages are end-to-end encrypted.

Beeper — a messaging client running on the operator's own laptop, which is where chat message content enters the system. No Google data is sent to it.

Superlist — a task application the operator uses. Holico reads tasks from it. No Google data is sent to it.

None of these providers receives Google user data for their own purposes, and none is permitted to use it beyond providing their service.

10. Deleting data and revoking access

The operator can revoke Holico's access to his Google account at any time from the Google account permissions page at myaccount.google.com/permissions. Revoking access invalidates the stored token immediately and stops all further API calls.

Stored data is deleted by deleting the underlying resources: the Firestore database, the Cloud Storage buckets and their backups, and the Holico/ folder in Google Drive. Since the operator owns the Google Cloud project and the Drive folder, this is a direct action he takes himself, not a request he files.

If you believe Holico holds data about you — most likely because you have written to the operator or exchanged messages with him — write to the address in section 12 and ask for it to be deleted. The operator will delete it.

11. Changes to this policy

If this policy changes, the new version is published at this URL and the effective date at the top changes with it. Because the system has one user, who is the same person who writes this policy, there is nobody to notify separately. Anyone who wants to see whether it has changed can check the date at the top of this page.

12. Contact

Hank Holiday, Holiday Ventures, San Francisco, California. Email: ryan.hank@gmail.com.