Introduction
Devon, operated by CodivineLabs (“Company”, “us”, “we”, or “our”), operates the Devon web application, API, and embeddable chat widget at https://getdevon.com (hereinafter referred to as “Service”).
Our Privacy Policy governs your visit to the Service and explains how we collect, safeguard, and disclose information that results from your use of our Service.
By using the Service, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, the terms used in this Privacy Policy have the same meanings as in our Terms and Conditions.
This page describes product behavior. It is not a claim of legal certification or compliance status (including GDPR or HIPAA).
Definitions
Service means the Devon website, dashboard, API, and embeddable chat widget operated by Devon.
Personal Data means data about a living individual who can be identified from those data (or from those and other information either in our possession or likely to come into our possession).
Usage Data is data collected automatically, either generated by the use of Service or from Service infrastructure itself (for example, page URL, session identifiers, or device metadata).
Data Controller means a natural or legal person who (either alone or jointly or in common with other persons) determines the purposes for which and the manner in which any personal data are, or are to be, processed. For the purpose of this Privacy Policy, we are a Data Controller of your account and platform operations data.
Data Processors (or Service Providers) means any natural or legal person who processes the data on behalf of the Data Controller. We may use the services of various Service Providers in order to process your data more effectively.
Data Subject is any living individual who is the subject of Personal Data.
User is the individual using our Service. The User corresponds to the Data Subject, who is the subject of Personal Data.
Information Collection and Use
We collect several different types of information for various purposes to provide and improve our Service to you.
Types of Data Collected
Account and registration data
While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you (“Personal Data”). Personally identifiable information may include, but is not limited to:
- Email address
- First name and display name
- Password hash (we never store plaintext passwords)
- Plan, billing, and organization membership details
Widget visitor and chat data
When visitors interact with a Devon chat widget embedded on a customer website, we may collect:
- Anonymous session fingerprint (deferred until the visitor starts chat when consent is required)
- IP address and user agent (retained for a limited period, then nulled per retention settings)
- Page URL and referrer context
- Chat messages, intents, and contact details the visitor submits
- Lead and meeting booking details (name, email, phone, company, preferred times)
Integration and OAuth data
When an organization connects third-party integrations, we store encrypted OAuth tokens and related metadata necessary to operate those integrations (for example Google Calendar, HubSpot (beta), or Salesforce (coming soon)).
Waitlist and beta program data
If you join the waitlist or beta program, we may collect your email, name, optional company or message, and signup metadata. Waitlist records may be retained after admin removal so we can notify you when Devon goes live unless you request erasure.
Google User Data
When an organization connects Google Calendar to a Devon bot, Devon requests access to the following Google user data through OAuth:
- Google account email address (
userinfo.email) — to identify which Google account is connected and show connection status in the dashboard. - Calendar free/busy information (
calendar.readonly) — to check whether a requested meeting time is available before booking. - Calendar events (
calendar.events) — to create, update, and send calendar invitations for meetings booked through Devon chat, including Google Meet links when applicable.
Devon uses this data only to power in-chat meeting scheduling: checking availability, creating or updating calendar events on the connected account, and returning event and Meet links to the visitor. Devon does not read or store the full contents of unrelated calendar events — availability checks use Google's free/busy API, which returns busy time ranges only.
Google user data obtained through Google OAuth is not sold to third parties and is not used for advertising or marketing.
Google data storage, protection, and retention
- OAuth tokens (access and refresh tokens) are stored in Devon's PostgreSQL database and encrypted at rest using AES-256-GCM.
- Connection metadata (connected Google account email, calendar ID) is stored alongside the encrypted tokens.
- Meeting records Devon creates locally (event ID, title, start/end time, event link, encrypted attendee email) are stored in PostgreSQL. Attendee contact details come from the visitor in chat, not from Google profile data.
- Data is hosted on Railway infrastructure with PostgreSQL and Redis. Data in transit uses TLS.
Retention: Google OAuth tokens and connection metadata are kept until the organization disconnects Google Calendar in bot settings, deletes the bot, or deletes their Devon account. Local meeting records follow conversation and account retention rules.
Deletion: Disconnect Google Calendar under Dashboard → Bots → Booking. Account deletion under Settings → Delete account removes stored tokens and connection data. Calendar events already created in Google Calendar remain in the user's Google account until removed there; Devon cannot delete events from Google after creation.
Google API Services User Data Policy
Our app's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Use of Data
Devon uses the collected data for various purposes:
- To provide and maintain our Service
- To operate chatbots, lead capture, and meeting booking features
- To notify you about changes to our Service or your account
- To provide customer support
- To gather analysis or valuable information so that we can improve our Service
- To monitor the usage of our Service and detect, prevent, and address technical issues
- To carry out our obligations and enforce our rights arising from any contracts entered into between you and us, including for billing and collection
- To provide you with notices about your account and/or subscription
- For any other purpose with your consent
Our Roles: Controller and Processor
For the personal data of our own customers (your account, billing, waitlist, and platform operations data), Devon is the Data Controller.
For the data your bots ingest and collect (knowledge-base content, end-user conversations with your bot, and leads captured by your bot), Devon acts as a Data Processor on your behalf: you are the controller of that data and we process it only to provide the Service. If you chat with a Devon-powered bot on another company's website, that company is the controller of your conversation and their privacy notice applies; we will refer any privacy request you send us about such data to them and assist them in fulfilling it where appropriate.
AI Features and Google Data
Devon uses third-party large language models (for example OpenAI and Anthropic) for chat replies and knowledge retrieval. Google user data obtained through Google OAuth APIs is not used to train, retrain, or improve generalized AI or machine learning models. Calendar availability checks and event creation run server-side via Google APIs; raw Google Calendar data is not sent to AI providers for model training.
Human access: Authorized organization admins may view meeting booking results (event title, time, links) in the Devon dashboard. During human handoff, assigned teammates may read chat messages to assist visitors — this applies to chat content, not to bulk Google Calendar data. Devon platform operators do not routinely read Google Calendar data except when necessary to investigate a support issue you report, and only with your organization's involvement.
Retention of Data
We will retain your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use your Personal Data to the extent necessary to comply with our legal obligations, resolve disputes, and enforce our legal agreements and policies.
In practice:
- Account data is kept for the life of your account and deleted when the account is erased.
- Visitor IP and user agent fields are nulled after the configured retention period.
- Chat and lead data are kept until you delete them, delete the bot, or erase the account (or until a configured retention window applies).
- Google OAuth tokens are kept until Google Calendar is disconnected or the bot or account is deleted.
- Integration webhook delivery logs are purged according to retention settings.
Transfer of Data
Your information, including Personal Data, may be transferred to — and maintained on — computers located outside of your state, province, country, or other governmental jurisdiction where the data protection laws may differ from those of your jurisdiction.
Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.
Devon will take all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy. No transfer of your Personal Data will take place to an organisation or a country unless there are adequate controls in place including the security of your data and other personal information.
Disclosure of Data
We may disclose personal information that we collect, or you provide:
Disclosure for law enforcement
Under certain circumstances, we may be required to disclose your Personal Data if required to do so by law or in response to valid requests by public authorities.
Business transaction
If we or our subsidiaries are involved in a merger, acquisition, or asset sale, your Personal Data may be transferred.
Other cases
We may disclose your information also:
- To fulfill the purpose for which you provide it
- For any other purpose with your consent
We do not sell personal data or Google user data to third parties. We do not use Google user data for advertising or marketing.
Security of Data
The security of your data is important to us, but remember that no method of transmission over the Internet or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.
Secrets and sensitive contact fields use AES-256-GCM encryption. OAuth tokens and PII contact fields are encrypted at rest. Lookup fields use keyed HMAC hashes where applicable. We avoid logging raw transcripts, tokens, or contact details by default.
Your Data Protection Rights
We aim to take reasonable steps to allow you to correct, amend, delete, or limit the use of your Personal Data.
In certain circumstances, you have the following data protection rights:
- The right to access, update, or delete the information we have on you
- The right of rectification — to have your information rectified if inaccurate or incomplete
- The right to object to our processing of your Personal Data
- The right of restriction — to request that we restrict processing of your personal information
- The right to data portability — to receive a copy of your Personal Data in a structured, machine-readable format
- The right to withdraw consent where we rely on consent to process your personal information
Signed-in dashboard users can export or erase their account from Settings → Download my data and Settings → Delete account. Organization admins can look up, export, or erase visitor and lead data by email under Settings → Visitor Data. Erasure deletes local Devon data and attempts best-effort CRM deletes when HubSpot (beta) links exist. Copies already sent to Slack, email, customer webhooks, calendars, or AI providers cannot be recalled.
To permanently delete waitlist or beta contact records we hold outside a signed-in account, use Remove my contact details. Public privacy forms do not delete platform accounts.
Service Providers
We may employ third-party companies and individuals to facilitate our Service (“Service Providers”), provide Service on our behalf, perform Service-related services, or assist us in analysing how our Service is used.
These third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.
Key service providers include:
| Tool | Privacy Policy |
|---|---|
| Google (Calendar OAuth) | policies.google.com/privacy |
| OpenAI | openai.com/policies/privacy-policy |
| Anthropic | anthropic.com/legal/privacy |
| Resend | resend.com/legal/privacy-policy |
| HubSpot (beta) | legal.hubspot.com/privacy-policy |
| Salesforce (coming soon) | salesforce.com/company/privacy |
| Railway (hosting) | railway.com/legal/privacy |
Organization customers should execute data processing agreements with vendors where required for their use case.
Links to Other Sites
Our Service may contain links to other sites that are not operated by us. If you click a third-party link, you will be directed to that third party's site. We strongly advise you to review the Privacy Policy of every site you visit.
We have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.
Children's Privacy
Our Services are not intended for use by children under the age of 18 (“Child” or “Children”).
We do not knowingly collect personally identifiable information from Children under 18. If you become aware that a Child has provided us with Personal Data, please contact us. If we become aware that we have collected Personal Data from Children without verification of parental consent, we take steps to remove that information from our servers.
Changes to This Privacy Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.
Contact Us
If you have any questions about this Privacy Policy, or wish to exercise any privacy right, contact your Devon organization admin for visitor or lead data on another organization's bot. For platform account questions, email [email protected] or visit our Contact page.