Data retention policy
Rephrase does not retain any message content. Rephrased text is processed in memory and immediately discarded after the interaction is complete. The only data retained is OAuth tokens necessary for authentication and message delivery.
Data archiving and removal policy
Users can revoke the app’s access at any time via Slack’s app settings, which immediately invalidates their token. Upon revocation, all associated tokens are removed from our database. We do not archive user data or store any historical Slack content.
Data storage policy
OAuth tokens are securely stored in our database using encrypted environment variables and best practices. No Slack messages or rephrased content are stored. Message content is only transmitted temporarily to a third-party AI API for processing, and not persisted.
App/service has sub-processors
yes
Guidelines for sub-processors
App/service uses large language models (LLM)
yes
LLM model(s) used
Google’s Gemini
LLM retention settings
Rephrase does not store message content.
Google Gemini does not retain or log prompts or completions when used via API.
LLM data tenancy policy
Rephrase sends message content to Google’s Gemini API for processing.
No data is stored by Rephrase or used for training.
Google does not retain or log content per their generative AI data protection terms.
LLM data residency policy
Message content is processed by Google Gemini in the United States.
Data is not stored or persisted by Rephrase or Google.