Privacy Policy
Last updated: October 19, 2026
1. Who we are and what this policy covers
3SixtyCRM is a hosted CRM service operated by Binary Ideas, United States. This policy covers our website, user accounts, CRM workspaces, and connected integrations. We operate the service and process data using our infrastructure providers. If a business uses the service to manage your information, contact that business about its use of your data; we can assist with requests concerning our processing.
2. Information we process
We process account and contact details, workspace membership and settings, and the information users submit to CRM features, including contacts, messages, appointments, forms, and related activity. Depending on the features used, this can include call recordings, transcripts, and AI conversations. We also process payment and transaction references, support communications, and technical information needed to operate and secure the service, such as device, browser, session, and error information. Payment providers handle payment credentials.
We use this information to provide requested features, authenticate users, manage workspaces and billing, deliver communications, respond to support requests, and protect the service. Login cookies and local browser storage maintain sessions and application preferences.
3. Google Calendar permissions and purpose
Connecting Google Calendar is optional and requires your authorization. We request openid and email to identify and display the connected Google account; calendar.freebusy to check busy periods on your primary calendar; and calendar.events to create, reschedule, and delete the Google copies of CRM bookings assigned to you. Although the events permission permits broader event access, the current integration uses it for these booking operations.
We receive your Google email address, authorization tokens, granted permissions, connection and sync status, busy start and end times, and identifiers for events created through the integration. Busy checks do not retrieve the titles, descriptions, attendees, or contents of your existing Google events. We send the CRM booking title, description, start and end times, and an internal booking reference to Google when creating an event. Booking descriptions may contain information supplied during booking.
Busy times help calculate appointment availability for public booking pages and assisted booking. Visitors receive available slots rather than the contents of your Google calendar. Workspace members can see connection status and the connected email address according to workspace permissions.
4. Storage, providers, and access
Google connection records and access and refresh tokens are stored in Google Cloud Firestore. Tokens are stored in a server-only collection that browser clients cannot read. The service also stores Google event identifiers with CRM bookings so it can update or remove the corresponding Google event. Busy intervals are temporarily cached in server memory for up to 60 seconds of reuse; expired entries can remain in memory until cache cleanup or the server instance ends.
Our application hosting and Google Firebase/Google Cloud providers process data to run the application, authenticate users, and store records. Google receives the API requests needed for the Calendar integration. AI-assisted booking can use Vapi or Retell for voice and OpenRouter and its selected model providers for AI processing, depending on the enabled configuration. Other enabled features use providers for payments, email, SMS, voice, AI, and support; those providers receive the information needed for the feature you use. Calendar credentials are not sent to messaging, payment, or AI providers.
Authorized Binary Ideas personnel may access service data where needed to operate, secure, or support the service. Access to Google user data is limited to the permitted purposes below. Data may be processed in the United States and other countries where our service providers operate.
5. Google data, AI, and Limited Use
Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements.
When AI-assisted booking is enabled, the assistant and its configured AI or voice providers may receive available appointment slots calculated using Google busy periods to help the user select a time. The Calendar integration does not send Google authorization tokens, raw busy intervals, or existing Google event contents to AI models. Information separately supplied in CRM conversations or bookings may be processed by the enabled AI features.
We do not use Google user data to develop, train, or improve generalized or non-personalized AI or machine learning models. We do not sell Google user data, use it for advertising, or transfer it for unrelated purposes. Transfers are limited to providing or improving the user-facing integration, your explicit direction, security purposes, legal requirements, or other purposes permitted by the Google policies. Human access to Google data is limited to your affirmative agreement for specific data, security investigations, legal obligations, or aggregated and anonymized internal operations as permitted by those policies.
6. Security
We use authenticated sessions, workspace permission checks, database access rules, and server-side handling of integration credentials. Google API calls use HTTPS. These controls reduce risk but cannot guarantee absolute security. Protect your login, invite only authorized team members, and review integrations regularly.
7. Retention, disconnection, and deletion
Google credentials and connection records are retained while the integration is connected, including when a connection needs reconnection, until disconnected or deleted. In your workspace Settings, open Calendar sync and disconnect Google Calendar. The service attempts to revoke the token with Google and deletes its saved tokens and connection record. A workspace administrator may also disconnect a member.
You can independently revoke authorization through Google Account third-party connections. Revoking at Google blocks future access but does not itself delete records already stored in the CRM. Previously created Google events remain after disconnection and can be deleted in Google Calendar. CRM bookings and their Google event references also remain until those records are deleted.
We retain CRM and account information as needed to provide the service, handle support and disputes, and meet legal obligations. Contact us to request deletion of your account, workspace, or stored integration data. We review the request and your authority over the affected records; information required for legal, security, or accounting purposes may be retained. Deletion of service records does not automatically delete copies held independently by Google, other connected providers, or recipients of communications.
8. Your choices and policy changes
Contact us to request access, correction, export, or deletion of your personal information, or to raise a privacy concern. Available rights depend on applicable law and your relationship with the workspace owner. You may decline optional integrations or revoke their access. We publish policy updates here with a revised date and communicate material changes through the service or account contact details.
Contact
Contact Binary Ideas, United States, at support@binaryideas.com for questions or requests about this page.