Privacy Policy

Last updated: August 1, 2026

Glever fills out job applications for you and, when you choose, drafts answers to application questions using AI. It comes in three forms — a Chrome extension, an iOS app for iPhone and iPad, and the web app at glever.co — all provided by Glever LLC (“we,” “us,” or “our”). This policy explains what data we collect, how we use it, who we share it with, and the choices you have. It covers all three, and we’ll call out anywhere they differ.

Information we collect

• Profile information you add — name, contact details, links (e.g. LinkedIn, portfolio), work and education history, and any answers you save for reuse across applications.
• Resume files you upload, and the text and structured details we extract from them to help autofill and draft answers.
• Voluntary self-identification answers — saved answers may include responses to a job application’s voluntary self-identification questions (such as gender, race/ethnicity, veteran, or disability status) if you choose to save them; we store these only to refill similar questions at your direction and never use them for any other purpose.
• Account information — when you sign in with Google, we receive your email address, name, and profile image to create and identify your account. When you use Sign in with Apple, we receive a unique Apple identifier and the email address you choose to share; if you pick Apple’s “Hide My Email,” we only ever see the private relay address, never your real one.
• Application activity — metadata about applications Glever fills out, such as company, job title, and application URL, so you can track them in your dashboard.
• In-progress application state — when you queue a job, we save a snapshot of the values Glever filled into that application so you can pick the run back up on another device and finish it.
• Billing information — if you subscribe to Premium, your subscription and payment method are handled by Stripe. We receive your subscription status but not your full card number.
• Basic usage data — things like AI feature calls and rate-limit counters, kept to operate quotas, prevent abuse, and keep the Service reliable.

How we use your information

• To fill out job application forms on supported sites, at your direction.
• To review and submit your ready queued applications on your behalf, when you’ve turned on Submit for me (see below).
• To draft AI-assisted answers to application questions when you use that feature.
• To sync your profile, resume, and saved answers across your devices.
• To operate your account, provide support, and process Premium subscriptions.
• To enforce plan limits, prevent abuse, and keep the Service secure and reliable.

Where your data is stored

Our servers are the source of truth for your profile, resume, and saved answers, and are what lets you sync across devices. The extension also keeps a copy locally in your browser, so autofill is fast and still works offline. It authenticates to our servers with a token you can revoke at any time by disconnecting your account. Removing the extension clears its local copy.

The iOS app stores only its access token and your user id in the iOS Keychain, plus small interface preferences (such as which tab you last had open) on the device. Your profile, resume, and saved answers are loaded from our servers as you use the app rather than kept in a local database. Signing out or deleting the app removes the token from the device. In every case, your account data stays on our servers until you request deletion, as described below.

Applying inside the iOS app

When you tap Autofill on a job, the iOS app opens the employer’s real application page in an in-app browser and runs the same autofill engine the extension uses. To do that, the app loads your profile, resume, and saved answers from our servers and hands them to the engine in memory for the duration of the session; the app doesn’t save them to your device. The page itself behaves like any web page you’d open in Safari — the employer and their application provider can see your visit and set their own cookies. Those cookies live in Glever’s own isolated app storage, are never shared with Safari or other apps, and are removed when you delete the app.

Unless you’ve turned on Submit for me (below), Glever never submits an application for you. You review the filled form, complete anything only you can do (such as a captcha), and tap the employer’s own submit button yourself, from your own device and network connection. We record only that a submission happened, along with the job metadata described above.

Submitting on your behalf (“Submit for me”)

Submit for me is an optional setting, off by default, that you can turn on or off from your dashboard’s Autofill Queue page. While it’s on, Glever personnel can open and view the contents of your filled applications — which can include your profile details, resume, answers to screening questions, and any voluntary self-identification disclosures the employer’s form asks for — solely in order to review each application and submit it to the employer on your behalf. We record the submission the same way as one you make yourself. Turning the setting off stops this access for future applications.

AI-assisted answers

When you ask Glever to draft an answer, the specific application question and the profile or resume context needed to answer it are sent to our server, which relays a purpose-built request to our AI provider, Anthropic, and returns the draft to you. We don’t send your entire profile for every request — just what’s relevant to the question. Anthropic processes this data to generate the response and, under our agreement with them, doesn’t use it to train their models.

Who we share data with

We share data with a small number of service providers, only as needed to run Glever:

• Anthropic — generates AI-drafted answers, as described above.
• Google — for sign-in and authentication.
• Apple — handles authentication when you use Sign in with Apple. We don’t send Apple your profile, resume, or application activity.
• Stripe — processes Premium subscription payments.
• Cloud infrastructure providers — host our database and web application.
• The job site you’re applying to — receives whatever information Glever enters into that application’s form, at your direction.

We don’t sell your personal information, and we don’t share it for advertising or marketing purposes.

Extension permissions

The extension only requests access to supported job application sites (currently Greenhouse, Lever, Ashby, Workable, and Rippling) so it can read and fill form fields on those pages, and to glever.co so it can sync with your account. It doesn’t run on, read, or collect data from any other site you visit.

What the iOS app doesn’t access

The Glever app asks for no device permissions at all. It doesn’t access your camera, photos, microphone, location, contacts, calendar, or health data, and it doesn’t send push notifications. When you upload a resume, iOS’s own file picker hands us only the single file you choose — Glever can’t browse the rest of your files.

The app contains no third-party analytics, advertising, or crash-reporting SDKs. We don’t track you across other companies’ apps or websites, we don’t use the advertising identifier, and we don’t build advertising profiles. The only server the app talks to is our own at glever.co.

Paying for Premium on iOS

Premium is sold by us, not through Apple’s in-app purchase system. Where the app offers an upgrade button, it opens a Stripe checkout page in a secure browser sheet; your card details go to Stripe and never pass through the app. Apple doesn’t receive your payment details from us, and we don’t receive them from Apple.

Data retention and your choices

• You can view, edit, or delete your profile, resume, and saved answers anytime in your dashboard or in the iOS app.
• You can disconnect the extension or remove it entirely, which revokes its access token and clears its local data.
• Signing out of the iOS app revokes that device’s access token on our servers and removes it from the device’s Keychain. Deleting the app removes everything it stored locally, including the in-app browser’s cookies.
• You can permanently delete your account from the dashboard, or from the account screen in the iOS app. This removes your profile, resume, saved answers, and application history, cancels any Premium subscription immediately, and can’t be undone. You can also email us at the address below if you’d rather we do it. We keep only limited records we’re required to (for example, billing records for tax or legal purposes) and the one item described next.

When you delete your account, we keep a one-way, irreversible identifier derived from your sign-in — not your email address, name, or any of your content, and not something we can turn back into your identity. Its only purpose is so that deleting an account and immediately creating a new one can’t be used to reset the one-time free AI application allowance. We discard it after 35 days — a deliberate cap on how long we hold even this anonymous identifier.

Security

Data is transmitted over encrypted connections (HTTPS). Access to our backend requires authentication, and the extension and iOS app talk to our servers using a revocable token rather than a static password — on iOS that token is held in the device Keychain, which is encrypted by iOS and unavailable until you first unlock the device after a restart. We apply rate limiting to AI features to reduce the impact of a compromised token. No method of storage or transmission is completely secure, so we can’t guarantee absolute security.

Children

Glever isn’t directed to children under 16, and we don’t knowingly collect their data.

Changes to this policy

We may update this policy as the Service changes. If we make a material change, we’ll update the “Last updated” date above.

Contact

Questions about this policy or your data? Email us at support@glever.co.