Privacy Policy

The short version

Celer collects the information it needs to help your team prepare, send and track job applications, and uses it only for that.
We don't sell your information, we don't use it for advertising, and we don't use it to decide anyone's creditworthiness.
AI features send the text they need to OpenAI. Other providers, such as Google, Telegram and our payment providers, get only what their part of the service needs.
The extension reads job pages and application forms when you use it. While a Profile ID is selected, it records what you click and type on the pages you open, on any site, as application activity. This is how your team counts and checks each application, because bids are paid per application. The extension shows a notice about it after you sign in. It never records passwords, payment card or bank details, one-time codes or hidden fields. You can pause recording in the extension; while it is paused, nothing is recorded and your bids are not counted.
Celer emails you about your account, your plan and your support messages, and sends Celer news, which you can turn off in Settings or with the link in any news email. Our emails may show Celer's logo, loaded from Celer's website: the same picture for everyone, never used to see who opened an email.
You can ask for a copy of your information, ask us to correct it, or ask us to delete your account at support@celerllc.org.

Who we are

Celer is run by Celer LLC ("Celer", "we", "us"). This policy covers the Celer website at celerllc.org, the services behind it, and the Celer extension for Google Chrome. It explains what information we collect, why, who we share it with, how long we keep it and the choices you have.

If you have a question or a request about your information, email us at support@celerllc.org.

What Celer does

Celer is a workspace for teams that apply for jobs on behalf of the people they represent. A member sets up profiles (each one a Profile ID: the person the team applies as), collects job links and runs the team. Leaders and bidders are hired by members and apply on their profiles. Celer writes a tailored resume and cover letter for each job, the extension helps fill in and send each application, and Celer records every application for the team.

The Celer extension has a single purpose: to help prepare and submit job applications and to track them for your team. Everything it does, and everything it collects, serves that purpose. The website also has GitHub tools for finding and emailing software developers, which only the accounts we give them to can use; the extension has no part in them.

Celer's AI features work with text only: they write resumes, cover letters, answers to application questions and email replies. They never create or edit images.

Information we collect

We collect the information you give us, the information the extension reads while you use it, and information from the services you choose to connect.

Your account

Your full name, email address and role, the members you work for, and when your account was created.
If you sign in with Google: your Google account ID, email address and name. For sign-in, Celer asks Google only for your basic profile and email address.
If you set a password or an emergency sign-in code: only a one-way hash of it, never the password or code itself.
Whether your email address is confirmed, and when: you confirm it by typing back a code we email to it, or Google confirms it when you sign in with Google using that same address.
Your settings (for example AI models, resume file types and Autofill choices), your progress through guided tours, and when you last signed in or used Celer.

Profiles and application details

For each profile, the details your team enters so applications can be filled in: name, preferred and legal name, email address, phone number, street address, city, state, zip code and country, LinkedIn and GitHub links, work authorization, last company and role (older profiles only), education, salary expectation, and how the person heard about jobs. Also the profile's work history and the Google Doc used as its resume template. Where an administrator has turned on the new Profile details form, also the person's time zone, portfolio and website links, whether they need visa sponsorship and their citizenship, the countries they can work in, their security clearance and its status, whether they are willing to take a drug test, their notice period and start date, whether they would relocate or meet in person, their work preference, and the languages they speak.

Job-site passwords. You can save the password a profile uses to sign in to job sites, so the extension's Copy password button can copy it. It is encrypted in our database. It can be seen by the people on your team who work with that profile, and it is never sent to an AI service.

Self-identification answers. Job applications often ask voluntary questions about gender, race or ethnicity, veteran status and disability. On JazzHR, Autofill answers them with the answers saved on the profile (see below), and with preset answers where the profile has no saved answer to a question. On other job boards, Autofill answers them with preset answers. Neither the saved nor the preset answers are ever sent to an AI service. If an employer asks such a question among its own questions, Autofill may send that question and its options to OpenAI like any other question, and fill in the answer OpenAI picks. Whoever chooses them, the answers go into the employer's form and can appear in your application activity.

