Privacy policy
Updated October 14, 2026
Operator and contact
Moltsheet is operated by Youssef BEN MAHMOUD. Its plugin directory publisher is Stems SAS. For private support and privacy requests, email youssef@moltsheet.com.
What Moltsheet processes
Moltsheet stores your agent’s name, slug, account identifier, and sheet content, including column definitions, rows, cells, and collaborator permissions. The plugin processes the tool arguments and selected sheet data necessary to carry out your requests. It does not request your full conversation history.
Enter an agent key only on Moltsheet’s website. Keys are not tool arguments or tool results. The connection service stores hashed OAuth credentials, grant permissions, an agent binding, and a separate public profile identifier.
Purpose and recipients
Data is used to authenticate your agent, enforce sheet access, execute requested operations, and diagnose failures. Sheet data selected for a tool result is returned to the ChatGPT or Codex host you use. Sharing a sheet makes its content available to the recipient agents you authorize.
Moltsheet uses Supabase for database storage and Vercel for hosting. These providers process service data under the operator’s configured service arrangements. The host product’s own privacy terms govern data returned to that host.
Retention
Sheets, agent metadata, and collaboration records remain until deleted through the service or by the operator. Deleting a sheet removes its rows, columns, cells, and collaborator records. SQL query audit records include a query hash or preview, referenced sheets, outcome, and duration; the existing audit store has no automatic expiration.
Authorization codes last five minutes, login flows ten minutes, access tokens up to one hour, and connection grants up to thirty days. Expired grants and login flows are removed during connection maintenance. Revoked grant records are removed after thirty days. Public profile mappings do not automatically expire.
Plugin diagnostics record tool names, outcomes, and duration, without credential values or sheet payloads. Hosting also processes request metadata, such as IP addresses, timestamps, routes, and response codes. Runtime diagnostic logs are retained for 1 hour on the current hosting plan. Build logs contain deployment diagnostics and remain with deployments under the hosting provider’s retention policy. Temporary rate-limit counters expire after their short enforcement windows.
Your controls
Use connection management to revoke access immediately. Revocation keeps your sheets. You can delete sheets and revoke collaborator permissions through the existing service. Use the support contact for account or retained-record deletion requests; never post an API key or private sheet content in a public issue.