Overview
CrewLink is a voice assistant for CRM workflows. The app helps users connect one active CRM, ask questions by voice, review CRM information, and create or manage CRM items when the connected account permits those actions.
This policy explains what information CrewLink may process, why it is used, and what choices users have. CrewLink should only access CRM data authorized by the user or by the organization that owns the connected CRM account.
Information We Process
CRM account data
- CRM provider selected by the user, such as JobNimbus, HubSpot, Zoho, Salesforce, ServiceTitan, Leap, Jobber, AccuLynx, or a custom CRM.
- Records the connected CRM account allows CrewLink to access, such as jobs, tasks, contacts, customers, notes, calendar events, files, work orders, and related project information.
- User profile or team information returned by the CRM when the connected account grants access.
Voice and assistant data
- Microphone input is used to convert spoken instructions into text.
- Transcriptions and assistant responses may be processed to answer questions, search CRM records, or create CRM actions requested by the user.
- The in-app assistant uses Claude, an AI model by Anthropic. Only after the user gives permission in the app, the user's messages and the CRM data needed to answer them (for example names, addresses, appointments and job details) are sent through CrewLink's server to Anthropic to generate the response.
- Anthropic processes this data only to provide the assistant's responses. Users can withdraw permission at any time in Settings → AI assistant; the rest of the app keeps working without it.
Credentials and tokens
- For API-key based CRMs, CrewLink stores the API key in the iPhone Keychain and, encrypted (AES-256-GCM), in our backend linked to the user's account, so the same CRM user loads on any iPhone after sign-in. Deleting the account deletes this data.
- For OAuth-based CRMs, a secure backend is used to complete authorization and manage tokens. Client secrets and refresh tokens should not be stored directly inside the iPhone app.
- Credentials are used only to connect the selected CRM and perform the actions requested by the user.
Diagnostics and usage data
- CrewLink may collect technical logs, connection status, error messages, request timing, and feature usage needed to operate and improve the service.
- Sensitive CRM content should be minimized in diagnostics whenever possible.
- If analytics, billing, crash reporting, or monitoring services are added, this policy should be updated before release.
Subscriptions and purchase history
- When you subscribe through Apple In-App Purchase, Apple processes payment and may share subscription status, product identifiers, and renewal dates with CrewLink so we can activate your organization plan and seat limits.
- CrewLink stores subscription status, plan tier, seat limits, and Apple original transaction identifiers in our backend.
- We do not receive your full Apple payment card details.
How Information Is Used
CrewLink uses information to connect the selected CRM, answer voice requests, show CRM records, create requested CRM actions, troubleshoot errors, protect the service, and support account administration.
CrewLink does not sell user CRM data. CrewLink should not use customer CRM content for advertising.
Third-Party Services
CrewLink may connect to the CRM provider selected by the user. If enabled, CrewLink may also use Apple speech or voice features on the device, Anthropic (Claude) for assistant responses with the user's permission, Supabase for backend storage, Vercel for hosting, and Apple In-App Purchase for subscriptions.
Each connected CRM and third-party provider may process information according to its own privacy policy and account permissions.
Security
CrewLink is designed to keep API keys in secure local storage on the iPhone for direct API-key testing, and to move OAuth secrets and refresh tokens to a secure backend for production CRM integrations. Backend tokens should be encrypted at rest and protected by access controls.
User Choices
- Disconnect a CRM integration from the app settings.
- Delete a locally stored API key from the iPhone.
- Delete the CrewLink account from the app (Settings → Privacy and security → Delete account), which removes backend-stored account records and CRM credentials.
- Allow or withdraw the AI assistant's permission to send data to Anthropic in Settings → AI assistant.
- Revoke CRM access directly from the CRM provider account when the CRM supports it.
- Disable voice features by denying microphone or speech recognition permissions in iOS Settings.
Data Retention
Local credentials remain on the iPhone until the user removes them or deletes the app. Backend records and OAuth tokens should be retained only as long as needed to provide the service, comply with legal obligations, resolve disputes, or maintain security.
Children
CrewLink is intended for business CRM use and is not directed to children.
Contact
For privacy questions, data deletion requests, or support, contact CrewLink at support@vigulab.com.