Effective date: 11 October 2026
Provided by Sree Priya, trading as Tike AI Ventures, Bengaluru, India. Contact: trust@tikeai.ventures
Propel Resume Screener helps recruiters rank resumes against a job description. Recruiters use the app. The candidates whose resumes are uploaded do not.
For a recruiter's own account, we decide how the data is used (we are the "controller"). For the resumes and job descriptions a recruiter uploads, we work on the recruiter's behalf (we are a "processor"), and the recruiter's company is responsible for them.
Resumes and job descriptions are sent to two AI providers: TypeSafe, which scores resumes, and Anthropic, which suggests criteria from job descriptions and may also score resumes. Either of them may receive job descriptions and resumes. Neither of them trains AI models on this data, and neither do we.
The app scores and ranks resumes. It never rejects, shortlists or contacts anyone. A person makes every hiring decision.
There is no advertising in the app. Usage analytics and crash reports are collected only if you switch them on, and are not linked to your account. We do not sell personal data.
Data is stored in the United States and kept until you delete it. The exception is the original files you upload, which we delete automatically 365 days after you upload them; the text extracted from them stays. You can delete a resume, a job profile or your whole account in the app at any time.
Propel Resume Screener ("the app") is made by Sree Priya, a sole proprietor trading as Tike AI Ventures in India ("we", "us", "our"). On the App Store, the app's seller is shown as Sree Priya.
Address: 3rd Floor Plot No. 7F, Raj Pinnacle, 6th Cross Phase 1, Doddanekundi Industrial Area, Bengaluru, Karnataka 560048, India
Privacy contact and Grievance Officer: Sree Priya, trust@tikeai.ventures
We have not appointed a data protection officer, and we have not yet appointed a representative in the European Union or the United Kingdom. Please use the contact details above for anything you would send to them.
Recruiters: people who sign in to Propel Resume Screener, and the companies or agencies they work for.
Candidates: people whose resumes a recruiter uploads to the app. Candidates do not use the app themselves.
Visitors to this page.
We are the controller of recruiters' account details, sign-in details, purchase and credit records, crash reports, usage analytics, support emails and server logs. Under India's Digital Personal Data Protection Act, 2023 (the "DPDP Act") we are the Data Fiduciary for this data.
We are a processor of the job descriptions and resumes a recruiter uploads, and of everything the app produces from them: criteria, scores, rankings and downloads. The recruiter's company is the controller (the Data Fiduciary under the DPDP Act). It decides whose resumes to upload, why, and how long to keep them. We use this data only to provide the app to that recruiter.
Our Data Processing Addendum sets out how we process this data for the recruiter's company. It forms part of our Terms and Conditions and applies automatically, including the EU standard contractual clauses for candidates in the EU, the UK and Switzerland.
Your first and last name, email address and company name, which you enter when you set up the app.
Your settings: the app theme, and whether criteria are generated automatically.
When you finished setting up, and whether you have used the free trial.
You sign in with Google or Apple. Google's Firebase Authentication service handles sign-in and gives us a user ID, your email address and the name the provider shares. If you use Apple's "Hide My Email", we receive a relay address instead of your own.
Firebase Authentication keeps your sign-in details: email address, name, sign-in provider, and when you signed up and last signed in. We never see or store a password.
Apple or Google takes your payment. We never see your card or bank details.
RevenueCat manages purchases, subscriptions and credits for us. It receives a random user ID that we create (not your name or email address), what you bought and when, store receipts, your credit balance, and basic device and app details such as operating system, app version and country.
We record how many credits each scoring run used.
Job descriptions you upload or paste, and the criteria you or the app create from them.
Resumes you upload as PDF, DOCX or TXT files. We keep the original file, so you can download it again (originals are deleted automatically 365 days after upload; the text stays), and the text extracted from it. The app reads the text only and ignores any images in the file.
To list and organise resumes, the app stores the first line of each resume as its title and the next two lines as its description. These are usually the candidate's name and contact details. It also stores a fingerprint of the first three lines to spot duplicate uploads.
A resume contains whatever its author chose to write: contact details, work history, education and skills, and sometimes date of birth, nationality, marital status, health, religion or other sensitive details. We do not ask for these details, and the scoring instructions only ask about the recruiter's criteria, but they remain in the text we store and send for scoring.
The scores of each resume against each criterion, and the rankings and downloads built from them: a ranking summary document, and a ZIP file of selected original resumes.
For each scoring run we record how many resumes were scored, the criteria used, the AI model, the time taken, the amount of text processed, the cost, the credits used and any errors. Each record names the resume it scored by its title and description.
When a resume or job profile is deleted, the candidate's name and contact lines in these records are erased straight away. The counts and costs remain.
Crash reports are covered by the same switch as usage analytics (below) and are off until you switch it on.
When the switch is on and the app crashes, Firebase Crashlytics (a Google service) sends us a crash report: where in the code it failed, your device model, operating system and app version, and a random installation ID. Crash reports are not linked to your account. Crashes before you sign in, or while the switch is off, are not reported.
Usage analytics and crash reports are off until you switch them on with a single tick box beside the Terms and Privacy Policy notice, during setup and each time that notice is shown, or later in Settings. The app works the same either way.
We save your choice (on or off, and when it changed) with your account, so it is kept if you reinstall the app or sign in on another device. Nothing is collected before you have signed in and the saved choice is on.
When they are on, Google Analytics for Firebase records how the app is used: the screens you open (by screen name only), the features you use (for example adding a position, starting a ranking or opening a link to our terms), the choices you make in setup (for example your theme), when sessions start and how long they last, app updates and purchases (the product and price). It also records your device model, operating system, app version, language, approximate location (country, region and city, worked out from your IP address) and a random app instance ID.
Analytics never include names, email addresses, job descriptions, resumes, candidates' details, file names or criteria. They are not linked to your account, they do not use advertising IDs, and Google's advertising features are switched off.
What you send us, and our replies.
Our servers log each request: the IP address, the time, the address requested, the user and record IDs involved, and error details. Error details can include the name of an uploaded file, which is often the candidate's name.
The app keeps your sign-in session and your theme on your device. Your analytics choice is saved with your account. Files you download or share from the app are then under your control.
No advertising trackers, no advertising IDs, and no tracking across other apps or websites. Usage analytics and crash reports are collected only if you switch them on.
No location, contacts, camera, microphone, photos of faces or biometric data.
We do not sell personal data, and we do not share it for advertising.
The EU and UK General Data Protection Regulation (GDPR) requires a legal basis for each use of personal data (Article 6). For data we process for recruiters, the recruiter's company needs its own legal basis (see section 6).
Running your account and signing you in. Legal basis: contract (Article 6(1)(b)).
Screening and ranking resumes, suggesting criteria and creating downloads. Legal basis for the recruiter's own data: contract. Candidates' data: processed on the recruiter's instructions, as their processor.
Handling purchases, the free trial and credits. Legal basis: contract.
Keeping the service secure and preventing abuse. Legal basis: our legitimate interest in a reliable and secure service (Article 6(1)(f)).
Tracking the cost and reliability of scoring. Legal basis: our legitimate interest in running the service sustainably.
Understanding how the app is used and fixing crashes, to improve it (usage analytics and crash reports). Legal basis: your consent (Article 6(1)(a)).
Answering support requests. Legal basis: contract, or our legitimate interest in answering you if you are not a customer.
Keeping records the law requires, and responding to lawful requests from authorities. Legal basis: legal obligation (Article 6(1)(c)).
In India, we process recruiters' data for the purposes they gave it to us, which are signing up for and using the app, as the DPDP Act allows, and with their consent where the Act requires it.
We do not use resumes or job descriptions to train AI models, and our AI providers have agreed not to either.
Before the app first sends a job description or resume to our AI providers, it asks for your permission and names the providers. You can withdraw that permission in Settings. Without it, the app cannot generate criteria or score resumes.
Usage analytics and crash reports are optional and off until you switch them on. The app works the same either way. You can switch them off at any time in Settings. Collection then stops at once, and data already collected is deleted when its retention period ends (14 months for usage analytics, 90 days for crash reports).
When you upload resumes, you instruct us to store them, send them to our AI providers (TypeSafe, or Anthropic where we use it for scoring) to be scored, and show you the results. Under our Terms and Conditions, you are responsible for:
having the right to process each resume, and a legal basis for doing so;
telling candidates, in your own privacy notice, that you use AI-assisted screening, what it does, and that a person makes the decision (you may link to this policy);
having the ranking reviewed by a person who is able to disagree with it, and does (see section 7);
answering candidates' requests to see, correct or delete their data;
deleting resumes when you no longer need them. The app deletes only the original files automatically, 365 days after upload. It does not delete resume text, criteria or scores.
A recruiter uploaded your resume to consider you for a job, and that recruiter decides how it is used. To see, correct or delete it, contact the recruiter first. If you contact us instead, tell us which company you applied to. We will pass your request on to that recruiter and help them respond.
The full text of your resume, including your name and contact details, is sent to TypeSafe, or to Anthropic where we use it for scoring, to be scored.
Criteria. When the recruiter asks, or has automatic criteria switched on, Anthropic's Claude model reads the job description and suggests up to 10 must-have and 10 secondary criteria. The recruiter can edit, add, remove or mute any of them.
Scoring. For each resume, the app sends the job description, the resume text and the criteria to an AI model: TypeSafe's Jev model, or Anthropic's Claude model where we use it for scoring. The model rates how well the resume shows each criterion on five levels: 0 not evidenced, 1 weak or tangential, 2 partially met, 3 clearly met, 4 exceeds the requirement. If the job description and resume together are too long for the model (for Jev, more than about 100,000 characters), they are shortened to fit, and the rest is not read.
Ranking. Our server turns the ratings into a total score out of 100. Must-have and secondary criteria share the 100 points according to a weight the recruiter sets, and resumes are listed from the highest score to the lowest. A resume "meets all must-haves" when every must-have it has been scored on is rated 2 or higher.
It never rejects, shortlists, advances or contacts a candidate.
It does not check whether what a resume says is true.
It reads text only: no photos, video, voice or social media.
It does not hide anyone. Recruiters can see every candidate and open every resume, whatever the score. The "meets all must-haves" filter is off unless the recruiter turns it on.
Scores are estimates and can be wrong. Scanned resumes without a text layer cannot be read, and very long documents are shortened.
Text hidden in a resume, or wording copied from the job description, can push a score up.
We do not make decisions about candidates. Recruiters do. But if a recruiter treats the score as the decision, for example by rejecting everyone below a cut-off without reading their resumes, the law can treat that as a decision based solely on automated processing, and the recruiter's obligations under Article 22 apply. Recruiters should have a person read the resumes who is free to disagree with the ranking. Candidates can ask the recruiter to have a person review a decision, to give their own view, and to explain the decision.
As the Australian Privacy Principles require (APP 1.7 to 1.9):
Kinds of personal information used by the computer programs: the text of candidates' resumes, including contact details, work history, education, skills and anything else in them, together with the job description and criteria the recruiter provides.
Decisions made solely by a computer program: none.
Decisions where a computer program does something substantially and directly related to making the decision: recruiters' decisions about which candidates to review, shortlist or interview for a job. The program scores and ranks the resumes and shows whether each one meets the must-have criteria.
We use the companies below to run the app. Each one processes data only to provide its service to us, under terms that protect your data to the same standard as this policy.
What they do: run our servers, database, file storage and logs.
Data: everything the app stores.
Location: United States (Iowa).
What they do: sign-in, crash reports and usage analytics (both only if you switch them on).
Data: sign-in details, crash reports, and usage analytics.
Location: United States. For analytics, we have switched off Google's data sharing and advertising features, so Google processes the data only for us.
What they do: score resumes against the criteria with their Jev AI model.
Data: the job description, the resume text (including the candidate's name and contact details) and the criteria.
Location: United States. TypeSafe does not train AI models on this data. Its own subprocessors are listed at trust.typesafe.ai/subprocessors.
What they do: suggest criteria from a job description with their Claude AI model, and may also score resumes.
Data: the job description text and, where we use Anthropic to score resumes, the resume text (including the candidate's name and contact details) and the criteria.
Location: United States. Under its commercial terms, Anthropic does not train AI models on this data.
What they do: manage purchases, subscriptions and credits.
Data: a random user ID, purchase and credit records, and basic device and app details.
Location: United States.
Sign in with Apple, Google Sign-In, the App Store and Google Play handle your sign-in and payments under their own privacy policies. They are not our processors.
We disclose personal data if the law requires it, or where needed to protect our users, the app or others. If the business is transferred, for example to a company we set up to run it, or is merged or sold, personal data may pass to the new owner, who must keep to this policy. We will tell you before that happens.
We are based in India, and our servers and providers are in the United States. Data is stored in the United States and accessed from India by the people who run the service. If you are in the EU, the UK or another country that regulates transfers abroad, your data leaves that country.
When a recruiter's company sends us candidates' data from the EU, the UK or Switzerland, our Data Processing Addendum includes the European Commission's standard contractual clauses and the UK addendum to them.
Our providers' data processing terms include the same clauses. Google is also certified under the EU-US Data Privacy Framework.
We do not offer data storage in the EU.
Account details and settings: until you delete your account.
Sign-in details: deleted with your account.
Job descriptions, resumes (files and text), criteria and scores: until the recruiter deletes them or deletes their account. The original uploaded files are also deleted automatically 365 days after upload; the extracted text, criteria and scores are not.
Scoring records: until the account is deleted. Candidates' names and contact lines in them are erased as soon as their resume or job profile is deleted.
Purchase and credit records: RevenueCat keeps these after you delete your account, linked only to the random user ID. Ask us and we will delete them, unless we must keep them for tax, accounting or fraud prevention. Apple and Google keep their own purchase records.
Crash reports (if switched on): 90 days.
Usage analytics: detailed data for 14 months, then deleted. Summary reports that do not identify anyone may be kept longer.
Server logs: 30 days.
Database backups and recoverable file copies: deleted data remains in backups, and deleted files remain recoverable by our administrators, for up to 7 days.
Data sent to TypeSafe and Anthropic: kept by them for a limited time under their own retention terms, then deleted.
Support emails: as long as needed to resolve your request and to show how we handled it.
Go to Settings → Delete account. This immediately and permanently deletes your account, all your job profiles and job descriptions, all resumes (original files and text), criteria, scores and scoring records, and your sign-in account.
Email trust@tikeai.ventures from the email address on your account, with the subject "Delete my Propel Resume Screener account". We will confirm the request with you and delete the account within 30 days.
Purchase records with Apple or Google, and with RevenueCat, where they are linked only to a random user ID. You can ask us to delete the RevenueCat records too.
Server logs for up to 30 days, database backups and recoverable file copies for up to 7 days and crash reports (if switched on) for up to 90 days. These are then deleted automatically.
Usage analytics, if you had them on, for up to 14 months. They are not linked to your account, so we cannot pick out yours to delete them sooner. Your saved choice is deleted with your account.
Deleting your account does not cancel a subscription. Cancel it in the store:
iPhone or iPad: Settings → your name → Subscriptions.
Android: Google Play Store → profile icon → Payments & subscriptions → Subscriptions.
You can also delete a single resume or job profile at any time in the app.
Wherever you are, you can ask us to see, correct, export or delete your personal data, or to stop using it for a particular purpose. Email trust@tikeai.ventures. We may ask you to confirm the request from the email address on your account. Requests are free, and we answer within one month.
Candidates: for resumes a recruiter uploaded, see section 6.
Under the GDPR and the UK GDPR you have the right to:
access your personal data;
have inaccurate data corrected;
have your data erased;
restrict how we use it;
receive the data you gave us in a portable format;
object to uses based on our legitimate interests;
withdraw consent at any time, where we rely on it;
not be subject to a decision based solely on automated processing that significantly affects you (see section 7).
You can also complain to the data protection authority in the country where you live or work, for example the Information Commissioner's Office (ICO) in the UK.
Under the DPDP Act you can ask for a summary of your personal data and how it is processed; ask us to correct, complete, update or erase it; and nominate another person to exercise these rights if you die or become unable to. Raise any grievance with our Grievance Officer, Sree Priya, at trust@tikeai.ventures. We will respond within 30 days. If you are not satisfied with our response, you can complain to the Data Protection Board of India.
You can ask to access and correct your personal information. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (OAIC).
We do not sell or share personal information, as those terms are defined in the California Consumer Privacy Act. You can make the requests described above, and we will not treat you differently for doing so.
All connections to our servers are encrypted (HTTPS), and Google Cloud encrypts the data it stores.
Each recruiter can see only their own data. Access to our servers is limited to the people who run the service.
You sign in through Google or Apple, so we never handle your password.
No system is perfectly secure. If a breach affects your data, we will tell affected recruiters without undue delay and notify regulators where the law requires, for example within 72 hours under the GDPR, and the Data Protection Board of India.
Propel Resume Screener is for recruiting and workplace use by adults. It is not for anyone under 18, and we do not knowingly collect children's personal data.
The app does not use cookies, and does not use any technology for advertising. If you switch on usage analytics and crash reports, Google Analytics for Firebase and Crashlytics keep a random app instance ID on your device. The app also keeps your sign-in session and theme on your device. This page is hosted on Google Sites, and Google may set cookies needed to serve it, under Google's own privacy policy.
We will update this policy when our practices change and update the effective date at the top. If a change materially affects how we use your data, we will tell you in the app or by email before it takes effect.
Sree Priya, trading as Tike AI Ventures
3rd Floor Plot No. 7F, Raj Pinnacle, 6th Cross Phase 1, Doddanekundi Industrial Area, Bengaluru, Karnataka 560048, India
Email: trust@tikeai.ventures
Grievance Officer: Sree Priya
Related: Terms and Conditions · Data Processing Addendum