Trust Center

The Callings.ai Trust Center explains, in plain language, how we handle your career data: what we collect, how it is protected, which third parties we work with, how long we keep it, and the controls you have. It goes into more operational detail than our formal Privacy Policy so you can make an informed decision before adding sensitive materials.

We built Callings.ai to hold some of the most personal information in a job search: your resume, your work history, your goals, and your outreach. We treat that responsibility seriously, and we would rather tell you exactly how things work today than make broad claims.

Last updated: September 17, 2026.

This page describes our current practices. It is a companion to, and does not replace, our Privacy Policy, which remains the authoritative legal document.

Our Approach

We follow a simple principle: your data is yours, we use it only to power your experience, and we never sell it. Selling subscriptions, not data, is how we stay in business.

We do not sell your personal information.
We do not share your resume, profile, or job-search activity with third parties except the service providers needed to operate the platform (listed below).
If an employer, school, or other organization pays for your access, it receives program counts, and, where it set up your account for you, whether you have signed in. Never your content, unless we have asked for your consent and you gave it. See When Someone Else Pays for Your Access.
No user content is used to train third-party AI models.
You can delete your data, in whole or in part, at any time.

The Data We Handle

Callings.ai collects only what it needs to run your job search. The main categories are:

Category	Examples
Account information	Name, email, password (stored hashed, never in plain text)
Career materials	Uploaded resumes, generated resumes, cover letters, job notes
Profile and preferences	Job titles, target roles, city and state, writing preferences
Job-search activity	Saved jobs, application statuses, contacts you choose to track
Application answers	Answers you save from application forms via the browser extension (opt-in), so future forms can be pre-filled. Each answer also notes how it got into the field: that you typed it on the form, that you wrote or chose it in the extension panel, that Callings filled it from what you had already told us, or that it came from an AI draft (and whether you edited that draft first). It is kept so your record shows what you wrote and what we wrote, and so we can measure how well the extension does its job. It is stored as part of that job in your tracker, it is never shared with employers or other users, and it is deleted with the job or with your account
Voluntary self-identification	Demographic answers (such as sex, gender identity, ethnicity, race, veteran or disability status) you explicitly choose to store, so we can complete the voluntary self-identification questions on forms you apply through. Entirely optional, and you decide per question whether we answer it for you or leave it to you. We never infer any of these from your resume or anything else; we only use what you typed. They are stored privately in your application profile, and where you answer one on a form, your answer is kept in that job's own application record alongside everything else you filled, so your record is a complete copy of what you sent. They are never shared with other users or used to pre-fill anyone else's form, never shown to anyone at Callings, and never used for job matching, recommendations, fit scores, analytics or advertising. Leaving an answer blank never affects an application, and you can view, edit, or delete them at any time
Generated content	AI outputs such as reports, tailored documents, and outreach drafts
Security and abuse prevention	At sign-up only, a one-way scrambled form of your IP address and browser identifier, plus the country, region, and city our network provider reports. Used solely to detect and prevent fraud and abuse of the service. The IP address itself is never stored, and this data is never used for advertising, profiling, or location matching
Public job searches	When anyone runs a search on our public job search page without signing in, we keep a standalone record of the search wording and how many results it returned, so we can see whether the search works. It carries no account, no IP address, no cookie, and no visitor or device identifier of any kind, so it cannot be connected to you, to your account, or to your other searches
Connected assistants	If you connect an outside AI assistant, we store the connection itself (which app, what you approved, when you connected it, when it was last used) so you can see and revoke it, plus a record of the few paid actions it takes on your behalf: which action, when, and whether it ran. Never your conversation with it
Billing	Handled by our payment processor; we do not store full card numbers

Encryption and Data Protection

All data is encrypted in transit and at rest.

In transit: Connections to Callings.ai use TLS (HTTPS) end to end.
At rest: All of your data is encrypted at rest. That includes the files you upload, such as resumes, held in encrypted cloud storage, and every database that stores your profile, job-search notes, contacts, and generated materials. All of it runs on encrypted infrastructure managed by a major US-based cloud provider.
Passwords: Stored using one-way hashing. We cannot see your password, and neither can anyone on our team.
Backups: Backups of our encrypted stores are themselves encrypted.

