Seersucker Ventures LLC
Privacy policy
Last updated: September 29, 2026
Seersucker Caller is an internal, owner-operated business application. This policy explains how the app handles information used for CRM synchronization, calling, authorized email workflows, and meeting coordination.
1. Who operates the app
Seersucker Ventures LLC operates Seersucker Caller. It is not a public sign-up service. For privacy questions or deletion requests, contact thad@thadallenwebsites.com.
2. Google information the app accesses
Google Sheets. The app uses Google Sheets read and write permission to synchronize one designated CRM workbook. CRM records can include business contact details, customer and interaction history, notes, and follow-up rules. Although the granted Sheets permission is broader, the app's configuration pins its CRM work to that workbook.
Google Calendar. The app requests permission to manage events on calendars the owner owns, read free/busy information, and read calendar identity and metadata. These permissions correspond to calendar.events.owned, calendar.freebusy, and calendar.calendars.readonly.
Availability checks use busy time ranges and calendar identity or metadata. The meeting workflow creates and manages its own meeting records and may access the details of events it creates. The app does not provide callers with a general feed of private calendar event details.
Authorization information. The app stores OAuth tokens so it can use the Google permissions granted by the owner without asking for sign-in on every operation.
3. How information is used
The app uses Google information to keep CRM records and customer history synchronized, apply follow-up rules, provide relevant context for the owner's calling and authorized email workflows, check meeting availability, and create or manage its meeting records.
This app does not sell Google user data, use it for advertising, or perform general-purpose AI model training with it. Its use of Google data is limited to the operations described in this policy.
4. Where information is stored
The CRM remains in Google Sheets. Local copies of selected data, operational records, and OAuth tokens are stored in private files or local SQLite databases on the owner's Mac.
The app also uses the service providers described below. Information sent to a provider is processed outside the owner's Mac and may be retained under that provider's applicable terms and privacy practices.
5. Service providers and sharing
- Google provides the connected Sheets and Calendar services.
- Retell and its configured voice, model, and telephone service providers process selected CRM contact and interaction context as needed to support the calling workflow.
- OpenAI/Codex receives selected CRM context for the authorized email workflow.
- No2Bounce receives the exact business email addresses submitted for hosted mailbox checks. A mailbox-check result is not a guarantee of delivery.
- Cloudflare hosts this static website and may process request and network information, such as IP addresses, to deliver and protect it.
This website has no analytics, forms, or advertising trackers. The app's statement about its own model-training use does not make a guarantee about every provider's retention or training practices.
6. Retention and deletion
Locally captured call text has a 30-day retention period. CRM records and other operational records do not have one universal automatic deletion deadline. Provider-held copies may have different retention rules.
Contact thad@thadallenwebsites.com to request deletion of information held by Seersucker Ventures LLC. The operator will review the request and identify any applicable recordkeeping requirements or limits on deleting provider-held information.
7. Control over Google access
The owner can revoke Seersucker Caller's Google access through the third-party connections settings in their Google Account. Revocation stops future access through that authorization. It does not, by itself, erase information already saved in local records, the CRM, or provider systems. Deletion requests can be made using the contact address above.
8. Changes to this policy
The operator may update this policy when the app's data practices change. The current version and its last updated date will be published on this page.