Self-identification answers saved on a profile. Where an administrator has turned on the new Profile details form, the member who owns a US or Canada profile can choose to save that person's answers to these voluntary questions, and to questions about whether they identify as LGBTQ+, their birth year, and whether they need accommodations during hiring. Every question starts at Decline to answer, and an answer other than a decline is saved only after the member confirms that the person agreed. The answers are encrypted. On the Celer website only that member can see and change them, and administrators see only whether answers are saved. Everyone who uses the profile in the Celer extension — that member and the leaders and bidders who work on the profile — can see them in the extension's profile details, so they can copy them into application forms; the extension does not save them. They are used only to fill in job application forms for that profile, so they also travel with that profile's other application details to the Celer extension used to apply for its jobs, including a leader's or bidder's. They are never sent to an AI service. Autofill fills them in on JazzHR, as described above; on other job boards it still uses preset answers. They are removed when the member removes them, when the profile's details are deleted, when the profile moves to another member, and when the profile's region is saved as anything other than US or Canada on the Profiles page. An encrypted copy can stay in our disaster-recovery backup until it is cleaned up; ask us and we will remove it from the backup too.

Jobs, resumes and history

The job links you add, share or collect, and what Celer reads from each posting: title, company, location, salary range and the job description.
For each profile: which jobs were sent to it, and when they were opened, downloaded and applied for, and by whom.
The resumes and cover letters Celer writes, the Google Docs and files made from them, and your prompts.
Job History and Bid History, including the application activity described below.

What the extension reads on web pages

The extension works on the pages you open in Chrome. It reads them to do what you ask:

