Privacy Policy
Effective October 31, 2026 · Version 1.2 (Pre-launch)
1. Who we are
This Privacy Policy describes how Agnostic Studios LLC, a Florida limited liability company, doing business as GreeterHub (“GreeterHub,” “we,” “us,” or “our”), collects, uses, and shares information when you interact with our website at greeterhub.com (the “Site”), call our public demo line at +1 (855) 799‑6531 (the “Demo Line”), place a founding member deposit reservation, or connect Google Calendar to the GreeterHub app (section 5). Together with our Terms of Service, this Privacy Policy is the agreement that governs your use of these services.
2. Information we collect
2.1 Information you give us directly
We collect information you provide when you:
- Place a founding deposit reservation. Your email address, optional name, the amount you indicated at signup, and payment confirmation data from Stripe (such as the last four digits of your card and the Stripe charge ID). We never receive or store your full card number, security code, or expiration date.
- Contact us. The contents of any email you send us and any contact details you include.
- Use the missed-call calculator. The business figures you enter (call volumes, average ticket, missed-call rate, how calls are answered today) and the computed results, which we store to generate your results and improve the tool. If you request the emailed report, we also store the email address you provide.
- Call the Demo Line. The audio of your call, an AI-generated transcript of the call, and any personal information you choose to share during the call. Your caller-ID telephone number and call metadata (timestamp, duration, hold and transfer events) are also captured by our telephony provider.
2.2 Information collected automatically
When you visit the Site, we and our service providers may automatically collect:
- IP address, approximate location derived from IP address, browser type and version, operating system, and device type;
- Pages viewed, time spent on pages, referring URLs, and similar usage information; and
- Information from cookies and similar technologies (see §7 below).
2.3 Information from third parties
We receive limited information from third parties who help us operate the Site and the deposit pipeline: for example, payment confirmation events from Stripe and email delivery events (sent, delivered, bounced) from Resend. If a business connects Google Calendar, we also receive the Google Calendar data described in section 5. We do not buy email lists or contact information from data brokers.
3. How we use information
We use the information we collect to:
- Process founding deposit reservations, manage the 72-hour claim window, and send reservation confirmations and launch updates;
- Operate the Demo Line and respond to your call;
- Operate, maintain, secure, and improve the Site and the Demo Line, including investigating bugs, abuse, and fraud;
- Respond to inquiries you send us, and follow up on customer interest;
- Send transactional messages related to your reservation (such as payment receipts, refund notices, and the 72-hour launch email);
- With your permission or as permitted by law, send occasional marketing emails about GreeterHub product updates (you can unsubscribe at any time using the link in those emails);
- Comply with our legal obligations, enforce our Terms, and protect our and others' rights, property, and safety; and
- Aggregate or de-identify information for analytics, research, and product improvement.
4. Demo Line calls
The Demo Line is operated directly by GreeterHub for demonstration and product-improvement purposes. When you call:
- You will hear an AI voice agent (not a live person) at the start of the call.
- The call is recorded. The recording disclosure is played in the greeting. If you do not consent to the recording, please hang up before the agent asks for any information.
- The audio of your call and an AI-generated transcript are processed by our voice runtime providers (currently Retell AI, Twilio, Anthropic, Cartesia, and ElevenLabs) to understand your speech, generate a response, and play that response back.
- GreeterHub does not use your voice to create a voiceprint, enroll you in any voice-recognition system, or attempt to identify or authenticate you across calls. Audio is processed solely to understand the content of the call and generate a response. Our voice runtime providers are not authorized to use your voice for speaker recognition or voice biometric processing on our behalf.
- Please do not share confidential or regulated personal information on the Demo Line (such as financial account numbers, social security numbers, medical information, or government identifiers). The Demo Line is not designed to handle that information.
5. Google Calendar data
A business that uses the GreeterHub app can connect its Google Calendar, so that its AI receptionist books around the business’s existing appointments and adds each new booking to that calendar. This section applies only to a business that connects Google Calendar, and it describes everything GreeterHub does with the data it receives from Google.
5.1 What we access, and why
When you connect Google Calendar, Google asks you to grant GreeterHub access to your availability (which Google lists as “View your availability in your calendars”), to events on calendars you own (“See, create, change, and delete events on Google calendars you own”), and to your Google Account’s email address. We use them only as follows:
- Busy times. When your receptionist checks for open arrival windows, GreeterHub asks Google for the busy times on the calendar you connected, for up to the next 14 days. Google returns only the start and end of each busy period, without event titles, descriptions, locations, or guests. We use these busy times for one purpose: so that your receptionist does not offer a caller a window your calendar shows as busy.
- Events for the bookings GreeterHub makes. When your receptionist books an appointment, GreeterHub adds an event for it to the calendar you connected, with the service, the customer’s name, the job description and access notes the caller gave, the address, and the arrival window. We keep the ID Google assigns to that event with the booking. Apart from adding these events, and removing one when you cancel its booking in GreeterHub, GreeterHub does not create, read, change, or delete events on your calendar.
- Your Google account’s email address, which the Integrations screen shows so you can see which account is connected.
- Access tokens. Google gives GreeterHub tokens that let it make the requests above on your behalf. Without them, GreeterHub cannot reach your calendar.
5.2 How we use it
We use Google Calendar data only to provide the booking features in section 5.1, which you can see in the GreeterHub app. In particular:
- We do not sell Google Calendar data, and we do not use or transfer it for advertising, for credit or lending decisions, or to build, train, or improve any AI or machine learning model.
- Our staff do not read it, unless you ask us to (for example, to help with a connection problem), it is necessary for security (such as investigating a bug or abuse), or the law requires it.
- GreeterHub’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and to the Google Workspace user data and developer policy.
5.3 Who receives it
- Busy times stay on GreeterHub’s servers. During a call, our servers turn them into the open arrival windows your receptionist may offer, and only those open windows (dates and times) go to our voice runtime providers (section 6.1), so that the receptionist can offer them to the caller.
- The booking details in an event GreeterHub adds go to Google, into the calendar you connected, where Google holds them under your own agreement with Google.
- We store Google Calendar data with our database provider, Supabase, and process it on our hosting provider, Vercel, both bound as section 6.1 describes.
- Otherwise, we disclose it only for the legal and safety reasons in section 6.2, and in a merger, acquisition, or sale of GreeterHub only after asking for your consent first.
5.4 How we store it, and how long we keep it
- Access tokens are stored in a database table that only GreeterHub’s servers can read. No one signed in to the GreeterHub app can read them, your own team included. Our database is encrypted at rest (section 11). We keep the tokens while Google Calendar is connected.
- Busy times are kept only in a short-term cache. A cached copy is used for at most 60 seconds before GreeterHub asks Google again, and each new answer replaces the one before it.
- Your account’s email address and the event IDs are kept while Google Calendar is connected.
- All of it is deleted when you disconnect (section 5.5).
5.5 Disconnecting, and deleting your data
- You can disconnect Google Calendar at any time in the GreeterHub app, under Settings, then Integrations. When you do, GreeterHub asks Google to revoke its access and deletes your access tokens, the cached busy times, the connected account’s email address, and the stored event IDs.
- You can also remove GreeterHub’s access on your Google Account’s linked apps page. GreeterHub then can no longer reach your calendar, and the next time it tries, it deletes the same data and shows the connection as needing to be reconnected.
- If you cancel your GreeterHub plan, we disconnect Google Calendar the same way.
- Events GreeterHub added to your calendar are yours. They stay on your Google Calendar after you disconnect, and you can edit or delete them there.
- To ask us to delete Google Calendar data at any time, email privacy@greeterhub.com.
6. How we share information
We do not sell your personal information for money. We do not share your personal information for cross-context behavioral advertising. We share information only as described below:
6.1 Service providers
We use the following categories of service providers to operate the pre-launch Services. Each is contractually bound to use your information only to provide services to GreeterHub and to maintain reasonable confidentiality and security safeguards:
- Payments: Stripe (PCI-DSS-compliant payment processing for the $5 founding deposit). GreeterHub never stores your full payment card number.
- Telephony: Twilio (Demo Line phone number, call routing, call metadata).
- Voice runtime: Retell AI (Demo Line orchestration and speech-to-text + text-to-speech routing), Anthropic (the AI language model that powers the Demo Line agent), Cartesia and ElevenLabs (text-to-speech voice generation), all accessed via our Retell-managed contracts.
- Email delivery: Resend (reservation confirmations, launch updates, and transactional messages), ImprovMX (email forwarding for general inquiries).
- Database and hosting: Supabase (reservation records, and the Google Calendar data in section 5), Vercel (Site hosting and edge runtime), Upstash Redis (short-lived Demo Line transcript cache, retained no more than 7 days).
- Domain and DNS: our domain registrar and DNS providers.
If a business connects Google Calendar, GreeterHub also exchanges data with Google at that business’s direction, as section 5 describes.
6.2 Legal and safety disclosures
We may disclose information if we believe in good faith that disclosure is necessary to (a) comply with a subpoena, court order, or other legal process; (b) enforce our Terms or this Privacy Policy; (c) protect the rights, property, or safety of GreeterHub, our customers, or the public; or (d) detect, investigate, or prevent fraud, abuse, or security incidents.
6.3 Business transitions
If GreeterHub is involved in a merger, acquisition, financing, or sale of all or part of its business or assets, your information may be transferred to the successor entity, subject to a privacy policy at least as protective as this one. Google Calendar data is transferred in such a transaction only with your prior consent (section 5.3).
6.4 De-identified and aggregated data
We may use and share de-identified or aggregated information (which cannot reasonably be used to identify you) for any lawful business purpose, including service improvement and product research.
7. Cookies and similar technologies
The Site uses a small number of cookies and similar technologies to remember your preferences, keep the Site functioning, and measure aggregated usage. Most browsers let you control cookies through their settings. We honor the Global Privacy Control (GPC) signal where applicable as a request to opt out of any cross-context behavioral advertising sharing, although we do not currently engage in such sharing.
8. How long we keep information
We keep personal information only for as long as reasonably necessary to provide the Services, fulfill the purposes described in this Privacy Policy, and comply with our legal obligations. Specifically:
- Reservation records (email, name, payment confirmation): kept while your reservation is active and for a reasonable period after launch or refund, plus retention required by tax and financial recordkeeping laws.
- Demo Line audio and transcripts: the live transcript cache is retained no more than 7 days; we may keep de-identified analytics derived from Demo Line interactions for longer to improve the Services.
- Site usage data and cookies: retained for the period described in our cookie controls or until you clear your browser.
- Marketing email subscribers: retained until you unsubscribe.
- Google Calendar data: as section 5.4 describes.
9. Your privacy choices
Depending on where you live, you may have specific rights under your state's privacy laws (for example, the California Consumer Privacy Act and similar laws in Virginia, Colorado, Connecticut, Utah, Texas, Florida, Oregon, Montana, Iowa, Delaware, New Hampshire, New Jersey, Tennessee, Minnesota, Indiana, Kentucky, and Rhode Island). Subject to the conditions and exceptions in those laws, you may have the right to:
- Confirm whether we process information about you and request a copy of that information;
- Request correction of inaccurate information;
- Request deletion of your information;
- Receive a copy of your information in a portable format;
- Opt out of the “sale” or “sharing” of your information (we do not sell or share for cross-context behavioral advertising, but you may exercise this right preemptively);
- Opt out of targeted advertising;
- Opt out of certain profiling that produces legal or similarly significant effects;
- Limit our use of your sensitive personal information (California);
- Appeal a denied request (in states that provide an appeal right); and
- Not be discriminated against for exercising your privacy rights.
9.1 How to exercise your rights
To submit a privacy request, email us at privacy@greeterhub.com with the words “Privacy Request” in the subject line and a description of your request. We may ask you to verify your identity (typically by confirming the email address on file with your reservation). We will respond within the time required by applicable law, typically 45 days, with an additional 45-day extension when reasonably necessary.
9.2 Marketing email opt-out
You can opt out of marketing emails at any time using the unsubscribe link in those emails, or by emailing privacy@greeterhub.com. We will still send you transactional messages required to administer your reservation (such as the 72-hour launch email and refund notices).
10. Children's privacy
The Services are intended for adults running service businesses in the United States. We do not knowingly collect personal information from children under 16. If you believe we have collected information from a child under 16, please contact us at privacy@greeterhub.com and we will delete it promptly.
11. Security
We use commercially reasonable administrative, technical, and physical safeguards to protect your information, including transport-layer encryption (TLS) for data in transit and AES-grade encryption for data at rest in our primary database. No system is perfectly secure, and we cannot guarantee the security of information transmitted to or from us. You are responsible for keeping the email address you use for your reservation secure.
12. Geographic scope
GreeterHub is operated from the United States and the Services are intended for use within the United States. If you access the Services from outside the United States, you understand and agree that your information will be transferred to, stored in, and processed in the United States, where data protection laws may differ from those in your country. We do not currently offer the Services in the European Union, the United Kingdom, Canada, or any other non-U.S. jurisdiction.
13. AI training
GreeterHub does not use information collected through the pre-launch Services to train AI models on identifiable individuals. Our voice runtime providers may use de-identified and aggregated data derived from Demo Line interactions to improve their underlying voice agent platforms, in line with their respective terms of service. GreeterHub never uses Google Calendar data to train AI models (section 5.2). More detailed disclosures about model training and our subprocessor relationships will be published when the GreeterHub voice agent product ships to paying customers.
14. Changes to this Privacy Policy
We may update this Privacy Policy from time to time. If we make material changes, we will notify you by email (to the address you provided for a reservation, if any) and by posting a notice on the Site, and will obtain your consent to those changes where required by applicable law. Non-material changes (such as clarifications, typo fixes, or contact-info updates) take effect immediately upon being posted with an updated “Effective” date.
15. Contact us
Agnostic Studios LLC, doing business as GreeterHub
Florida, United States
Privacy: privacy@greeterhub.com
General: hello@greeterhub.com
Legal: legal@greeterhub.com
Last updated: October 31, 2026. Prior versions are available on request.
What changed on October 31, 2026: sections 1 and 15 now name the company that operates GreeterHub, Agnostic Studios LLC, a Florida limited liability company, doing business as GreeterHub. Nothing else changed.