We use established, US-based, tier-one cloud infrastructure. Databases are not exposed to the public internet and are reachable only by our application. Service credentials are held in a managed secrets store rather than in code.

AI Providers and Your Content

When you generate a resume, cover letter, or report, we send an established US-based AI provider only the content needed for that task, and that content is not used to train the provider's models.

For resume and cover letter generation, the provider receives your resume text, the relevant job description, and any instructions you give. It returns the generated document.
For job matching, a provider receives a condensed extract of your resume together with the job descriptions being scored, and returns how well each job fits. When you type a search in your own words, that search text is sent to be interpreted into search filters.
We do not enable any data-sharing-for-training option with our providers. Under their business and API terms, content submitted through the API is not used to train their models. Providers may retain content for a limited period for operational and abuse-monitoring purposes under those same terms, after which it is removed.
Image features (for example, illustrations on calling cards or posts) use a separate provider and do not receive your resume content.
We do not send your career materials to any provider for advertising or model training.

A current list of the providers we work with is in the Subprocessors section below.

AI Assistants You Connect Yourself

If you connect an outside AI assistant to your Callings account, that assistant can read your job hunt on your behalf, and what it reads passes through the company that runs it. This is a different arrangement from the providers above, and it happens only when you set it up.

It is off unless you turn it on. Nothing is connected by default. You add the connection in your assistant, sign in to Callings in your own browser, and approve what it may see on a screen built from the actual permissions.
The assistant is acting for you, not for us. We have no agreement with the company running it governing your conversation, which is why it is not one of our subprocessors: it is your own tool, reading your own data at your instruction. That company's terms and retention then apply to the conversation, including the parts of your job hunt that appear in it.
It reads your account only. The connection carries your identity and cannot reach another user's data, and it cannot see your password or your payment details.
A handful of actions can write. It can add a job, record your decision on one, save a found email address onto a contact, and start a tailored resume or cover letter. Nothing deletes your data, applies to a job, sends an email, or publishes anything.
We never receive your conversation. We see the requests your assistant makes and the details it sends in order to answer them, and we keep routine operational logs of that. What you typed and what the assistant replied never reach us.
You can end it instantly. Settings > Integrations lists every connected assistant and revokes it on our side in one click, which stops it working whatever the assistant does next. Access also expires on its own roughly every hour and is renewed in the background.

If your search is confidential, this is the section to weigh before connecting: the data is yours to route, and routing it into another company's product is a choice only you can make. Our own AI Assistants documentation sets out exactly what can be read and changed.

Cookies, Analytics, and Tracking

Your cookie choice controls what is stored on your device and what reaches advertising and marketing platforms. Separately, we keep an internal operational record that we need in order to run the service.

We show a cookie consent banner, managed by a dedicated consent platform (CookieYes). Choosing to reject disables cookie-based tracking and clears related cookies.
The banner adapts to where you are. In regions that require opt-in consent, such as the EU and UK, nothing non-essential runs until you accept. In regions that operate on an opt-out basis, you can decline at any time and we honour browser-level signals such as Global Privacy Control.
Your choice is recorded so we can show what was agreed and when, and you can change it whenever you like.
Advertising trackers run only on our public marketing pages. They are switched off the moment you sign in, so advertising does not follow you inside your account. If you decline, nothing about you reaches an advertising platform and you are not added to any advertising audience.
With your consent, our marketing analytics measures which pages are visited, inside your account as well as on our public pages, so we can see how people find the platform and what they do next. It records page addresses and product events such as saving a job. It never includes the content of your resumes, cover letters, or messages, and it is not used to target advertising to you.
Inside your account, with your consent, we also use privacy-respecting product analytics to understand which features are used so we can improve the platform. This never includes the content of your resumes, cover letters, or messages.
Separately from cookies, we keep an internal record of key product events, for example that an account signed in, saved a job, generated a document, or ran into an error. We keep this whatever your cookie choice, because we rely on it to operate, monitor, secure, and improve the service, and we do so on the basis of our legitimate interest in running a reliable platform. It is linked to your account by an internal identifier, is never used for advertising, is never sold, and never includes the content of your resumes, cover letters, or messages. You can object to this use by contacting us.
The same applies to searches run on our public job search page without signing in, with one difference: those records carry no identifier at all. We store the search wording and the number of results, and nothing that says who ran it or that two searches came from the same person. They set nothing on your device, so they do not depend on your cookie choice and cannot be used to build a profile of you.
When counts of those milestones are sent to our external marketing analytics provider and you have not consented to cookies, they go without any cookie, device access, or persistent identifier, so those reports cannot be connected to you or to each other.
You can reopen the cookie preferences at any time from Settings under Privacy and Data, or from the Cookie Preferences link in the site footer, and change any category.
Some pages can carry a video player hosted by YouTube or Vimeo, for example a short welcome video an organization added to the letter you see on your first sign-in. Loading the player tells that host your IP address and which page it is on. We use YouTube's no-cookie player, so it sets no advertising cookie unless you start the video.