Job descriptions and page text. When you build a resume, copy a prompt, get a page's text or check a job, the extension reads the job page's text. When Celer prepares resumes for your Job Links, it may open the job page in a tab, or load it using your browser's sign-in to that site.
Application forms. When Autofill runs on a supported job board, it reads the form's questions and options, then fills in the answers, the profile's details, the resume and the cover letter.
Verification codes. After you apply, the extension shows the code or link a job site emailed to the profile's connected mailbox.
Link Scraper. For the members we give the Link Scraper to, the extension opens the job boards it supports in your browser, where you are signed in, and collects the job postings it finds there (each one's title, company, company website and logo, when it was posted, and its link) into Scraped Links, from where you can move them on to your team's job lists. It runs only when you start it.
Highlight words. The extension highlights your chosen words on pages. This happens in your browser; no page text is sent anywhere for it.
ChatGPT. In ChatGPT mode, the extension types the prompt (the job description and the profile's work history) into your own ChatGPT tab, and reads ChatGPT's answer from the page, from what the page copies, or from your ChatGPT conversation. On chatgpt.com it watches what the page copies only to pick up that answer.
Profile details. The panel shows the selected profile's details, work history, education and saved self-identification answers to the people using the profile, and keeps the work history, education and self-identification answers only while it is open.
Clipboard. The extension copies what you ask it to, such as profile details, codes, passwords and prompts. It reads the clipboard only to take a resume answer that you or ChatGPT copied, and to clear a copied password. It removes a copied password from the clipboard, if it is still there, after about 30 seconds, but only once you are back in the Celer panel: until you return to the panel, the password stays on the clipboard.
Page control. To fill some forms, including forms in background tabs, the extension uses Chrome's debugger permission to type, click and scroll in that tab as you would. Chrome shows a notice while it does. The extension does not read your network traffic, and nothing it reads this way leaves your browser.

Application activity

Why it is recorded. Recording is how your team counts and checks each application: bids are paid per application, so each one is counted from this record, and the record shows what was done on it. That is why recording is part of using the extension.

Pausing recording. You can pause recording in the extension, with the pause button beside the selected profile. While it is paused, nothing is recorded and your bids are not counted, and the extension's panel says so. The pause ends when you resume, sign out or restart the browser, and it can end sooner, for example when the extension is updated.

The notice in the extension. After you sign in, the extension shows a notice, What Celer records, that says what it records, what it never records, that you can pause it, and how to stop. Got it closes it. It is a notice, not a choice: nothing waits on it, and recording works the same whether or not you have closed it. Another account signed in on the same browser sees it again.

While a Profile ID is selected in the extension, it records what happens on the web pages you open, on any website (not only job sites), so your team can see each application in Bid History:

the address and title of each page;
the buttons and links clicked, and when;
the values typed or chosen in form fields, with each field's label, including what Autofill fills in, and the names of files you upload;
when a resume is uploaded and when the application is submitted.

Never recorded: passwords; payment card numbers, security codes (CVV or CVC) and expiry dates; bank details such as IBAN, routing and account numbers; social security numbers, PINs and one-time codes; hidden fields; and rich-text message boxes outside a form, such as an email or chat composer. The extension recognizes these fields by how the page marks and labels them, and leaves each one out entirely, its label too. Nothing at all is recorded on payment sites (Stripe, PayPal, Braintree, Adyen, Square and Checkout.com), on ChatGPT or on the Celer website, or while no Profile ID is selected (for example after you sign out of the extension) or recording is paused.

The extension sends this record to Celer. The people on your team who see Bid History see it there, as What your team can see describes. It is kept as How long we keep it describes, with a copy in the job's Bid History.

Other sites too. Recording is not limited to job sites. While a Profile ID is selected, what you click, type and upload on any other site you use is recorded in the same way, apart from the fields and sites above: a search or a message typed into an ordinary form field, for example. To stop recording, sign out of the extension. To keep a site out of the record, pause recording or sign out before you use it. While recording is paused, your bids are not counted.

AI requests

When you use an AI feature, Celer sends the text that feature needs to OpenAI, and keeps a log of the request and the answer (see How long we keep it). What is sent:

Resumes and cover letters: the profile's prompt and work history, and the job description and link.
Autofill: the form's questions and options, the profile's application details, the resume and the job description. The application details include what the new Profile details form holds: name, location and time zone, phone and links, work authorization, visa sponsorship and citizenship, the countries the person can work in, security clearance and its status, willingness to take a drug test, notice period and start date, whether they would relocate or meet in person, work preference, salary expectation and languages. Never sent: the profile's job-site passwords and its self-identification answers, saved or preset. The questions can include an employer's own questions about gender, race or ethnicity, veteran status or disability (see Self-identification answers).
Chat: your question, with the job's resume, cover letter and description.
Job postings: a posting's text, to clean it up, to compare it with a resume, or to check collected jobs against your rules.
Mail: one email and its thread, when you ask for an AI-drafted reply.
Profile from resume: the text and links of a resume you upload on the Profiles page, to fill in a new profile or the empty parts of one you already have. The file itself isn't kept.

If you add your own OpenAI API key, requests for your profiles use your key and your OpenAI account. Otherwise they use Celer's key and are paid from your credit.

The log keeps the text that was sent and the answer, for 30 days. Only Celer administrators can open it, and they open a request's text only when you agree to it for that request (for example, when you ask us to look into a problem with it), when it is needed for security, such as investigating abuse, or when the law requires it. Otherwise they see only a request's details without its text: which feature, model and key it used, when it ran, how large it was and whether it worked.

OpenAI also keeps each request and its answer in the OpenAI account whose key paid for it — Celer's own account, or yours if you added your own OpenAI key — where it shows on that account's Logs page. OpenAI says it keeps these for 30 days. The rule above applies to the copies in Celer's account too: our staff open their text only when you agree, for security or when the law requires it.

Connected mailboxes and verification codes

Accounts with Mail can connect a Gmail or Outlook mailbox to a profile. Celer then asks Google or Microsoft for permission to read, organize and send mail in that mailbox, and uses it to:

find interview emails, and keep a short summary of each one (sender, subject, a short excerpt, date and mailbox) for the Interview Inbox;
show a whole email when you open it, without storing its body;
mark an email as read when you open it, star or flag it when you ask, and send the replies you write;
find a sign-in or verification code a job site has just sent, and show it to you and your team in the extension and in Mail Search. Codes are not stored in our database;
let the leaders and bidders working on a profile search its mailbox and read, without changing anything, any email that reached it in the last 10 minutes (Mail Search), such as a code or a note asking to finish an application;
send alerts about new interview emails (sender, subject and a short excerpt) to the Telegram chats linked by the member, by the member's leaders and by the bidder who holds the profile, for those who switch these alerts on.

The Interview Inbox keeps summaries for the recent period your mail filter sets, 72 hours unless you change it: older ones are removed each time it updates, and those of a mailbox you remove are deleted with your account or when you ask us.

Google Docs and Drive

Celer creates each resume as a Google Doc. A member's resume templates come from their own Google Drive: connect it, then pick a Doc or build one from a design. Celer creates those resumes in a "Celer resumes" folder in your Drive, and it can reach only the files it creates and the files you pick. Celer's own Google account creates resumes for profiles that have no member owner (their templates are built from a design) and, until its template is chosen again, for an older profile whose template is still a Doc link. It keeps the resumes it created before. When you pick a Doc, Google's file picker opens in your browser. When you build a template from a design, Celer's own Google account makes a temporary copy of the design, fills it in with the profile's details, and deletes that copy once the template is in your Drive.

Telegram, Notion and GitHub

Telegram: if you link a chat, we store the chat's ID, type and title and your Telegram user ID and username, and send the alerts you switch on. Alerts can include an interview email's sender, subject and a short excerpt, meeting reminders, jobs shared with you, and your notifications. Alerts about a member's interview emails also go to the chats that member's leaders and bidders link, and alerts about support chat messages go to our staff's chats (see Support).
Notion: if you connect Notion, we store the connection, your Notion workspace and user details (name, email address and picture), and the meeting boards and availability you set, to send meeting reminders.
GitHub tools (website only): accounts that have them can use the website's GitHub pages to find software developers on GitHub and their contact emails, save GitHub access tokens, and send outreach email from email accounts they add. We store what they find, the emails sent and the replies. The extension has no part in them.

Support, notifications and emails

The messages you send to and receive from our support chat. When you write, our staff get an alert with your name, email address and the start of your message, including in the Telegram chats they link.
The notifications shown to you in Celer.
A daily email to each person who sent bids, with their own bid totals for each profile, sent from Celer's Google account.
The emails Celer sends you from its own addresses, described just below.

Emails from Celer

Celer sends emails from its own addresses at celerllc.org through our email host, Hostinger. They go to your account's email address. To write them, Celer uses only your account details: your name, email address and role, and for an email about your plan, its name, how many Profile IDs it has and when it ends. Nothing from your connected mailboxes, your Google Drive or the extension goes into them.

Emails about your account: a welcome email after you first sign in; an email when your plan starts or renews, and a reminder a few days before a plan that won't renew by itself ends; a note that your message reached us when you write to our support chat; and a code when you ask for one to confirm your email address, for example to reset a forgotten emergency sign-in code. They come with your account and have no off switch.
Celer news: emails about Celer itself, such as new features and changes. You get them unless you turn them off: every news email has a link to unsubscribe, and Settings has a Celer news switch under Emails. Turning it off stops only Celer news.
Celer's logo, no tracking: our emails may show Celer's logo, loaded from Celer's website. It is the same picture for everyone, with nothing in it that identifies you. Like any picture on the web, loading it sends your IP address to our web server, which keeps no log of those requests, and we don't use it to see who opened an email. Our emails have no tracked links, so we don't know what you click in them.
Do-not-email list: when you unsubscribe from Celer news, your address goes on our do-not-email list for Celer news. When emails to an address bounce because it doesn't exist, or our staff add it (for example when someone asks us to stop), it goes on the list for every email. The list keeps the address, why it is there and when it was added (with a short note, if our staff add one), and it stays after an account is deleted, so an address that asked not to be emailed isn't emailed again.
Codes to confirm your email: we keep only a one-way hash of the code, never the code itself, and delete it once it is used or within a day. To limit how many codes can be asked for, we keep the times you asked for one for a day too.
Email log: for each email we send, who it went to, its subject and text, which Celer address sent it, and whether it was sent or why it wasn't, kept for 90 days. For an email with a code, the log keeps only its subject, never the code: its text is removed as soon as it is sent, or can't be.

Payments and credit

Celer plans are paid from prepaid credit. You add credit with cryptocurrency through our payment providers, NOWPayments or ATLOS, or by a request that an administrator confirms. You pay the provider directly; we never receive your wallet keys or card details. We keep the amount, currency, method and status of each payment, any reference you enter, the provider's payment and transaction IDs, your credit balance and its history, your plan (its Profile IDs, length, discount and the price paid), credit returned when you switch plans, AI use paid from credit, and referral rewards. The extension takes no part in paying for Celer. It never records card numbers, security codes or expiry dates, or anything on the payment sites named under Application activity, but while a Profile ID is selected it can record a payment form's other fields on another site, such as the name or billing address.

Usage and technical information

When you last signed in and used Celer, and the counts behind your team's dashboard.
Server logs, which record errors and, for some sign-in and payment requests, the IP address.
The extension's version number, sent with each request so Celer can handle older versions.
IP addresses and accounts are checked for a short time to limit repeated sign-in attempts and other abuse.

Cookies and browser storage

The website uses one cookie to keep you signed in. The website and the extension also keep settings in your browser, such as your theme and filters, and an invite code until you sign up. We use no advertising or analytics cookies or trackers. Two features load a script from a provider when you use them: Google's file picker, when you pick a Google Doc, and the ATLOS payment window on the Credits page.

Information about other people

Some of the information in Celer is about people who don't use it:

The people profiles represent. Members enter their details, and must have their permission to do so.
People who email a connected mailbox: their name, email address, subject and a short excerpt, in the Interview Inbox.
Developers on GitHub: accounts with the GitHub tools can collect public GitHub profile information, such as name, location, company and the email address shown on public commits, to contact developers.
People who apply for a job at Celer LLC or contact us through celerllc.org: the details and resume they send.

Anyone who wants their information removed can email support@celerllc.org.

How we use information

We use information only to provide Celer:

to prepare and submit job applications: write resumes and cover letters, fill in forms, find verification codes and answer application questions;
to let teams organize and track their work: job links, history, counts, dashboards, alerts and daily summaries;
to count and check each application from its application activity, because bids are paid per application;
to sign you in, keep accounts secure, prevent abuse and fix problems — including emailing you a code, when you ask for one, to confirm your email address;
to bill for plans and AI use, and to give free credit and referral rewards once per person;
to answer support requests and send the messages you switch on;
to email you about your account, your plan and your support messages, and to send Celer news, which you can turn off;
to run the website's GitHub tools for the accounts that have them;
to comply with the law.

We do not sell personal information, and we do not use it or share it for advertising. We do not use or transfer what the extension collects for any purpose other than its single purpose, and the website's GitHub tools use none of it. We do not use it to determine creditworthiness or for lending. We do not use it to train AI models.

What your team can see

Members see everything for their own profiles, including profile details and job-site passwords, job links, resumes, history and counts, and the activity of the leaders and bidders they hire.
Leaders and bidders see what they need to work for a member: the profiles they work on, including the details, work history and job-site passwords used to apply (and, in the extension's profile details, saved self-identification answers), the team's job links, verification codes for those profiles, any email that reached those profiles' mailboxes in the last 10 minutes (Mail Search), alerts about those profiles' interview emails in their own Telegram chats, and the team's history and counts as their role allows.
Celer administrators (our staff) can see the information needed to run Celer, such as accounts, profiles, plans, payments, usage, the support chat and the AI request log, and use it only to run the service, support you and fix problems. They open the text of an AI request only as described under AI requests. Of saved self-identification answers, they see only whether a profile has any.

How long we keep it

Profiles, job links and postings, resumes, history and the support chat are kept until you or your team delete them, or until the account is deleted. Some information is kept for a shorter time:

AI request logs: 30 days. OpenAI's copies of the requests: 30 days, as OpenAI says.
Application activity: the detailed record is deleted 30 days after its last event; a copy stays with the job's Bid History.
Interview Inbox summaries: your mail filter's period, 72 hours unless you change it; older ones are removed each time the inbox updates.
Verification codes: not stored in our database.
Notifications: 7 days.
Email log: 90 days.
Codes to confirm your email: deleted once used, or within a day; the times codes were asked for, one day.
Do-not-email list: until you subscribe to Celer news again, or our staff remove the address.
Jobs an administrator offers to share with you: 7 days, unless you accept them.
Link Scraper links: 90 days.
Sign-in: a website or extension sign-in lasts up to 30 days.
Wrong emergency sign-in codes for an email with no account: a one-way hash of the email is kept for one year after the last try, to stop guessing.
In the extension: your sign-in until you sign out; profile details, codes, passwords and job details until you close the browser or sign out; cached prompts and highlight words for up to an hour. Resume files you download stay in your Downloads folder.
Server logs: kept without a fixed period.
Job applications to Celer LLC and messages sent through our contact form, including any resume attached: kept without a fixed period. Ask us at support@celerllc.org and we will delete them.

When an account is deleted

Accounts are deleted by a Celer administrator: ask us at support@celerllc.org or in the support chat. Deleting an account signs it out everywhere and removes its profiles and their details (including job-site passwords), job links and postings, resume records, Job and Bid History, application activity, connected mailboxes and their summaries, its Google Drive, Telegram and Notion connections, prompts, GitHub tokens and email accounts, notifications and support chat.

Some records are kept after an account is deleted:

payment, credit and AI-use records, which we need for accounting;
daily bid counts used in team statistics;
a one-way hash of your email address and Google account ID, so free credit is given only once per person;
referral records, marked void;
AI request logs, and OpenAI's copies of the requests, until their 30 days end;
the email log, until its 90 days end;
codes to confirm your email, and the times they were asked for, until their day ends;
your address on our do-not-email list, if it is there (you unsubscribed from Celer news, or emails to it bounced), so it isn't emailed again;
information collected with the GitHub tools;
the Notion meeting boards, availability, unavailable times and meeting reminders you set, until you ask us to delete them;
Google Docs already created: those in your Drive are yours to delete, and we will delete those in Celer's Google account if you ask;
our disaster-recovery backup, which can keep deleted information until it is cleaned up. Ask us and we will remove it from the backup too.

To withdraw Celer's access at Google, Microsoft or Notion as well, remove it in that account's settings.

How we protect it

Connections to the website, its API and the extension use HTTPS.
Sign-in passwords and emergency codes are stored only as one-way hashes. Extension sign-ins are stored as hashes and expire.
Mailbox, Google Drive, Notion and GitHub connections, the passwords of email accounts you add, and OpenAI API keys you add are encrypted in our database. Only a short hint of a key is ever shown.
History backups you download are encrypted.
Self-identification answers saved on a profile are encrypted in our database.
Job-site passwords saved on a profile are encrypted in our database.
Roles decide who sees what, and sign-in and other sensitive requests are rate-limited.

Other information, including profile details, is protected by these controls but is not separately encrypted in our database. No system is completely secure. If you think your account has been misused, tell us at support@celerllc.org.

Your choices and rights

See and export: most of your information is visible in Celer. Members can download their Job and Bid History as an encrypted backup, which can only be restored into Celer, not opened or read on its own. For a copy you can read, of that or of anything else, ask us at support@celerllc.org.
Correct: edit profiles and settings in Celer, or ask us.
Delete: delete job links, postings, prompts and profiles in Celer, or ask us to delete your account.
Disconnect: remove a mailbox on the Mail page, disconnect Google Drive in Settings (this also withdraws Celer's access at Google, unless that Google account is still connected to Celer another way, such as a mailbox), remove Telegram chats and your Notion connection, and remove your emergency code or OpenAI keys in Settings. You can also withdraw Celer's access in your Google, Microsoft or Notion account settings at any time.
Emails: turn Celer news off or on in Settings under Emails, or use the unsubscribe link in any news email. Emails about your account, your plan and your support messages have no off switch.
The extension: signing out stops application activity recording, and clears its saved sign-in and most of what it keeps in your browser. You can also pause recording in the extension. While it is paused, nothing is recorded and your bids are not counted, because recording is how your team counts each application. The pause ends when you resume, sign out or restart the browser. Removing the extension from Chrome deletes everything it stored there.

Depending on where you live, you may have the right to access, correct or delete your information, to receive a copy of it, to object to or restrict how we use it, and to complain to your data protection authority. To use these rights, email us at support@celerllc.org. We aim to answer within 30 days, and we will not treat you differently for using them.

Children

Celer is not meant for anyone under 16, and we do not knowingly collect information from children under 16. If you believe a child has given us information, contact us and we will delete it.

International transfers

Celer LLC and our service providers may store and process information in the United States and in other countries, whose data protection laws may differ from those where you live. Wherever it is processed, we protect it as this policy describes.

Google user data

This section brings together what Celer does with the information it receives through Google's APIs: Google Sign-In, Google Drive and Docs, and Gmail. Celer asks Google only for what the features you use need, and only when you use them.

What we access

Google Sign-In: your Google account ID, name and email address, to create your account and sign you in, and to give free credit only once per person and no invite reward for inviting yourself.
Google Drive and Docs, if you connect your Drive: the email address and Google account ID of the Google account you connect, the files Celer creates and the Google Docs you pick with Google's file picker. Celer uses the Docs you pick as resume templates and creates the resumes made from them in a "Celer resumes" folder in your Drive. It cannot see your other files.
Gmail, for each mailbox you connect to a profile: Celer reads the mailbox's email, marks an email as read when you open it, stars or flags it when you ask, and sends the replies you write, as described under Connected mailboxes and verification codes.

Separately, Celer uses its own Google account, not yours, to create resumes as Google Docs when a profile's template is not in its owner's Drive (a profile with no member owner, whose template is built from a design, or an older profile whose template is still a Doc link), to keep the resumes it created before, to make the temporary copy of a design described under Google Docs and Drive, and to send Celer's daily summary emails. It no longer reads Google Sheets.

How we use it

Only to provide the features you use it with: signing you in; creating, opening, downloading and attaching your resumes; and the Interview Inbox, verification codes, Mail Search and the replies you send. The email address Google Sign-In gives us is also your Celer account's address, where Celer sends the emails described under Emails from Celer; nothing from your Gmail mailboxes or your Google Drive goes into them. A one-way hash of your Google account ID also makes sure free credit goes only once per person and nobody earns an invite reward for inviting themselves (see When an account is deleted). We do not sell it, and we do not use it for advertising or for anything else.

We pass it on only to provide those features: to the employers and job boards you apply to, the resume files you or Autofill attach; to OpenAI, an email and its thread when you ask for AI help with it (see AI requests); to the Telegram chats you or your team linked, a short alert about a new interview email; and to your team, as described under What your team can see. We may also disclose it when the law requires it.

How we store and protect it

Your Google Drive and mailbox connections are encrypted in our database, and every connection to Celer uses HTTPS. Celer keeps only what a feature needs: the Interview Inbox keeps a short summary of each interview email, an email you open is shown without being stored, and verification codes are not stored in our database. The one exception is an email you ask AI help with, which is kept with that AI request as described under AI requests. See also How we protect it.

How long we keep it and how to delete it

The Interview Inbox keeps summaries for your mail filter's period, 72 hours unless you change it: older ones are removed each time it updates, and those of a mailbox you remove are deleted with your account or when you ask us. The other periods are under How long we keep it. Remove a mailbox on the Mail page or disconnect Google Drive in Settings and Celer stops using it. Disconnecting Drive also withdraws Celer's access at Google, unless that Google account is still connected to Celer another way, for example as a mailbox; Settings tells you when it could not. You can withdraw Celer's access at any time in your Google Account's security settings. Resumes in your Drive are yours to keep or delete. To delete your account, ask us at support@celerllc.org; When an account is deleted lists what is removed and the few records we keep.

AI and images

Google Workspace APIs are not used to develop, improve, or train non-personalized AI and/or ML models, and neither is any information Celer receives from them.

Nothing Celer receives from Google is used to create or edit images, including AI-generated non-consensual intimate imagery (NCII), and Celer's AI features never create or edit images.

Chrome Web Store and Google API data

The Celer extension's use of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. The extension uses information only for its single purpose: to help prepare and submit job applications and track them for your team. The text of AI requests, which can include what the extension read from web pages, is read by our staff only as described under AI requests.

Celer's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Information from Google (your Google sign-in, Google Docs and Drive files, and the Gmail mailboxes you connect) is used only for the features you use it with: signing in, creating resumes, the Interview Inbox, replies and verification codes. It is passed on only to provide those features, for example to OpenAI when you ask for an AI-drafted reply, or to the Telegram chats you or your team linked for an interview alert. Your team sees it as described under What your team can see. Our staff do not read your email, except the text of an AI-drafted reply's request, and only as described under AI requests: when you agree to it, for security, or when the law requires it. We do not use it for advertising, and we do not use it to develop, improve or train generalized AI or machine-learning models. The email address from your Google sign-in is also where Celer sends you its emails (see Emails from Celer); no Gmail or Drive data goes into them. More in Google user data.

Changes to this policy

We may update this policy as Celer changes. We will post the new version on this page and change the date at the top. If a change is significant, we will also tell you in Celer.

Contact us

Celer LLC. Email support@celerllc.org with any question or request about your information. Signed-in users can also write to us in the support chat.