Privacy & data use

For customer CRM records and connected-workspace content, the customer company decides why and how the information is used. Elevate handles that information on the company's instructions. Elevate separately decides how it uses its own account, billing, service-security, and website-operational data.

Requests about a person's CRM record normally go to the customer company. If Elevate receives one directly, the design is to verify it, route it securely to the correct company, and provide the technical tools needed to respond.

• Account identity, company membership, permissions, and security-factor state.
• Customer-entered CRM records such as companies, contacts, deals, tasks, notes, decisions, and evidence links.
• Only the Google messages or bounded excerpts needed for a visible CRM, drafting, summarization, or follow-up feature.
• Content-free audit metadata, digests, security events, and operational measurements needed to protect and run the service.

Elevate does not intentionally support health, biometric, or similarly sensitive categories at launch. The intended design warns users and redacts such content from external AI requests where practical; formal support requires a separate privacy risk assessment.

The intended Gmail permissions are identity, read-only message access, and send access. A company administrator must approve Gmail use for the workspace, and each person connects their own Google account. There is no domain-wide delegation.

Elevate may use selected message content to summarize customer context, propose tasks, and draft email. Drafting may happen automatically, but every email remains in a review pane until a person edits, rejects, defers, or approves the exact version. No approval means no send.

An external AI provider may receive only the task-minimized excerpt needed for the user-visible feature. Google Workspace information is not sold, used for advertising, mixed across customer companies, or used to train or improve a generalized AI model. A specific user's personalized writing profile must remain isolated to that user and resettable.

Elevate's use of information received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements. Read the Google Workspace API user-data policy.

The current product decision proposes deleting or truly anonymizing ordinary CRM records after 24 months without meaningful customer activity, subject to a documented legal duty, claim, or narrower customer rule. This is a configurable product default, not a GDPR safe harbor, and automated enforcement is not active yet.

For personalized email writing, the current proposal is to keep only selected sent-email samples for no more than 90 days, derive a user-specific style profile, and then delete the raw samples. That period is not active and must be shortened if Google's final approval, cache rules, customer instructions, or legal review require it. Users must be able to reset the style profile.

A valid deletion request takes priority unless a narrow, documented exception applies. Accounting evidence and legal holds must be classified and separated from ordinary CRM data instead of extending the whole customer record indefinitely.

The intended hosting policy is EU-first for the main database, files, and supported processing. A necessary transfer outside the EU requires an approved provider, a documented purpose, appropriate contractual and legal safeguards, and the minimum data needed for the task.

The product is designed around tenant isolation, least privilege, encrypted provider credentials, multifactor authentication, bounded requests, human approval for external effects, content-minimized audit trails, and revocable personal connections. Production evidence and independent assessment remain required before customer access.

• Connect or revoke a personal Google account.
• Review, rewrite, reject, defer, or approve email drafts.
• Reset a personalized writing profile.
• Ask the customer company to access, correct, export, restrict, object to, or delete applicable personal information.

Final request channels and response details will be published with the operating entity's verified privacy contact before Live customer onboarding.