1. About Plereme
We provide Plereme. Privacy and security questions can be sent to Plereme support.
2. Data Plereme collects
Plereme may collect and process the following data when customers use the service:
- Account information, including email address, authentication events, plan, and support messages.
- Billing information needed to process subscriptions, Spark top-ups, invoices, refunds, and disputes.
- Assistant content, including prompts, responses, conversations, generated artifacts, files, and metadata.
- Memory records, corrections, preferences, source references, and deletion/export events.
- Integration data from connected services such as email, calendar, file storage, and documents.
- Scheduled job definitions, run logs, approval records, Spark usage, provider usage facts, and audit logs.
- Technical data such as IP address, device/browser metadata, error logs, rate-limit events, and security logs.
3. How data is used
We use data to provide and protect Plereme, including to:
- Run assistant workflows, memory, files, integrations, scheduled jobs, approvals, and generated artifacts.
- Meter usage, manage Spark balances, process billing, reconcile checkout events, and prevent abuse.
- Secure accounts, detect misuse, enforce limits, and comply with legal obligations.
- Communicate about account access, billing, security, support, service changes, and policy changes.
At launch, Plereme does not send promotional or marketing emails unless a person separately opts in to receive them. Plereme may still send transactional messages needed to provide the service, including account, security, billing, purchase, support, and important service or policy notices.
4. AI providers and subprocessors
When you use an available AI feature, the prompt, selected context or files, tool results, and usage information needed for the request may be processed by the AI and infrastructure providers used for that feature. We do not sell customer content.
Do not provide highly regulated data unless we have agreed in writing that the account is approved for that use case.
5. Google Workspace data and Limited Use
Plereme's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy , including the Limited Use requirements.
Google Workspace data is used only to provide a capability the customer selected, to secure and operate it, or as required by law. Plereme does not sell Workspace data, use it for advertising, or train generalized AI or machine-learning models with it.
This page does not identify an approved AI processor for Google Workspace content. Choosing a direct model provider does not, by itself, authorize sending Workspace data to that provider. Before a Workspace capability sends content to a processor, its processing arrangement, purpose, and material handling terms must be reviewed and clearly disclosed. For current account controls, see Google Workspace data controls.
Google Workspace processing facts reviewed 5 October 2026. The policy date above remains 24 August 2026.
6. Integrations and credentials
Customers choose which integrations to connect and can disconnect them in the product. Plereme uses integration tokens and permissions only to provide requested assistant workflows, scheduled jobs, sync, retrieval, and approved actions. Disconnecting an integration stops future access. Workspace artifacts and cached derived copies are subject to the Workspace lifecycle policy; content-free tombstones may remain only to prevent duplicate actions and prove deletion.
7. Security controls
Plereme is designed with security controls appropriate for an early paid product:
- Encryption in transit for web app and API traffic.
- Access controls for accounts, workspaces, integrations, billing, and administrative surfaces.
- Audit records for assistant runs, Spark usage, provider events, integration changes, and deletion actions.
- Approval gates for sensitive external actions where the product requires confirmation.
- Rate limits, abuse monitoring, checkout reconciliation, and provider-event idempotency.
- Account export, deletion readiness, and integration credential cleanup paths.
9. Data retention
Retention depends on the plan, account state, legal obligations, security needs, and product controls. Customers can request export or deletion. Some billing, ledger, security, and abuse-prevention records may be retained when necessary for accounting, dispute resolution, fraud prevention, legal compliance, and audit integrity.
10. Customer choices
Customers can request access, export, correction, deletion, or integration disconnection by emailing Plereme support. Product surfaces may also provide self-serve controls for memory visibility, deletion, account export, and integration removal. Step-by-step instructions for reviewing, disconnecting, revoking, exporting, and deleting Google Workspace-related data are available on the Google Workspace data controls page.
11. Children
Plereme is not intended for children and should not be used by anyone under 13. Customers must not knowingly submit children's personal data without appropriate authority and legal basis.
12. Changes
We may update this policy as Plereme changes. Material changes will be reflected by updating the date on this page and, where appropriate, notifying customers through the product or account email.