Garcia Technology Group
Contact & booking privacy
Contact and booking notice · Version 2026-10-07.1
Current availability
Public contact and booking submissions are not open yet. The forms show when submissions are unavailable. Authorized development tests use fictional details; they are not an invitation to submit personal or customer information.
This notice covers these contact and booking journeys. It does not set policies for separate products or payment services.
Information and purpose
The forms request a name, email address, inquiry topic and brief message. Booking also uses the selected time and the timezone reported by your browser. The message is optional for booking. Please leave out passwords, payment details and sensitive business information.
Submission requires an unchecked consent choice. Its version, the notice version and the acceptance time are recorded with the request. The permitted purposes are responding to your inquiry, managing your requested call, maintaining the business relationship and limited follow-up about that inquiry. This does not enroll you in a newsletter, campaign or promotional marketing.
Systems involved
The public forms currently accept no submissions. Local fictional tests do not send email or create provider records. A separately authorized provider test uses GTG-controlled records in Neon PostgreSQL, Calendly for scheduling and calendar invitations, HubSpot for a contact record and the latest inquiry context, and Resend for inquiry-related email to designated test recipients.
GTG retains control of acceptance, consent, booking state and follow-up. Calendly receives the booking name, email, timezone and selected time. HubSpot receives contact details, inquiry context and consent information. Resend receives the sender, recipient and message needed to handle an email. GTG notification recipients must be identified before a provider test is enabled.
Retention and choices
Local fictional test records last only for the running test process. Durable provider-test records remain until an authorized operator removes them; this implementation has no automatic deletion schedule. Form details are encrypted in GTG's durable store. Request identifiers and limited audit records support duplicate prevention and recovery.
The inquiry email includes a control to stop pending inquiry follow-up. Confirming a booking also stops pending pre-booking follow-up. An email already accepted for sending cannot be recalled by this control.
GTG's operator can remove stored form details and pending message content. This does not automatically remove records already held by other providers or their backups; those require separate provider handling. A verified privacy contact and the operational retention and deletion procedures must be published before public collection opens.
