DARWIN AI CALENDAR
Privacy Policy
Effective date:
This policy explains how information is handled when you schedule a meeting at darwin.raphaelporto.com or connect the host’s Google Calendar.
1. Who operates this service
Raphael Porto manages this scheduling site for meetings with his Darwin AI clients. For privacy, support, or data requests, contact raphael.porto@getdarwin.ai. This policy covers this scheduling site; other Darwin AI products and websites have their own policies.
2. Information we handle
- Booking details: your name, email address, selected meeting type and time, and any notes or answers you submit.
- Client records: the host may save your name, company, email, client tier, and internal relationship notes to manage your personalized booking page.
- Google account and calendar data: the connected host’s verified Google email address, authorization tokens, calendar busy periods, and information about meetings created through this site, including event identifiers and Calendar or Meet links.
- Technical information: the hosting infrastructure may record IP addresses, request paths, browser information, timestamps, and errors for operation and security. Request paths can include a personalized booking link.
Guests do not need to grant Google account access to book. Only the host connects a Google Calendar.
3. How information is used
We use information to display available times, avoid calendar conflicts, personalize client pages, create meetings and Google Meet links, send calendar invitations through Google, communicate about your meeting, and operate and protect the service. Providing a name and valid email is necessary to create a booking; additional required questions are identified in the booking form.
4. Google Calendar access and Limited Use
The host authorizes access to verify the account’s email, check calendar availability, and create meeting events. The event permission allows viewing and editing calendar events; this application uses it to create bookings and does not fetch the titles or descriptions of existing meetings. Guests see available times rather than the host’s other event details.
Google user data is used only to provide and protect the scheduling features described here. We do not sell it, use it for advertising, or use it to train AI models. Our handling of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Human access to Google user data is limited to the host’s authorized use, assistance with the account holder’s permission, security investigations, or legal requirements.
5. Sharing and external services
Booking details, including your notes and answers, are sent to Google Calendar and included in the meeting event and invitation. The host, invited participants, and people with access to the relevant calendar or invitation may see those details. Google and recipients’ calendar or email providers process their copies under their own policies. See Google’s Privacy Policy.
Hosting and infrastructure providers process information needed to serve and secure the site. Access by authorized service administrators is limited to operating, maintaining, and protecting it. Information may also be disclosed when required by applicable law. Google user data is subject to the Limited Use limits described above.
Google and infrastructure providers may process information outside your country. Their processing is subject to their applicable terms and privacy policies.
6. Storage, security, and retention
The site uses HTTPS. Host settings and client records are stored in private server storage; Google access and refresh tokens are encrypted at rest. Access to the owner dashboard requires authentication.
Client records are kept while needed to manage the client relationship, unless removed earlier following a request. Google connection credentials are kept while the integration is maintained and removed when the host decommissions the connection. Meeting details remain in Google Calendar and invitation recipients’ systems until removed there under their respective retention practices. The app does not maintain a separate local database of submitted booking answers.
Operational logs are retained according to hosting maintenance and log-rotation practices. Backup copies may remain until replaced or removed. Information may be retained where necessary for security or applicable legal obligations. No system can guarantee absolute security.
7. Cookies
The owner dashboard uses an essential sign-in cookie with a maximum lifetime of eight hours. Connecting Google uses a temporary security cookie lasting up to ten minutes. The site does not use advertising cookies or third-party analytics scripts. Google may set its own cookies when you visit Google’s authorization or meeting services.
8. Your choices and requests
Contact raphael.porto@getdarwin.ai to request access, correction, or deletion of information held by this service, or to raise a privacy concern. Depending on applicable law, you may have additional rights, including objection or restriction of processing. We may need to verify your identity before handling a request.
The host can revoke calendar access in Google Account connections and request removal of stored connection credentials. Revoking access stops future authorized API access; it does not automatically delete existing calendar events or invitation copies. Removing a local client record also does not remove copies already held by Google or recipients.
9. Changes to this policy
Updates will be published on this page with a revised effective date. Material changes to Google data access or use will be disclosed before the new use begins, with renewed authorization where required.