Location Data

Location matching uses your city and state, not precise device location.

We use the city and state from your profile to match you to nearby roles.
We do not request or use GPS or precise device location.
Location is used only for job matching and to operate the platform. It is not used for advertising.

Data Retention

We keep your data for as long as your account is active, and remove it when you delete your account or the specific item.

Career materials, generated content, and job-search activity are retained for the life of your account so the platform stays useful to you.
Operational records that support generation features are retained for the life of your account and removed on deletion.
Diagnostic logs used to keep the service running are short-lived and roll off on a routine cycle.
Sign-up security records (the scrambled IP and browser identifier described above) are retained for the life of your account and removed on deletion.
Records of searches run on the public job search page without signing in are kept as aggregate usage history. They are not tied to an account, so they are not linked to you and there is nothing in them to look up, return, or delete on request; the search wording is all that remains, standing alone.
Connected-assistant records are removed when you disconnect the app or delete your account; the record of paid actions taken on your behalf rolls off after six months.
Billing records may be retained as required by law and by our payment processor, even after account deletion.

Your Controls and Rights

You can review, edit, and delete your information at any time.

Delete individual items: You can delete an uploaded resume, a generated resume, a job entry, or a note without closing your account. Cover letters and tailored resumes are attached to the job they belong to and are removed when you delete that job or replaced when you regenerate them.
Delete your account: Settings includes a Danger Zone where you can request permanent deletion.
Control cookies and analytics: Open Manage Cookie Preferences in Settings under Privacy and Data, or the Cookie Preferences link in the site footer.
Download your documents: Resumes, cover letters, and reports can be downloaded directly from the app, typically as PDF or DOCX.
Regional rights: We honor data-subject requests, including access and deletion rights under GDPR and CCPA. To request a copy of the personal data we hold about you, contact support.

To exercise any of these rights, use the in-app controls or email [email protected].

Account Deletion in Detail

When you delete your account, your career materials, generated content, job notes, and job-search activity are removed from our active systems.

Deletion removes your resumes, generated documents, cover letters, job descriptions, notes, saved jobs, the contacts you track and their notes, and related records from live systems.
Encrypted backups age out on their normal rotation rather than being individually edited, so residual copies expire over time.
Because each AI generation is a stateless request, there is no separate per-user store at the AI provider for us to delete; any transient provider-side copy expires under the provider's terms.
Billing and transaction records may be retained where the law requires it.
Searches run on the public page before you had an account are unaffected, because nothing ever connected them to you: those records hold no account, cookie, or device identifier, so there is no way to tell which of them were yours.
Account deletion is permanent and cannot be undone once processed.

What Stays Private to You

Everything you add yourself stays in your account. It is never shown to other users and is never added to any shared pool.

The content you create as you run your search is private by default:

Jobs you add manually are saved only to your tracker. Other users cannot see, search, or be matched against them.
Contacts you add or track belong only to you.
Recruiters you add manually are stored exactly like a personal contact, scoped to your account. They are never written to the shared recruiter pool that powers recruiter suggestions for other users.
Target and saved companies you add are yours alone.
Notes and to-dos you write are visible only to you.

