Data handling
What Cust imports, how to control its scope, and how to request access or deletion.
Controller and processor
For customer personal data processed through the service, you are the data controller and Cust acts as your processor under the Data Processing Agreement. Cust's security overview states that customer data is not used to train AI models.
Control what is imported
The scope depends on each connection's permissions and configuration. Cust can contain customers, prospects, former customers, and other company records. Connecting a CRM does not by itself restrict every source to won deals or current paying customers.
- CRM: review the selected objects, fields, record filters, and connected user's access. CRM guide.
- Email: review the connected mailboxes, ignored domains, and exceptions. Inbox's customer-focus filter changes what you see, not what is ingested. Email and calendar guide.
- Slack: enable the channels you want synced and map them to the correct companies. Slack guide.
- Support, calls, and product data: review each provider's supported resources and filters. Matching an imported interaction to a company is separate from limiting what the provider account can access.
Review connection permissions
In Settings → Integrations, open the provider's details and review Connection, Access granted, and Data synced. The connection review guide explains each panel and its states.
Access granted shows provider-reported scopes where available. For opaque API keys, review the permissions of the credential at the provider. BigQuery access is governed by the connected service account's IAM roles. If no scope list is available, follow the explanation in the panel and inspect the provider's app or credential permissions.
Use Data synced to check the configured resources and their individual last-sync times. Provider permission defines what the connection can access; Cust's resource selection, queries, and filters define what it imports. Review both when narrowing scope.
Ignored email domains
Organization settings can ignore emails whose participants are all within the ignored scope, with configurable exceptions. The check considers the sender and To, Cc, and Bcc recipients. A mixed conversation containing both an ignored domain and an external participant is not necessarily excluded.
Use Settings to review this configuration. Do not treat a domain entry as a rule that removes every message involving that domain.
Historical imports
History varies by source:
| Source | Normal initial scope |
|---|---|
| 180 days, approximately six months. | |
| Calendar | Fetching can cover five years back and two years ahead. Meeting processing and recurring-event handling narrow the future events used for actions. |
| CRM | Accessible records that match the sync configuration. |
| Slack | Up to 30 days for a newly enabled channel. |
| Pylon | The last seven days of issues on the initial sync. |
| Gong and Grain | Available meeting details, summaries, or transcripts, subject to provider access and usable content. |
A provider may retain less history, restrict API access, or delay processing. Check the relevant integration guide for details rather than assuming a single lookback applies to all sources.
Disconnecting and deleting
Stopping a sync or disconnecting a provider generally preserves data already imported. It does not constitute a deletion request. Some configuration actions, such as removing managed CRM fields, explicitly delete their stored values and show a confirmation preview.
Contact support@cust.co for data access or deletion requests. The DPA describes the applicable processing and end-of-service arrangements.