01Who we are
Applyra (“Applyra”, “we”, “us”) is an AI-assisted career and placement platform operated from India. In this policy, “you” means anyone whose personal data we handle: a job seeker, a student, a college or university placement team, an employer or recruiter, or an interviewer.
This policy applies to the Applyra website at applyra.co, the Applyra web application at app.applyra.co, the APIs behind them, and every Applyra product surface across our four portals — Job Seekers, Students, Colleges and Employers. It does not apply to any third-party website, job board or applicant tracking system you reach through Applyra, each of which has its own privacy policy.
We process personal data in accordance with India's Digital Personal Data Protection Act, 2023 (“DPDP Act”) and applicable rules under it. Where the EU or UK General Data Protection Regulation applies to a user, we also honour the rights and legal-basis requirements described in this policy.
02Summary at a glance
This summary is for orientation only. The detailed sections below govern.
- We do not sell personal data. We have never sold it and we do not rent, trade or licence it to data brokers or advertisers.
- We do not run behavioural advertising. Applyra carries no third-party ad pixels and we do not build advertising profiles.
- Your resume is used to help you, not to train public AI models. Resume and profile content is sent to our AI provider under enterprise terms that prohibit using it to train the provider's general models.
- A college or employer that invites you can see your data on their tenant. Applyra is multi-tenant: if you register through a college or a recruiter, that organisation is the primary decision-maker for the records it holds about you.
- Google and Microsoft account access is narrow and revocable. We request the minimum permissions for the feature you enable, we never ask for access to your email inbox or to your whole Drive, and you can disconnect at any time.
- You can ask for a copy, a correction, or erasure. Write to support@applyra.co.
03Our role: controller or processor
Applyra serves individuals directly and also serves institutions. Which of those applies changes who is accountable for your data, so it is worth being precise.
Where Applyra is the Data Fiduciary (controller)
When you sign up for Applyra yourself as a job seeker, create your own account, buy a subscription or credits, or contact us, Applyra decides the purposes and means of processing. We are the Data Fiduciary under the DPDP Act (equivalent to a “controller” under the GDPR) for that data.
Where Applyra is a Data Processor
When a college, university or employer licenses Applyra and uploads or invites its students or candidates, that organisation is the Data Fiduciary. It decides what records to hold, which drives to run, which candidates to shortlist and how long to keep the data. Applyra processes that data on its documented instructions, under contract, and does not use it for our own independent purposes.
In that situation, requests to access, correct or delete records held on your institution's tenant are best directed to the institution first — its placement office, TPO or HR team. If you contact us instead, we will acknowledge you and route the request to them, and we will tell you that we have done so.
A note on dual records
It is possible to have both: a personal Applyra job-seeker account that you control, and a student or candidate record on an institution's tenant. They are separate records. Deleting one does not delete the other, and we will tell you which one a given request affects.
04Information we collect
4.1 Information you give us directly
- Account details: name, email address, mobile number, a hashed password, your role on the platform, and email or phone verification status.
- Job-seeker profile: current company and designation, years of experience, highest qualification, preferred location, skills, LinkedIn, GitHub and portfolio links.
- Student academic record (where you use the Students or Colleges portal): enrollment number, department or branch, passing year, CGPA, active and total backlogs, class 10, class 12 and diploma percentages, certifications, gender and date of birth.
- Documents you upload: resumes, marksheets, degree and course certificates, identity or eligibility documents requested by a recruiter, and any other file you attach. We also store text and structured fields extracted from those documents by optical character recognition, and a classification verdict indicating whether a document appears to be of the type requested.
- Application activity: jobs and drives you save or apply to, application status transitions, interview round results and feedback, offers extended, offer acceptance or decline, and current or offered CTC.
- Interview and scheduling data: your availability, booked slots, and interview panel assignments.
- Payment and billing data: the plan or credit pack you purchase, order and payment identifiers returned by our payment gateway, invoice and credit-transaction history, and for organisations, billing contact and GSTIN (which we may verify against a government GST lookup service). We do not receive or store your full card number, CVV, UPI PIN or netbanking credentials — those go directly to the payment gateway.
- Support and communications: what you write to us, and our replies.
4.2 Information we receive from your college or employer
A placement office or recruiter may create your record before you ever log in — by importing a student roster, uploading a candidate list, or forwarding a resume. That record may include your name, email, phone, resume, academic figures and internal recruiter notes about you. When we send you an invitation to register, that is usually why you already exist in the system.
4.3 Information from a Google or Microsoft account you connect
Connecting a Google or Microsoft account is optional and feature-specific. If you connect one, we store the email address of the connected account (so we can show you what is linked), an OAuth access token and refresh token, and the granted permissions. Depending on the feature, we then handle application forms we created and the responses submitted to them, interview calendar events and busy intervals, and, only where the interviewer's company has switched interview transcripts on, the transcript of an interview meeting. Section 7 sets out each permission and its purpose in full.
4.4 Business contact details of recruiters and company representatives
To help colleges reach companies for campus placements, we keep business contact details of people who work in recruitment, HR, talent or leadership roles at companies: name, job title, company, work email address, and the public page where the details were found. We collect these from the company's own public website, from public search results, and from business email-finding services. We never collect personal email addresses or phone numbers this way, and an address on a free email service is discarded.
If you are one of these people, you can ask us to remove your details or stop using them at any time by writing to support@applyra.co, or by using the opt-out line in any outreach email you receive through Applyra. We then keep only a record that you opted out, so you are not added again.
4.5 Information collected automatically
- Session and security data: authentication tokens and refresh tokens, login timestamps, and the IP address and user-agent associated with a session, used to keep you signed in and to detect abuse.
- Server logs: request paths, response codes, timings and error traces. We instrument our systems to avoid writing credentials, tokens or document contents into logs.
- Product usage: which features you use and how often, including counts of AI runs, so we can meter plan limits and credits and improve the product.
4.6 What we do not collect
We do not ask for and do not want your Aadhaar or PAN number, caste or religion, health records, biometric data, or bank account credentials. If a college or employer configures a custom field that collects something of this kind, it does so as the Data Fiduciary and on its own responsibility; we ask institutions not to, and you may raise it with us at support@applyra.co.
05How and why we use it
We use personal data only for the purposes below. Where the GDPR applies, the legal basis is named alongside; under the DPDP Act we rely on your consent or, where available, a legitimate use such as performing a service you have asked for.
| Purpose | What that means in practice | Legal basis (GDPR) |
|---|---|---|
| Provide the service | Create and authenticate your account, build and store your profile and resume, show you jobs and drives, submit applications, track status, run interview rounds and record outcomes. | Performance of a contract |
| Match and recommend | Compare your skills, experience and eligibility against job and drive criteria to produce recommendations, eligibility checks and skill-gap analysis. | Contract; consent for optional AI features |
| Generate AI output you request | Optimise or rewrite a resume for a specific role, score it against a job description, draft recruiter outreach, and run interview practice with feedback. | Consent |
| Communicate | Send verification and password emails, application and interview updates, deadline reminders, offer notices and service announcements — by email and, if you opt in, WhatsApp or SMS. | Contract; consent for marketing |
| Billing and credits | Take payment, meter plan limits and credit balances, issue invoices, handle refunds and chargebacks, and meet tax and accounting obligations. | Contract; legal obligation |
| Safety, integrity and abuse prevention | Detect fraudulent accounts, fake resumes, scraping, spam applications and credential stuffing; enforce our Terms. | Legitimate interests |
| Improve the product | Diagnose faults, measure feature performance, and analyse aggregated, de-identified usage patterns. | Legitimate interests |
| Legal compliance | Respond to lawful requests, keep records we are required to keep, and defend legal claims. | Legal obligation |
We do not use your personal data for advertising or ad targeting, and we do not disclose it to advertising networks or data brokers.
06AI features and automated processing
Several Applyra features use large language models: resume building and optimisation, ATS scoring, job matching, drive and job-description creation, candidate ranking, interview questions and evaluation analysis, recruiter outreach drafting, interview practice and feedback, career and skill-gap insights, and document classification.
What is sent to the model
Only the content the feature needs — typically your resume text or profile fields plus the relevant job description or question — is sent to our AI provider (Google Cloud Vertex AI, and Google Cloud Document AI for reading text from scanned documents). Where an interview transcript is available, the evaluation analysis also sends that transcript. We apply input filtering before dispatch to reduce the risk of prompt injection from uploaded content.
What the provider may not do with it
We use these services under enterprise terms under which the provider processes the content only to return a response to us, does not use it to train or improve its generally available models, and does not use it for its own purposes.
AI output is a draft, not a decision
AI-generated resumes, scores, matches and feedback are suggestions. They can be wrong, incomplete or out of date. Review anything before you send it. An ATS score from Applyra is our own heuristic estimate and is not the score any particular employer's system will produce.
Decisions about you
Applyra does not make hiring decisions. Eligibility filters on a campus drive (for example a CGPA cut-off or a backlog rule) are configured by the college or employer, applied mechanically to the figures in your record, and can exclude you from a drive. Shortlisting, rejection and selection are decisions of the college or employer, made by their people.
If an automated eligibility rule excludes you and you believe the underlying data is wrong, you can correct your record and ask the institution to re-evaluate. Where the GDPR applies and a decision is made solely by automated means with a significant effect on you, you have the right to obtain human intervention, express your view and contest the decision — write to support@applyra.co.
Auto Apply
AI Auto Apply, where enabled on a paid plan, submits applications on your behalf to roles matching criteria you set. That means your resume and profile are transmitted to the receiving employer or job portal without a further click from you. You choose the criteria, you can pause or disable Auto Apply at any time, and applications already submitted cannot be recalled by us.
07Connected Google and Microsoft accounts
Applyra's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Connecting a Google account is optional and is never required to use Applyra. Connecting one enables specific integrations. We request the narrowest scopes that make the feature work, we ask for them only in the flow that needs them, and we never request access to your Gmail inbox.
7.1 Scopes requested when a recruiter or placement team connects an account
-
openidemailIdentify which Google account was connected, so we can show you what is linked and let you disconnect the right one. Non-sensitive. -
https://www.googleapis.com/auth/forms.bodyCreate and edit the Google Form used to collect applications for a role or drive. -
https://www.googleapis.com/auth/forms.responses.readonlyRead submitted responses so applications appear in your Applyra pipeline. Read-only: Applyra never writes or alters a response. -
https://www.googleapis.com/auth/drive.fileShare and, when you ask, delete only the form files Applyra itself created. This scope grants no access to anything else in your Drive.
We do not ask your Google account for drive.readonly, drive,
or any other broad Drive scope. Those would grant read access to files unrelated
to Applyra, which is not needed to provision a form.
Separately, a recruiter can choose to share a folder of resumes with Applyra's own service address, in the same way you would share it with a colleague. We then read only the files in that shared folder, to import those resumes. This uses the access you gave through Drive's sharing settings, not your Google account's sign-in, and you can stop it by removing the address from the folder.
7.2 Scopes requested when an interviewer connects a calendar
-
openidemailIdentify the connected calendar account. -
https://www.googleapis.com/auth/calendar.readonlyRead busy intervals so Applyra does not offer candidates a slot when you are already booked. -
https://www.googleapis.com/auth/calendar.eventsCreate, update and cancel the interview events Applyra schedules, and keep them in sync when a slot moves. -
https://www.googleapis.com/auth/meetings.space.readonlyRequested only if the interviewer's company has switched interview transcripts on. Reads the transcript of the interview meetings the interviewer organised or joined, so the interview evaluation can use what was said. -
https://www.googleapis.com/auth/meetings.space.settingsRequested together with the scope above. Turns on automatic transcription for the interview meeting Applyra creates.
7.3 How we handle Google user data
- We use data obtained through Google APIs only to provide and improve the user-facing features described above.
- We do not transfer it to anyone else except as necessary to provide those features, to comply with applicable law, or as part of a merger or acquisition with notice to affected users and their consent where required.
- We do not use it for advertising, ad targeting, or any advertising purpose.
- We do not use it to develop, improve or train generalised or general-purpose AI models. Form responses and interview transcripts may be sent to our AI provider, Google Cloud Vertex AI, only to rank applications and analyse interview evaluations you asked for, under terms that prohibit the provider from training its models on them.
- We do not sell it.
- No human at Applyra reads it, except with your explicit consent for a specific purpose (such as support you have requested), where necessary for security investigation or abuse prevention, to comply with applicable law, or where the data is aggregated and de-identified.
7.4 Revoking access
You can disconnect a Google account inside Applyra at any time, which revokes the token with Google and deletes the stored token from our systems. You can also revoke access directly at myaccount.google.com/permissions. Revoking stops future access; forms and calendar events already created remain in your Google account and under your control, and any responses or transcripts already imported into Applyra remain in the relevant application or interview record unless you ask us to delete them.
7.5 Microsoft accounts
An interviewer can connect a Microsoft 365 account instead of a Google account. We then
request openid, email, profile and
offline_access to identify the account and keep the connection working,
Calendars.ReadWrite to read busy times and create, move and cancel interview
events, and OnlineMeetings.ReadWrite to create the Teams meeting for an
interview. Only where the interviewer's company has switched transcripts on, we also request
OnlineMeetings.Read and OnlineMeetingTranscript.Read.All to read
the transcript of those interview meetings. We do not request access to Outlook email.
Microsoft account data is handled under the same rules as section 7.3, and you can
disconnect it inside Applyra or at
myaccount.microsoft.com.
09Applying through external job portals
One Click Apply and Auto Apply submit your application to job boards, employer career sites and applicant tracking systems outside Applyra. Once your resume and details reach one of those systems, they are governed by that operator's privacy policy and retention practices, not ours. We cannot delete, correct or retrieve data from a third-party system on your behalf, and we cannot control how long they keep it. If you want data removed from such a system, you will need to contact that operator directly; tell us and we will share what we know about where an application was sent.
Job listings on Applyra may originate from partner recruitment agencies and aggregators. We take reasonable care but do not warrant that every listing is current, accurate or genuine, and you should never pay a fee to a purported recruiter. Report suspicious listings to support@applyra.co.
10International transfers
Applyra is operated from India and our primary data storage is in the Asia-Pacific (Mumbai) region. Some of our service providers process data in other countries, including the United States and the European Union. Where personal data moves outside its country of origin, we rely on the transfer mechanisms available to us — for EU and UK data, Standard Contractual Clauses or an adequacy decision; and we transfer to a jurisdiction only where such transfer is permitted under applicable Indian law.
11How long we keep data
We keep personal data only as long as we need it for the purpose it was collected for, plus any period we are required to retain it.
| Data | Retention |
|---|---|
| Active account and profile | For as long as your account is open |
| Account after you request deletion | Removed from the live product promptly, and purged from active systems within 30 days; encrypted backups age out within 90 days |
| Dormant account with no login | We may notify you and close the account after 24 months of inactivity |
| Resumes and uploaded documents | Deleted with the account, or earlier when you delete the file, except where a copy sits in a submitted application record on an institution's tenant |
| Application, drive and placement records on a college or employer tenant | For the period that institution sets, since it is the Data Fiduciary; typically through the placement cycle and its reporting obligations, such as NAAC or NBA reporting |
| Google and Microsoft OAuth tokens | Until you disconnect or revoke, then deleted |
| Interview transcripts | Kept with the interview record for the period the company or college sets, and deleted with it |
| Business contact details of recruiters (section 4.4) | Re-checked about once a year and deleted when no longer accurate, or at once when the person asks us to remove them |
| Payment, invoice and tax records | Retained as required by Indian tax and accounting law, generally 8 years |
| Security and audit logs | Up to 12 months |
| Aggregated, de-identified statistics | Indefinitely, since they no longer identify anyone |
Where we are unable to delete a record immediately — for example because it is part of an active recruitment process, or subject to a legal hold — we will restrict its processing and tell you why and for how long.
12Security
Our safeguards include:
- Encryption in transit over TLS for all traffic, and encryption at rest for stored files and databases.
- Passwords stored only as salted one-way hashes; we cannot read your password.
- Short-lived access tokens with rotating refresh tokens, revocable per session.
- Strict tenant isolation, so a college or recruiter can query only its own records.
- Role-based access control, with staff access limited to what a role requires and granted on a need-to-know basis.
- Deliberate exclusion of secrets, tokens and document contents from application logs.
- Uploaded files served through time-limited signed URLs rather than public links.
- Payment credentials handled entirely by a PCI-DSS compliant gateway; they never touch our servers.
No system is perfectly secure. If a personal data breach occurs, we will notify the Data Protection Board of India and affected users as required by the DPDP Act, and any other regulator to whom we owe notice, without undue delay. If you believe you have found a vulnerability, please report it to support@applyra.co and give us a reasonable opportunity to fix it before disclosing it publicly.
Please help us: use a strong unique password, do not share your login, and sign out of shared devices.
13Your rights and choices
Subject to applicable law, you can ask us to:
- Access the personal data we hold about you, and receive a summary of how it is processed and with whom it has been shared.
- Correct data that is inaccurate, and complete or update data that is incomplete or out of date. Most profile and academic fields you can edit yourself in the app.
- Erase your personal data where it is no longer needed for the purpose it was collected for, and delete your account.
- Export a copy of your data in a portable, machine-readable format.
- Withdraw consent at any time, including for AI features, marketing messages, WhatsApp or SMS notifications and Google account connection. Withdrawal applies going forward and may mean a feature stops working.
- Object to or restrict processing based on our legitimate interests, and, where the GDPR applies, contest a solely automated decision that significantly affects you.
- Nominate another individual to exercise your rights on your behalf in the event of your death or incapacity, as provided by the DPDP Act.
- Complain to us, and then to a regulator — the Data Protection Board of India, or in the EU or UK your local supervisory authority.
How to exercise a right
Email support@applyra.co from the address on your account, saying what you want. We will acknowledge within 7 days and respond substantively within 30 days. If we need longer for a complex request, we will tell you why and when to expect a reply. We may ask you to verify your identity before acting, and we will not charge you for a first reasonable request.
If your record sits on a college or employer tenant, see section 3 — that institution decides, and we will route your request to it and tell you we have.
Communication preferences
You can unsubscribe from marketing email using the link in any such email, or by writing to us. Service messages that are part of using Applyra — verification, security notices, application status, interview invitations, deadline reminders, billing and receipts — cannot be switched off while your account is active, because they are how the product works.
15Children and minors
Applyra is intended for people aged 18 and over, and for students at institutions of higher education. We do not knowingly create accounts for children under 18. Under the DPDP Act, processing a child's personal data requires verifiable parental consent, and we do not undertake tracking, behavioural monitoring or targeted advertising directed at children in any event.
If you are a parent or guardian and believe a child has given us personal data, write to support@applyra.co and we will delete it. If a college enrolls a student under 18, the college is responsible for obtaining the consent the law requires before uploading that student's data.
16Changes to this policy
We may update this policy as the product, our vendors or the law change. The “Last updated” date at the top always reflects the current version. For changes that materially affect how we use your personal data, we will give notice by email or an in-product notice at least 14 days before they take effect, and where the law requires consent for the new use, we will ask for it rather than assume it. Continuing to use Applyra after a change takes effect means you accept the updated policy.
17Contact and grievance redressal
For any question, request or complaint about privacy, or to exercise a right under section 13:
Privacy and grievance contact:
support@applyra.co
Write with the subject “Privacy” or “Grievance” and a member of
the Applyra team responsible for data protection will reply.
We will acknowledge your message within 7 days and aim to resolve it within 30 days. If you are not satisfied with our response, you may escalate to the Data Protection Board of India or, if the GDPR applies to you, to your local data protection supervisory authority.