Privacy — processing and readiness
This is a transparent inventory of product data flows and decisions still required. It does not replace an operator-specific privacy notice.
1. Data the product handles
Account and membership records; brand information; customer-imported contacts, companies and source/consent records; email content, delivery events and connected-mailbox threads; product events; integration credentials; billing references; audit and usage records. The data present depends on the features and connections a workspace actually uses.
2. Purposes and role allocation
The application uses data to authenticate users, maintain workspace permissions, prepare and execute approved email work, process replies, measure observed outcomes and operate billing and security. The operator must identify where it acts as controller and processor, the applicable legal bases, and customer instructions in a signed agreement. A generic product description cannot determine every customer’s lawful basis.
3. Provider processing and location
Authorized connections can transfer relevant data to email, CRM, AI, storage and billing providers. AI processing requires configured authorization and must be reviewed against actual provider terms. Disabling response storage is not a zero-retention guarantee. Deployment location does not imply that all providers process only in the EU. Exact entities, locations and transfer mechanisms remain to be confirmed.
4. Cookies and preferences
Authentication uses session cookies; the application stores the active workspace preference and sendalto_locale language choice. Public language switching sets the language preference for up to one year. This public website does not include advertising pixels or third-party analytics scripts. Any future nonessential tracking requires a separate deployment-specific assessment and notice.
5. Retention and rights
Authorized workspace privacy operations support export and deletion workflows. The operator must publish actual retention periods by category, backup expiration, identity-verification and request-response procedures, and the privacy contact and supervisory authority where applicable. Suppression records can be needed to honor a refusal; accounting or security duties may require limited retention. These decisions must be documented, not assumed.