Privacy Policy
Last updated 19 November 2026
What Avely is
Avely is an applicant tracking system (ATS) used by recruiting teams to manage jobs, candidates, and hiring pipelines. This policy covers the account owner (the company using Avely) and its staff users (recruiters, hiring managers), and (separately, where noted) the candidates and contacts whose information staff users add to the system.
Google user data that Avely accesses
If you connect your Google account, Avely accesses only the following Google user data:
- Your Google Account email address.
- Google Calendar data: your free/busy time ranges at a proposed interview time (not the details of those events); your next five upcoming events (title, time, location and meeting link), shown only to you on your Avely dashboard; and the interview events Avely creates for you (title, time, the attendees you chose, and the location or Google Meet link).
- Gmail data: none. Avely can only send messages you write in Avely. It cannot read, search or store anything in your mailbox.
Google user data: what Avely accesses and how it is used
When a staff user connects their own Google account in Avely's Settings, Avely requests exactly three permissions. Each is used only for the purposes listed here.
- Send email on your behalf (gmail.send) : used only when you click "Send" on a message you wrote inside Avely (a candidate email or a questionnaire link). Avely does not request any permission to read Gmail, so it cannot see, search or store any message in your mailbox.
- See, edit, share and permanently delete calendars (calendar) : used only to: create, update or cancel the single calendar event for an interview you schedule, reschedule or cancel in Avely (Google then sends the invitations to the attendees you chose); check whether you are free or busy at a proposed interview time, for which Avely receives only busy time ranges. Never the title, attendees or location of your other events; and show your next five upcoming events (title, time, location and meeting link) to you on your own Avely dashboard. Apart from that dashboard view, Avely does not read, change or delete any event it did not itself create.
- See your primary Google Account email address (userinfo.email) : used to show you which Google account is connected, and to confirm that an interview's calendar event still belongs to the Google account that created it.
Google user data: what Avely stores
Stored: your Google access and refresh tokens, in encrypted form; your Google account email address; the permissions you granted and when you connected; and, for interview events that Avely created, the event's identifier and its Google Meet link.
Not stored: your upcoming events, your free/busy information, and any Gmail content. These are used at the moment of your request and then discarded. (When you send an email from Avely, Avely keeps a record of that message, its subject and a short preview, in the candidate's history; that is the message you wrote in Avely, not data read from Gmail.)
Google user data: how it is shared or disclosed
Avely does not sell Google user data, does not use it for advertising, and does not use it to train AI models. It is disclosed only in these cases:
- Google : to carry out the actions described above.
- Service providers that operate Avely for us, only to provide the service: Vercel (application hosting) processes the data in memory while handling your request; Supabase (database hosting) stores the encrypted tokens, your Google account email address and the event identifiers and meeting links listed above, including in its backups; Sentry (error monitoring) receives technical diagnostics only. Avely removes tokens, email addresses, request contents and Google Calendar content and identifiers before anything is sent to it.
- Other staff users in your own company's Avely account, only as far as a feature needs it: a colleague who reschedules or cancels an interview that you organized acts through your connected calendar, and can see whether you are free or busy at the proposed time (time ranges only, no event details); the meeting link of an interview is visible to colleagues who have access to that job.
- Legal requirements : where disclosure is required by applicable law or binding legal process.
Google user data is never disclosed to other companies that use Avely.
Google user data: how Avely protects it
- All data is transmitted over encrypted connections (HTTPS/TLS).
- Before a Google token is stored, Avely's server encrypts it (AES-256-GCM) with a key that is kept outside the database, and the database is configured to refuse a token that is not in that encrypted form. The tokens are decrypted only on the server, when needed. Our database provider separately encrypts stored data at rest. This does not protect against a compromise of Avely's own server environment, which must hold the key in order to use the tokens.
- The tokens cannot be read or written from the browser. They are used on Avely's server only, to carry out the features described above, including on your behalf when a colleague on your team reschedules or cancels an interview that you organized.
- Each company's data is separated from every other company's by database access rules, and before using a token Avely's server confirms that its owner is an active staff member of the same company.
- Avely's diagnostic logging is designed to exclude tokens and Google content.
Disconnecting your Google account
You can disconnect your Google account at any time from Settings. This immediately and permanently deletes both the tokens and the connection record from Avely's live systems, and then asks Google to revoke Avely's access. If Google can't confirm that, Avely tells you, and you can also remove Avely from the third-party access list in your Google Account's security settings. Copies held in our database provider's backups age out on the provider's own schedule. Events that Avely already created on your calendar stay on your calendar.
Job applications, shared links and abuse protection
When someone applies to a job through a careers page, or opens a shared candidate or questionnaire link, Avely records the request's IP address for a short time to limit automated abuse. These records are deleted automatically within 24 hours. If an address submits several applications in a short period, the form may ask for a one-time verification provided by Cloudflare Turnstile; that check runs in the browser and shares technical information about the browser and connection with Cloudflare. It is not shown for ordinary submissions. Shared candidate links and questionnaire links stop working 30 days after they are created.
Limited Use disclosure
Avely's use and transfer of information received from Google APIs adheres to the
Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, do not sell it, do not allow humans to read it except as necessary for security, legal compliance, or with your explicit consent, and do not transfer it to anyone except as described under "Google user data: how it is shared or disclosed" above.
Microsoft (Outlook) connection
Avely also supports connecting a Microsoft/Outlook account instead of Google, for the same purposes (sending candidate email, calendar scheduling and availability). For Microsoft, Avely additionally requests permission to read the connected mailbox (Mail.Read). It is used only to show, in a candidate's Communications tab, the correspondence between that staff user and that candidate's email address. Avely is designed for one connected provider per staff user. Microsoft tokens are stored and protected in the same way as Google tokens. Avely can only disconnect a Microsoft account on its own side: Microsoft may keep listing Avely among your allowed apps until you remove it in your Microsoft account's app permissions.
Avely Sourcing browser extension
The Avely Sourcing extension (Chrome Web Store) lets a staff user add a candidate to their company's Avely account from a side panel in the browser. It does not read the web pages you visit, your browsing history or your tabs: it only sends what the staff user types, pastes or attaches in the panel (the candidate's name, contact details, current role, salary details, notice period, tags, a note and an optional CV file) to Avely at app.avely.io, where it is handled like any candidate added in Avely (see "Candidate and contact data" below). On the staff user's own device, the extension keeps the personal access token they created in Avely and a short list of their company's open jobs, in the browser's extension storage. The token can be revoked at any time in Avely, and removing the extension deletes what it kept on the device. The extension contains no advertising or analytics, and its data is not sold or shared with anyone else.
Candidate and contact data
Staff users add candidate information (name, contact details, CV, application history, notes) to Avely as part of running their hiring process. This data belongs to and is controlled by the company using Avely, not by Avely itself. We act as a data processor. Candidates should direct any request about their personal data to the specific company they applied to.
AI features
Some Avely features use artificial intelligence to help staff users: reading a CV to fill in a candidate profile, finding the parts of a CV that match a job's requirements, suggesting how well a candidate fits a job (with the CV passages each suggestion is based on), and answering questions in the Copilot assistant. For this, Avely sends the information the feature needs, such as a CV, a job description or the question asked, to Anthropic, which provides the AI model. Anthropic processes it only to return the result to Avely and does not use it to train its models. The results are stored in the company's Avely account. AI results can be wrong and are suggestions for a person to review: Avely never rejects a candidate, moves a candidate to another stage or sends a message on its own. Every hiring decision is made by the company's staff. When a recruiter searches for candidates outside their own database, Avely sends the search criteria to a third-party provider of public professional profile data, which returns public profile information (such as name, current and past roles, and a profile link). Profiles a recruiter adds are stored in that company's Avely account and are deleted with it.
Payments
Paid subscriptions and credit packs are paid through Stripe, our payment provider. Card details are entered on Stripe's secure payment page and go directly to Stripe: Avely never receives or stores card numbers. Stripe keeps the billing name, address, tax number and email a company enters, and its payment records, under its own
privacy policy. Avely keeps the company's Stripe customer and subscription identifiers, its number of seats, the subscription status and payment dates, and a history of billing changes, to provide the service. Avely emails a company's Admins about the end of its free trial.
Support chat
When you open Help & support in the app, Avely uses Crisp to run the support chat. Crisp receives your name, sign-in email, company name and internal account identifiers, the messages you send, and technical details from your browser (such as approximate location and browser type). No candidate data is shared with Crisp. The chat is loaded only when you open it, and it is cleared from your browser when you log out. Crisp keeps support conversations under its own retention rules; see its
privacy policy.
Data retention
Data is retained for as long as the company's Avely account is active. When a company closes its account, its data is deleted 30 days after the request, except billing records our payment provider must keep by law, and a record that the deletion took place (dates and counts only, with no personal details). Database backups that still contain the data expire within 30 days after that. A staff user's Google or Microsoft connection and its tokens are deleted from Avely's live systems immediately on disconnect, and are not retained there afterward for any purpose; copies in database backups age out on the database provider's schedule. Separately, a short non-secret record of that event (the member, the connected account's email address, when it happened, and whether the provider confirmed the revocation) is kept for 90 days for security auditing, or until the company is deleted, whichever comes first; a daily automated job then deletes it. Some of our service providers keep their own records for a limited time under their own retention rules: Resend (the emails Avely sends and receives), Anthropic (AI requests), our candidate search data provider (search requests), Crisp (support chat conversations), Google and Microsoft (activity of a connected account), and Stripe (billing). When a company is deleted, Avely revokes its Google connections and removes its Microsoft connections, cancels anything that could still charge in Stripe, and removes the saved payment methods; invoices stay with Stripe as the record holder for accounting. Uploaded files, such as CVs, are also copied each day to a separate encrypted backup storage provider, so they can be recovered if lost. A deleted file is removed from that copy within 48 hours.
Contact
Questions about this policy or how your data is handled can be sent to
support@avely.io.