Privacy Policy

Seekrly ("we", "us", "our") is a product of ProteinSlice. It is a personal job-search manager: you track applications, recruiter contacts, interviews, follow-ups, notes and resumes, and you can optionally use Seekrly AI, our browser extension, AI apps you connect to your account, and an API for your own tools. This policy explains, in plain terms, exactly what data we collect, why we collect it, how we use and store it, who it is shared with, and the choices you have. We have written it to describe what the application actually does, nothing more.

We collect the following, and only the following:

• Account data: your name, email address, and (for password accounts) a bcrypt hash of your password when you register.
• Google sign-in data: if you choose "Sign in with Google", we receive your name, email address, and Google account identifier from Google to create and identify your account. Your name and email then become your account details, used like other account data (for example, shown to apps you connect; see section 7). We never receive your Google password.
• Profile data: optional details you add, such as headline, phone, location, work history, skills, links, and an uploaded resume file.
• Job-search data: applications, contacts, follow-ups, notes, and interview records you create. Contacts may include personal details of third parties (e.g. a recruiter's name and email) that you choose to enter.
• Companies: the companies in your job search. We create them from the company names on your applications and contacts, and you can add details (website, careers page, social links, industry, locations, a description) and private notes. Companies you suggest for the shared company directory are also kept as suggestions for our team to review (see section 10).
• Seekrly AI requests and answers: when you use an AI feature, the input you give it (for example a job description, form questions, or the resume you pick), the answer it returns, and a usage record (which feature, when, which model, and how much of your AI allowance it used). See "Seekrly AI" below.
• Connected apps and API keys: if you connect an AI app or create an API key, the app's name, the permissions you granted, and when it was used. API keys are stored only as hashes.
• Email-sending credentials: if you connect an account to send outreach, we store either (a) a Gmail OAuth refresh token, or (b) your custom SMTP server details and password. In both cases the secret is encrypted at rest (see "Google user data and Gmail access" and "Data storage and security" below).
• Outreach content: the subject and body of follow-up/outreach messages you compose (including drafts written with Seekrly AI), and the recipient address, so we can send them and show you a history.
• Support requests: if you contact us through the contact form, the browser extension, a connected AI app or the API, the name, email, topic, subject, and message (and, from the contact form, the page you were on). From the extension, an AI app or the API, the name and email are taken from your account.
• Usage and security data: basic server logs (IP address, timestamps, request paths) and temporary rate-limiting counters and one-time verification codes, retained briefly for security and abuse prevention.
• Activity records: a record of sign-ins, security events and changes to your data (for example "application updated"), with which device, extension, API key or connected app made it, the IP address, the approximate location derived from it, and the browser or app details. We use it to show you your account activity, to keep your account secure, and to remind you when you haven't used Seekrly for a while. See section 14 for how long it is kept.
• Session and device data: when you log in (on the website or through the browser extension), we record the device and session details needed to show you a list of active sessions in Settings and to let you remotely log out individual devices. This includes: IP addresses used during the session, operating system and version, browser name and version, screen resolution, device memory and CPU core count, device pixel ratio, preferred language, timezone, and whether the device is mobile. For the browser extension, we additionally collect the extension version, CPU architecture, and platform identifier. IP addresses are stored as a history so you can see where each session was accessed from.

We do not use advertising trackers or behavioural profiling, and we do not sell your data to anyone. Analytics loads only with your consent (see "Cookies and similar technologies").

• To provide, operate, and maintain the Service.
• To authenticate you (via password or Google sign-in) and keep your account secure.
• To track active login sessions and connected extension devices, so you can review and revoke access to individual devices from your account settings.
• To send transactional email you would expect: email verification codes, password reset codes, security notices, reminders you set, and a welcome message.
• To send the outreach messages you compose and send (or schedule to send), from your connected Gmail or SMTP account, to recipients you choose.
• To run the Seekrly AI features you ask for, the automatic ones you turn on, and the short AI note in report emails unless you turn it off.
• To let the browser extension, AI apps you connect, and your API keys work with your account, within the permissions you granted.
• To group your applications and contacts by company, suggest companies that may be saved twice, and fill in shared details from the company directory.
• To build the shared company directory from companies users suggest (see section 10). Behind the scenes we also count how many users track a company name that isn't in the directory yet, so our team can add it; only the count is used, never who tracks it.
• To enforce our Terms of Service and protect against abuse.

We do not use your data, your AI requests, or your AI answers to train AI models, and we do not use them for advertising.

Seekrly AI is an optional set of features on plans that include it. It only runs when you ask it to, or when you turn on an automatic feature yourself. The one exception is the short AI note in our report emails, on any plan that gets those reports: it is on by default and you can turn it off, as described under "Report emails" below.

What it does

• Job fit and job insights: scores how well a job matches your profile and breaks down a job post (requirements, pay, work mode, gaps to close).
• Resumes: reads a resume you upload into your profile or the resume builder, and suggests a tailored version for one job from your profile's facts.
• Messages: drafts cover letters, recruiter emails, follow-ups, thank-you notes and replies. A draft is only a suggestion: nothing is sent until you send it or schedule it.
• Interview prep: likely questions, answer outlines and topics to revise for an interview round.
• Reviews and strategy: feedback on your profile, a review of how your applications are going, and a job-search plan.
• Application-form answers: in the browser extension, suggests answers to the questions on an application form that autofill couldn't fill.

Automatic features (for example, a fit score for each new application, or interview prep when you schedule an interview) are off by default. You can turn them on or off in Settings → Preferences.

Report emails

If you had activity in the period, your weekly or monthly report email can include a short AI note. It does not use your AI credits. To stop it, turn off "Use AI in my report emails" in Settings → Report emails. When it is off, your data is not sent to an AI provider for these reports and you still get your numbers. The change applies from your next report: a report already being prepared may have been sent for processing. A period with no activity never uses AI. We keep each request and answer as the AI provider saw them, with personal details replaced by placeholders, for up to 400 days for troubleshooting and cost records, and delete them sooner if you delete your account.

Weekly and monthly reports send the following to the AI provider:

• Your numbers for the period and the one before: applications tracked, jobs applied to, applications moved to interviews, offers, interviews held, follow-ups sent and replies received, plus how many interviews and follow-ups are due in the next 7 days.
• How your applications went, for the period and the last 3 months: response and interview rates, typical time to a reply, stalled applications, follow-up totals, figures by job site and resume name, your most common job titles and locations, your latest applications (up to 10 for a weekly report, 20 for a monthly one) and up to 15 applications that reached an interview, each with job title, company, job site, status and resume name.
• A few details from your career profile: target roles, headline, years of experience, up to 15 skills, your last three jobs (title and employer) and preferred locations.

Reports do not send job descriptions, the contents of your resumes, your contacts, your messages, your expected salary or your own notes. Your name, email address, phone number and other personal details, including any in a resume name, are replaced with placeholders before the AI provider sees them.

What it uses

Each feature uses only what it needs for that request: the input you give it (such as a job description or form questions) and, where the feature needs it, your career profile, a resume you pick, or summaries of your applications, contacts and messages you saved in Seekrly. It never uses data from your Gmail account (see section 5).

How it is processed

• Your request is processed by our own AI service, which sends it to an AI model provider (see "Service providers") and returns the answer to you.
• Personal details are hidden first. Before anything reaches a model provider, we replace your name, email address, phone number, street address, postal code and profile links (and, where a feature doesn't need it, your city) with placeholders, along with any other email addresses, phone numbers and profile links in the text. We put the real values back into the answer before you see it. Uploaded files are turned into text and hidden the same way; the file itself is never sent to a provider.
• Our model providers process requests under their business API terms, which do not allow them to use your requests to train their models. They may keep requests for a limited time to detect abuse, as their terms allow.
• Text from other people (job posts, recruiter messages) is treated as data, not instructions, to protect against attempts to manipulate the AI.

What we keep

• AI history: your requests and answers appear in your AI history so you can reopen them. How long they stay visible there depends on your plan, and you can remove an entry at any time.
• Usage records: a record of each AI request (feature, time, model, and how much of your allowance it used) is kept for up to about 13 months for billing, support and abuse prevention, even if you remove it from your history.
• Troubleshooting: to fix problems with AI answers, we may keep a copy of a request as the model received it and its answer with that record. Only a small number of our team can see it, and only to support you, fix problems, or investigate abuse.

Accuracy and your control

AI answers can be incomplete or wrong. Check them before you rely on them, send them, or submit them to an employer. Seekrly AI does not make decisions about you: it suggests, and you decide. You can use every other part of Seekrly without it.

Google Workspace user data is used solely to provide the features requested by the user and is never used for advertising, profiling, or training generalized AI or machine learning models.

If you connect Gmail to send outreach, Seekrly uses Google OAuth and requests the gmail.send scope. We want to be precise about what this does and does not allow:

• What we request: permission to send email on your behalf through the Gmail API, plus your basic profile and email address to identify the connected account.
• What we can do: send the outreach emails you compose and choose to send, or schedule to send. That is all.
• What we cannot do: we do not request read, modify, or delete permissions. We cannot read your inbox or existing emails, see your contacts, search your mailbox, or access any other Google data. The gmail.send scope only permits sending.
• What we store: an encrypted OAuth refresh token and your Gmail address, so we can send on your behalf without asking you to sign in each time. The refresh token is encrypted at rest with AES-256-GCM.
• How to revoke: disconnect Gmail at any time from Settings → Email (which deletes the stored token and asks Google to revoke it), or remove access directly at myaccount.google.com/permissions.

Gmail and AI

• Data we receive from Google APIs is never sent to an AI model provider, and is never used to develop, improve, or train any AI or machine learning model, generalized or personalized. If you signed in with Google, your account name and email are among the details we hide before a request reaches a provider (see section 4).
• Seekrly AI can help you write a message. It works from what you saved in Seekrly (your profile, the contact, and earlier messages you sent through Seekrly), never from your mailbox. You review and edit every draft, and it is sent only when you send it or schedule it.

Gmail, connected AI apps and API keys

• An AI app you connect, or a tool using your API key, can ask Seekrly to send an email only if you granted it the "Send emails to your contacts" permission. Seekrly then sends it through your connected account like any other outreach. From a connected AI app, sending takes a separate confirmation step, and the app is asked to show you the full email before you confirm.
• These apps and tools never receive your Gmail token, your connected Gmail address, or anything else from your Gmail connection. They only learn whether an email sender is connected and whether a message was sent.

Google user data is not transferred to third parties except as needed to provide the sending feature (i.e. to Google itself to deliver your message), to comply with law, or as part of a merger or acquisition disclosed to you. No person at Seekrly reads Google user data unless you ask us to (for example, for support), it is needed for security or to investigate abuse, or the law requires it.

Seekrly'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.

Outreach (follow-ups to your own contacts) is sent from your mailbox through your connected Gmail account or your own SMTP server, not from a shared Seekrly address. The recipient therefore sees your address, and replies go to you. A message is sent only when you send it, or at the time you scheduled it if you turned on automatic sending for that follow-up. You are responsible for the content of these messages, including drafts written with Seekrly AI, and for having a lawful basis to contact each recipient (see our Terms of Service).

Separately, transactional emails (verification codes, password resets, security notices, reminders) are sent by Seekrly through our own email-delivery provider.

You can connect AI apps (assistants that support the Model Context Protocol, MCP) to your account, and on plans that include it, create API keys for your own tools and automations.

• You choose the access. When you connect an app, you see what it asks for and choose which parts of your account it can view or change. An API key has only the permissions you pick when you create it. Every connected app always receives your name, email address and Seekrly plan.
• What Seekrly receives from the app. Only the requests the app sends to carry out what you asked, such as a job posting to save, an interview to schedule or an email you approved, plus the connection itself: the app's name, the permissions you granted, when it was last used, and its access tokens (stored only as hashes). Seekrly does not receive your conversation with the AI app, your chat history or your other chats, and never asks the app for them or for your precise location.
• What the app receives. Only the Seekrly data it asks for to answer you, within the permissions you granted. It never receives your password, your Gmail or SMTP credentials, your API keys or other connections' secrets. Resume download links it gets expire after 5 minutes.
• Sensitive actions need your OK. From a connected AI app, sending an email, deleting anything, merging companies, suggesting a company or a correction for the shared directory, sending a message to our support team, rewriting your career profile or a resume, and making a resume public each take a separate confirmation step. The app is asked to show you a preview first, and the preview expires after 10 minutes.
• The app handles what you share under its own policy. Data a connected app reads from Seekrly goes to that app and to the AI model it uses, and is governed by that app's privacy policy, not this one. Only connect apps you trust.
• Seekrly AI through the API. If you grant the "Use Seekrly AI" permission, an app or tool can run Seekrly AI features for you. They use your AI allowance and are processed as described in section 4.
• Revoke any time. Disconnect an app, change its access, or revoke an API key from Settings → Security. It loses access immediately.
• How long a connection lasts. An app's access token expires after 1 hour and is renewed while you use the app. A connection that isn't used for 30 days ends, and you connect again to keep using it. What an app did in your account is kept in your activity records (see section 14).

We use what connected apps send only to carry out your requests, never to train AI models or for advertising.

Application data is stored in a MongoDB database. Passwords are hashed with bcrypt; we never store plaintext passwords. API keys are stored as SHA-256 hashes. Secrets we must be able to reuse (your SMTP password and your Gmail OAuth refresh token) are encrypted at rest with AES-256-GCM and are never returned to your browser, to connected apps, or to AI providers. Session tokens are signed JWTs stored in HTTP-only, Secure, SameSite cookies. One-time verification codes are stored hashed and expire automatically. AI requests waiting to be processed are held in a temporary queue and removed from it as soon as the answer is ready.

Login session records (including device details and IP history) are retained while the session is active. When you log out or revoke a session, the record is deleted and no longer accessible. Extension session records follow the same lifecycle.

While we take reasonable technical measures to protect your data, no system is completely secure. Please use a strong, unique password and keep your API keys confidential.

We rely on a small number of providers that process data on our behalf solely to run the Service. These providers act as processors under their own security and privacy terms and are not permitted to use your data for their own purposes. We currently use service providers including:

• MongoDB Atlas: database hosting
• Cloudflare: CDN and security, including bot protection (Turnstile) on sign-up and sign-in forms
• OpenAI and Anthropic: AI models for Seekrly AI features, receiving only requests with personal details hidden (see section 4)
• Amazon Web Services Simple Email Service (Amazon SES): transactional email delivery
• PayPal: payment processing
• Razorpay: payment processing

These providers only process data on our behalf and may not use it for their own purposes. Our AI model providers may be located in the United States.

We do not sell, rent, or share your personal data with third parties, except:

• With the service providers described above, only as needed to operate the Service.
• With AI model providers, only the content of the AI requests you make, with your personal details hidden (see section 4).
• With AI apps and tools you connect, within the permissions you grant (see section 7).
• With email recipients you choose: when you send an outreach message, its contents are delivered to that recipient through your mailbox.
• With people you share a resume link with (see section 12).
• With other Seekrly users, through the shared company directory, as described below.
• When required by law or a valid legal process.
• To protect the rights, property, or safety of Seekrly, its users, or the public.

We do not sell, license, or transfer Google user data to data brokers, advertisers, AI model providers, or other third parties.

The shared company directory. Seekrly keeps a directory of companies whose public details (name, website, careers page, social links, industry, offices and a description) are shown to every user who tracks that company. You can suggest one of your companies for it, and unless you turn this off in Settings, Preferences, a company you add with a website or careers page is suggested automatically (not when a connected AI app adds or edits it: from an AI app, only a suggestion you confirm is sent). A suggestion sends only that company's public details, never your name, your applications, notes, contacts or anything else about your job search, and it is never shown as coming from you. Our team reviews every suggestion and may edit or reject it; once added, the details become part of the directory and stay there even if you later delete your company or your account. Applications, contacts, follow-ups, notes, interviews and resumes are never shared through the directory. Companies, applications and contacts are not otherwise made public.

If you purchase a paid plan, payment is processed by a third-party payment provider. In connection with billing we collect and/or process:

• Billing identifiers: your name, email address, and a customer identifier from the payment provider, used to link your subscription to your Seekrly account.
• Transaction records: plan type, billing cycle, payment amount, currency, transaction status, and timestamps for charges, renewals, and cancellations.
• Partial card details: we may store the last four digits and expiry date of your card (provided by the payment processor) so you can identify the payment method on file. We never receive or store your full card number, CVV, or banking credentials.

Payment data is used solely to process transactions, manage your subscription, and comply with applicable tax and financial record-keeping obligations. It is shared only with the payment processor as necessary to complete your transactions. We retain billing records for as long as required by law (typically up to 7 years for tax purposes) even after account deletion.

Resumes you upload are stored in our database or file storage, tied to your account. Resumes you build are stored as structured data in our database. Both are private by default: only you, and apps you allow to view your resumes, can access them. They are deleted when you remove them or delete your account. If you ask Seekrly AI to read or tailor a resume, it is processed as described in section 4.

Sharing. You can choose to share a resume through a link. A shared link can be public (anyone with the link can view it) or password-protected (viewers must enter the password you set). We ask search engines not to index shared resumes, but anyone you give the link to can pass it on, view, and, if you allow it, download the resume. Please only share what you are comfortable making public.

• For a built resume, viewers see a version that leaves out your street address, postal code, and references. Contact details on the resume, such as your email and phone number, are shown.
• For an uploaded resume, viewers see the original file exactly as you uploaded it, including everything in it.
• You can turn downloads off, change the password, create a new link (which stops the old one working), or make the resume private again at any time.
• We show you how many times your shared resume was viewed and downloaded, as totals only. See “Shared resume view counts” in our Cookie Policy.

Seekrly offers an optional Chrome browser extension that helps you save jobs, find recruiter contacts, and fill in application forms. Using it is entirely optional.

• Where it runs: it can load on the pages you visit so it can recognize job postings and application forms. Recognizing a page happens on your device; it does not record or send your browsing history.
• What it sends on its own: on a page it recognizes as a job posting, it shows its button and asks your Seekrly account whether you already saved that job, sending only the site and the job's identifier. Nothing is sent from other pages.
• What it sends when you act: when you save a job, it sends the visible job details on that page (such as title, company, location, salary, description, and skills) to your account, along with any contacts or follow-ups you add. If you turn on automatic tracking, clicking a job's Apply button saves the job the same way.
• Autofill: when you click Auto-fill, it fills the form on that page from your Seekrly profile and the resume you choose. If your plan includes Seekrly AI, questions it can't fill can be sent with the job details to Seekrly AI for suggested answers (see section 4). Fields that look like passwords, verification codes, or card and bank numbers are never sent to Seekrly AI. To improve autofill, it may report which kinds of fields were filled wrongly, as anonymous counts without the values.
• Where data goes: only to your own Seekrly account, over HTTPS. The extension does not send data to any other party; AI requests are processed as described in section 4.
• How it authenticates: it signs in through your existing Seekrly web session and uses short-lived tokens, stored in the browser's extension storage on your device and not exposed to the web pages you visit. You can sign out from the extension or revoke its session in Settings.
• Device information: when the extension connects, it sends device details (operating system, browser, extension version, screen resolution, CPU architecture, memory, timezone, and language) so you can identify connected devices in your account settings. This data is stored alongside the extension session and deleted when you revoke the session.
• What it does not do: it contains no analytics, advertising, or tracking code, and it does not collect data for any purpose other than the features described here.

We retain your data for as long as your account is active. If your account is inactive for 12 consecutive months (no login or API activity), we may permanently delete your account and all associated data without prior notification. It is your responsibility to maintain activity on your account if you wish to preserve your data.

Items you delete are hidden right away and permanently removed within 30 days. AI usage records are kept as described in section 4. Your suggestions for the company directory are kept until your account is deleted; company details our team has added to the directory are not personal data and remain in it.

Activity records (section 2) are kept for 365 days and then deleted automatically. A connected app or API key you revoke stops working at once, and its record is permanently removed within 30 days. Support requests are kept as our support records so we can follow up on them, including after your account is deleted; ask us and we will delete them.

When you delete your account (or when it is deleted due to inactivity), your account is immediately disabled, and API keys and connected apps are revoked. Personal data, including your AI history and AI usage records, is permanently deleted from our production systems within 30 days, except where we are legally required to retain certain records (such as billing records, which may be retained for up to 7 years for tax purposes) and support requests as described above. Backup copies are automatically overwritten within 90 days.

We use cookies and browser storage in three groups. Essential ones are always on. Analytics and embedded content load only after you allow them in our cookie banner. Our Cookie Policy lists each one, what it is for and how long it is kept, and lets you change your choice.

Depending on your location, you may have the right to access, correct, export, or delete your personal data, to object to or restrict how it is processed, and to withdraw consent (for example, by disconnecting Gmail, disconnecting an AI app, turning off automatic AI features, or turning off company directory suggestions in Settings). You can choose not to use Seekrly AI at all. To exercise these rights, contact us using the information below. We will respond within a reasonable timeframe.

The Service is not directed at children under 13. We do not knowingly collect personal data from children under 13. If you believe we have collected such data, please contact us immediately.

We may update this Privacy Policy from time to time. When we do, we will revise the effective date above. Continued use of the Service after changes constitutes acceptance of the updated policy.

Google user data is only accessed after explicit user authorization. Access is limited to the minimum permissions required for the requested functionality. Seekrly never requests or accesses Gmail content beyond what is required to send emails explicitly initiated by the user, and never requests or accesses Gmail messages, drafts, contacts, attachments, or mailbox metadata. Data from your Gmail connection is never shared with AI model providers or connected AI apps, and no Google user data is used to train AI or machine learning models.

For privacy-related questions or data requests, email us at [email protected]. We aim to respond promptly.