How Entake handles your data.
This policy covers the Entake Reply Chrome extension and the Entake web and mobile applications.
What the extension does
Entake Reply reads the customer message displayed in your dealership CRM, sends it to Entake's backend to generate replies that follow the Entake System methodology, and shows those replies so the rep can copy and paste them.
Data collected
- Customer message text you explicitly choose to generate a reply for. Sent to api.entakeai.com over HTTPS.
- Channel and stage you select (email/text, follow-up/new lead/objection/cold).
- Your Entake auth token and email, stored locally in Chrome extension storage so you stay logged in.
- Optional thumbs up/down feedback on generated replies, to improve reply quality.
What is NOT collected
- The extension does not read customer names, phone numbers, SSNs, payment data, or any other dealership CRM content beyond the message text you choose to process.
- The extension does not access your browsing history, cookies, or any other site.
- No advertising analytics or cross-site tracking of any kind.
How data is used
Customer messages are processed to generate replies. Replies may be stored in Entake's database to power your dealership's reply history, allow managers to review and approve golden example replies, and improve model quality. Data is scoped to your dealership account.
Data sharing
Entake does not sell personal data. Customer message text is sent to OpenAI's API for language-model processing. OpenAI does not use API inputs to train its models.
Security
All data is transmitted over HTTPS. Backend data is stored in AWS RDS with role-based access controls. Auth uses industry-standard JWT tokens.
Your rights
Log out of the extension anytime to clear your local auth token. Contact us to request deletion of reply history.
Contact
Questions: sales@entakeai.com