Some discovery features (such as suggested recruiters, professional associations, and events) draw on shared reference data so we can match the right opportunities to many users at once. That reference data comes from public sources, not from what you add, and your own activity on it (saves, dismissals, outreach drafts, and notes) always stays private to you.

When Someone Else Pays for Your Access

Someone may pay for your Callings.ai access: an employer, an outplacement or career transition firm, a university or alumni association, a professional body, a reseller, or an advisor. We call any of them a sponsoring organization. Paying for the service buys them the service for you. It does not buy them your job search.

Unless we have asked for your consent and you have given it, a sponsoring organization never sees:

your resume, cover letters, or any document the service writes for you;
the jobs you save, track, or apply to, and where you are in each one;
your contacts, recruiters, target companies, notes, or outreach drafts;
your searches, your preferences, or your fit scores;
anything you write to us or to our AI features.

What it can see is limited to how your account came to exist:

If the organization set up your account by giving us your email address, which it already had, it can see in its own console that the seat exists, whether an invitation email was sent to you, and whether you have signed in since that seat was created. It does not see anything from before that point, including whether you had used Callings.ai already.
If you signed up yourself through a link or code the organization shared, you are counted in its totals and never listed by name. It is not shown who joined.

What we report to a sponsoring organization is anonymous and aggregated: counts such as seats used, how many people started, and how many are active. Never a list of people, and never anything you have written or saved. Anything beyond that happens only where we have asked you and you have agreed, and you can withdraw that at any time. Accepting our terms or using access someone else paid for is not consent, and nobody can give it on your behalf.

Your account belongs to you, not to whoever pays for it. The organization cannot read, export, or delete your content, and if its sponsorship ends the account stays with you. Deleting it is always your decision, and works exactly as described above.

Public Pages and Visibility

Some features can help you create public-facing pages, and anything public is your deliberate, opt-in choice. We do not make your content public by default.

Callings.ai can help you build pages meant to be seen, such as your Calling Card and the Posts you choose to publish. These are designed to help you be found, so when public they are intentionally discoverable and may be promoted (for example, through search optimization).

You stay in control:

Nothing is published automatically. Making a page public is always an action you take.
You can change a page's visibility, or unpublish it, at any time.
If your goal is to avoid a public presence, you can keep these features private or simply not use them.
Deleting your account removes these pages and requests their removal from search indexes.

Internal Access

Access to user data inside Callings.ai is restricted to authorized personnel on a need-to-support basis.

Internal systems follow least-privilege access: people and services get only the access they need.
We access your content only to operate the service or to respond to a support request you have raised.
Some engineering and database work is carried out by contracted specialists rather than employees. They work inside our systems using individual named accounts protected by multi-factor authentication, their activity is recorded in our audit logs, and they are bound by confidentiality obligations equivalent to those of our employees.
Some of those specialists work outside the United States. Your data is always stored and processed in the United States, and none of it is transferred abroad, but it can be accessed from outside the country by these authorized individuals in order to maintain the service.
We do not browse, sell, or share your materials.

Subprocessors

We rely on a vetted set of service providers, our subprocessors, to operate the platform. Each one processes data under its own agreement and only as needed to provide its service. No subprocessor uses your content to train AI models.

See our full, dated Subprocessor List for the current providers, what each one does, the data it handles, and where it operates.

An AI assistant you connect yourself is not on that list and not a subprocessor: it does not process data on our behalf under our instruction, it reads your data on yours. It is described under AI Providers and Your Content above, and you control it from Settings > Integrations.

Compliance Posture

Callings.ai is an independent, growing company. We apply the practices described on this page, and we are candid about where we are in our security maturity.

We do not yet hold formal third-party certifications such as SOC 2 Type II or ISO 27001. The practices here, including encryption, restricted access, consent-based tracking, and clear deletion controls, reflect how we operate today. We report our current state rather than promise future milestones.

Reporting a Security Concern

If you believe you have found a security or privacy issue, we want to hear from you.

