Privacy Policy — Hughesboro
Last updated: August 31, 2026
Hughesboro is a private family organization tool built and operated by Terry Hughes ("I," "we"). It is used by a single household to coordinate calendars, lists, contacts, files, and shared logistics. This policy describes what information Hughesboro collects, how it is used, and how it is protected — including information obtained through Google APIs.
If you have questions about this policy, contact terry@hughesboro.com.
1. Who this applies to
Hughesboro is not a public product. Accounts are created only for members of the operating household. This policy describes our practices for those users.
2. Information we collect
Account information. When an account is created, we store an email address and authentication credentials managed by our authentication provider (Supabase). We do not store passwords in readable form.
Information you enter. Lists, tasks, deadlines, events, contacts, and related notes that you create in Hughesboro are stored in our database so the application can display them to you and to the household members you share them with.
Files you add to Hughesboro. You may attach files to events, list items, and other things in Hughesboro. These are stored by us, in our own storage, and are not sent to Google. They are visible only to the people who can already see the thing you attached them to.
Google account information, if you connect your Google account. Connecting is optional and initiated by you. If you connect, we receive and store:
- A Google refresh token — a credential that lets Hughesboro access your Google data on your behalf. It is encrypted before storage and can be revoked by you at any time (see §7).
- Your basic profile — your Google account email address, name, and profile picture, used to identify you inside Hughesboro and to label which account a connection belongs to.
- Your calendar list — the names, identifiers, colors, and your access level for the calendars in your Google account. We use this to determine which calendars to display and what you are permitted to do with them.
- Event data from calendars you or your household have connected — titles, descriptions, locations, times and time zones, recurrence information, organizer and creator addresses, guest email addresses and their RSVP responses, attachments, and each event's visibility setting. We receive each event exactly as Google presents it to your account, and no more.
- Your Google contacts — names, email addresses, phone numbers, birthdays, organizations, and photos from the contacts in your own Google account.
- Specific Google Drive files you choose. When you attach a Drive file to an event, we access that file's name, type, and link. We cannot see any other file in your Drive — see §4.
Technical information. Our hosting providers generate ordinary server logs (timestamps, request paths, error conditions). We keep a limited operational log of synchronization outcomes — what synced and whether it succeeded — which records identifiers and counts, never event contents, contact details, file contents, or credentials.
3. How we use information
We use this information solely to operate Hughesboro for its users:
- To display your calendars, events, contacts, lists, tasks, and files
- To keep Hughesboro's copy of your Google Calendar events current, in both directions, when you choose to make changes in Hughesboro
- To keep Hughesboro's copy of your Google contacts current, in both directions, when you choose to make changes in Hughesboro
- To show birthdays from your contacts on your calendar
- To attach a Google Drive file you have chosen to an event, and to show that attachment afterwards
- To store and show files you add to Hughesboro itself
- To send calendar invitations through Google when you add a guest to an event
- To enforce who may see and edit what, according to the permissions Google and Hughesboro record
- To diagnose and fix problems with synchronization
We do not use your information for advertising, profiling, or marketing. We do not sell, rent, or trade it. We do not transfer it to third parties except the infrastructure providers listed in §5, who process it only to provide their services to us.
4. Google API Services — Limited Use disclosure
Hughesboro's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically:
- We use Google data only to provide and improve the calendar, contacts, and attachment features visible to the user who authorized access and to the household members they have shared calendars with in Google.
- We do not transfer Google user data to others except as necessary to provide and improve these features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with user notice and consent.
- We do not use Google user data for serving advertisements.
- We do not allow humans to read Google user data unless we have the user's affirmative agreement for specific messages, it is necessary for security purposes such as investigating abuse, to comply with applicable law, or where the data is aggregated and anonymized for internal operations.
What we ask for, and why each is the narrowest permission that works:
| Permission | Why |
|---|---|
| Google Calendar | Hughesboro reads and writes events, and reads and updates which calendars you are subscribed to and how they appear. This is the smallest single permission Google offers that covers all of it — asking for narrower ones in combination would grant the same access across more separate permissions. |
| Google Contacts | Contacts sync is two-way: a change you make in Hughesboro is written back to Google. That requires write access. Read-only would make Hughesboro's contacts a dead-end copy that silently diverges from yours. |
| Specific Drive files | This grants access only to the individual files you pick through Google's own file chooser, and to files Hughesboro creates. It does not grant access to your Drive as a whole. We deliberately do not ask for the broader Drive permissions, which would let this application read every file you own. |
| Basic profile and email | To identify you when you sign in and to label which Google account a connection belongs to. |
5. Where information is stored and who processes it
Hughesboro runs on third-party infrastructure. Each provider processes data only to deliver its service to us:
| Provider | Role |
|---|---|
| Supabase | Database, authentication, file storage |
| Railway | Application server for synchronization and Google API access |
| Vercel | Web application hosting |
| Calendar, Contacts, and Drive data source, when you connect your account |
6. How information is protected
- Encryption in transit. All connections use HTTPS/TLS.
- Encrypted credentials. Google refresh tokens are encrypted with AES-256-GCM before being written to the database. The encryption key is held only in the application server's environment and never stored alongside the data.
- Enforced access control. Access rules are enforced in the database itself, not only in the application, so a user cannot retrieve data they are not permitted to see even by bypassing the interface.
- We do not receive private event details you are not entitled to see. Each household member connects their own Google account, and Hughesboro stores a separate copy of each calendar for each person, containing exactly what Google sends to that person. When someone marks an event Private in Google, Google withholds its title, description, location and guest list from anyone not permitted to see them — so those details never reach Hughesboro at all. Hughesboro shows the time as busy and says plainly that the details are held back by Google. This is stronger than hiding the information in the interface: we are not holding it.
- Your contacts are yours alone. Contacts mirrored from your Google account are visible only to you. They are not shared with other household members and are not merged into a common address book. This is enforced in the database, in the same way as private event details.
- Files you add to Hughesboro inherit their permissions. A file attached to something in Hughesboro is visible to exactly the people who can already see that thing, and to nobody else. Files carry no separate sharing of their own, so there is no way for a file's access to drift apart from the access to what it belongs to.
7. Your choices and how to revoke access
- Disconnect inside Hughesboro. Disconnecting Google deletes the stored credential and asks Google to revoke Hughesboro's access. Calendar and contact data mirrored from your account is marked for deletion immediately and stops being shown; see §8 for how long it remains recoverable before it is permanently removed.
- Revoke at Google. You may revoke Hughesboro's access at any time at myaccount.google.com/permissions. Access ends immediately.
- Delete your data. Contact terry@hughesboro.com to request deletion of your account and associated data, or immediate permanent removal of mirrored data without waiting for the recovery window in §8.
One thing disconnecting cannot undo. If you attach a Google Drive file to an event and give a guest access to it, that access is granted in Google Drive and belongs to Drive, not to Hughesboro. It is permanent until you change it yourself. Deleting the event, removing the guest, disconnecting Google, and deleting your Hughesboro account will none of them take it back. Hughesboro says so at the moment you grant it, and shows you where to change it. You can review and remove file access at any time in Google Drive.
8. Data retention
Calendar and contact data mirrored from Google is retained while the connection is active. When you disconnect, or when a calendar is removed, that data is marked deleted and stops being shown immediately.
Deleted items remain recoverable before being permanently removed: 30 days for information you created in Hughesboro, and 35 days for data mirrored from Google. The longer window for mirrored data exists so that an item you restore in Google is not permanently discarded here first. Operational synchronization logs are retained for 30 days.
Files you add to Hughesboro are kept while the thing they are attached to exists, and are removed with it on the same 30-day recovery window. We do not keep copies of Google Drive files — a Drive attachment is a link to a file that stays in Drive, and removing the attachment does not delete the file.
9. Children
Hughesboro is used within a single household and includes accounts for the operators' minor children, created and administered by their parents. Where a child connects a Google account, their calendar and contact data is mirrored in the same way and under the same protections described above — including that their contacts are visible only to them and not to other household members. We do not offer the service to the public and do not knowingly collect information from children outside this household.
10. Changes to this policy
If we change this policy we will update the date above. For material changes — including any change to what Google data we access — Hughesboro shows a notice inside the application to every user, which stays visible until dismissed.
11. Contact
Terry Hughes — terry@hughesboro.com
Hughesboro is operated by an individual, not a company.