1. Google user data we access
When a user connects a Google account from TracktCRM, we access only the data the user authorizes for that integration:
- Google account profile: name, email address, and profile identifier, to show which Google account is connected.
- Gmail: send and receive email, and sync threads linked to CRM leads or deals, when the user enables email from TracktCRM.
- Google Calendar: create and update calendar events linked to CRM meetings, site visits, or follow-ups.
- Google Meet (when enabled): create and read meeting spaces, meeting links, and meeting metadata tied to CRM records.
- Google Drive (when enabled): list metadata for files or folders the user selects, and upload or attach files the user chooses for a CRM record. We do not request access to the user's entire Drive.
- Google Sheets / Forms (when enabled): read or write spreadsheet data or form responses the user selects, to export CRM records or import leads/contacts.
We do not access Google data unrelated to these CRM features. Scope is limited to the permissions the user grants in Google's OAuth consent screen.
2. How we use Google user data
Google user data is used only to provide or improve user-facing TracktCRM features requested by that user:
- Connect the user's Google account and display connection status.
- Send or sync Gmail and schedule Calendar / Meet events from leads and deals.
- Attach selected Drive files to CRM records.
- Export or sync selected CRM data with Google Sheets.
- Import selected Google Form responses as leads.
- Show meeting links, metadata, and optional AI summaries inside the user's own CRM workspace.
Limited Use: TracktCRM's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not:
- sell Google user data;
- use Google user data for advertising, retargeting, or personalized ads;
- use Google user data to determine credit-worthiness;
- use Google Workspace APIs to develop, improve, or train generalized or non-personalized AI / ML models;
- transfer Google user data to data brokers or information resellers.
Any AI summary of a meeting or conversation is generated only to provide that feature to the same customer workspace. It is not used to train models.
3. How we store Google user data
- OAuth access and refresh tokens are stored on TracktCRM's servers so the integration can keep working until the user disconnects it.
- We store connection metadata (Google account name/email, token expiry) and IDs needed for the feature (calendar event IDs, Meet space IDs, selected Drive file/folder IDs, spreadsheet IDs, form IDs).
- Imported Form responses and selected Sheet rows are stored as CRM lead/contact records.
- Meeting titles, times, links, and optional recording/transcript references may be stored on the related CRM deal.
- Data is stored on our cloud hosting infrastructure and transmitted over HTTPS/TLS.
4. How we share, transfer, or disclose Google user data
We do not sell Google user data. We do not share it with advertisers. Google user data may be disclosed only:
- to Google, to provide the requested API feature;
- to cloud hosting and infrastructure providers who process data solely to operate TracktCRM, under confidentiality obligations;
- to other users inside the same customer's TracktCRM workspace, according to that workspace's roles and permissions;
- if required by law, or to protect security and prevent abuse.
We do not transfer Google user data to third parties for advertising, data brokerage, lending, or AI model training.
5. Data protection
- HTTPS/TLS encryption in transit.
- Access controls so only authorized workspace users and systems can use connected Google data.
- OAuth tokens are stored with restricted access on our servers.
- Human access to Google user data is limited to cases needed to provide the service the user requested, fix issues, meet legal obligations, or protect against security threats.
6. Retention and deletion
- Google connection data is kept while the integration stays connected and the TracktCRM account is active.
- The user can disconnect Google (Gmail, Calendar, Meet, Drive, Sheets, or Forms) at any time from TracktCRM → Account Setup / Integrations. Disconnecting revokes TracktCRM's access.
- After disconnect or a deletion request, we delete or anonymize stored Google tokens and Google connection records within 30 days, unless a longer period is required by law.
- CRM records created from imported Form/Sheet data remain in the workspace until the customer deletes those leads or closes the account, because they have become business records of that customer.
- To request deletion, email traktcrm@gmail.com.
7. Other information we collect
Independent of Google, TracktCRM may process:
- Account details: name, email, phone, company.
- CRM data: leads, deals, pipeline stages, tasks, notes, files, and communications you store in the product.
- Channels you connect: WhatsApp Business messaging metadata and message content synced into your workspace; Meta / Google Ads lead form data you authorize.
- Website forms: name, email, phone, company and message when you contact us or book a demo.
- Technical data: IP address, browser, device, and basic analytics (for example page views) to operate and improve the service.
We use this information to provide the CRM, respond to enquiries, send service messages, improve reliability and security, and meet legal obligations (including India's Digital Personal Data Protection Act where applicable). We do not sell personal data.
8. Changes
If we change how we use Google user data or other personal data, we will update this page and notify users by email or in-app notice before the change takes effect where required. Continued use after changes means you accept the updated policy. See also our Terms & Conditions.
9. Contact
TracktCRM
Email: traktcrm@gmail.com
Phone: +91 70098 11184
Address: 3rd Floor, D-231, Phase 8B, Sector 91, Sahibzada Ajit Singh Nagar, Punjab 140308
Support hours: Mon–Fri, 10:00–19:00 IST
Questions? Contact us or chat on WhatsApp.