Email [email protected] with the details. We review reports promptly and will follow up with you.

Who We Are and How to Reach Us

Callings.ai is operated by JobHunters, Inc., doing business as Callings.ai.

Email: [email protected]
Mail: JobHunters, Inc. (dba Callings.ai), 2010 El Camino Real #2270, Santa Clara, CA 95050, USA

This is the address that appears in the footer of the emails we send you, and the address to use for written privacy or data-subject requests.

Frequently Asked Questions

Q: Are my uploaded resumes encrypted? A: Yes. All of your data is encrypted at rest, including the files you upload such as resumes, and everything is also encrypted in transit using TLS.

Q: Do you use my resume or prompts to train AI models? A: No. Your content is not used to train any third-party AI model. We do not enable training-data-sharing with our providers, and we never sell your data. If you connect your own AI assistant, the conversation you have with it is governed by that company's settings rather than ours, so check its training and retention options if that matters to you.

Q: Which AI providers see my career materials? A: For resume and cover letter generation, your content goes only to an established US-based AI provider, sent solely to produce the document you requested. Job matching sends a condensed extract of your resume and the job descriptions being scored to a US-based provider so it can rank how well each job fits. Image features use a separate provider that does not receive your resume content. Every provider we use is named in the Subprocessor List, and none of them train on your content. The one exception is an AI assistant you connect yourself, which is covered in the next answer.

Q: If I connect an AI assistant, what does it see and who else sees it? A: It can read your own job hunt (your tracker, matches, contacts, resumes, saved companies and notes) and it can add a job, record your decision on one, save a found email onto a contact, and start a tailored resume or cover letter. Because it is your assistant and not our provider, what it reads passes through the company that runs it, and that company's terms and retention apply to your conversation. Nothing is connected unless you set it up, we never receive the conversation itself, and you can revoke access in one click from Settings > Integrations.

Q: Can I delete a single resume without deleting my whole account? A: Yes. You can delete an uploaded resume, a generated resume, a job, or a note individually. Cover letters and tailored resumes live with the job they belong to and are removed when you delete that job.

Q: What happens to my data when I delete my account? A: Your career materials, generated content, notes, job-search activity, and any connected-assistant permissions are removed from active systems. Encrypted backups expire on their normal rotation, and billing records may be retained where the law requires it.

Q: Am I tracked when I am signed in? A: Advertising trackers do not run inside your account, and nothing about you reaches an advertising platform without your consent. With your consent, our analytics does measure the pages you visit inside your account, so we can understand how the product is used and improve it. That measurement covers page addresses and product events such as saving a job, never the content of your documents, and it is not used to target advertising to you. Whatever you choose, we keep an internal record of key product events, such as signing in or saving a job, because we need it to operate, monitor, and secure the service. That record stays internal, is never used for advertising or sold, and never includes the content of your documents.

Q: What do you record when I search jobs without an account? A: Only the search wording and how many results came back, kept so we can tell whether the search is working and how much it is used. There is no account behind it, and we attach no cookie, IP address, or device identifier to it, so the record cannot be connected to you or to any other search you run. Nothing is stored on your device to make this work, which is why it does not depend on your cookie choice.

Q: My employer, school, or another organization is paying for my account. What can they see? A: Not your job search. They never see your resume, the jobs you save or apply to, your contacts, your notes, or your searches. If they set the account up for you with an email address they already had, they can see that the seat exists, whether an invitation was sent, and whether you have signed in since. If you signed up yourself through a link they shared, you are only counted in their totals and never listed. What we report to them is counts, not lists of people. The exception is anything we have asked your consent for and you have agreed to, which you can withdraw. Full detail is in When Someone Else Pays for Your Access above.

Q: Do you have SOC 2 or ISO 27001? A: Not yet. We are a growing company and do not currently hold those certifications. This page describes the protections we have in place today.

Q: Where is the subprocessor list? A: A representative list is in our Privacy Policy. For the full current list, email [email protected].

Your career story is yours. We hold it carefully, use it only to help you find your next role, and give you the controls to take it back whenever you choose.