Hirova privacy policy
Effective date: 2026-10-13
Who is responsible
Hirova is operated by Marcos Jaen, an individual business established in Spain. We are the controller responsible for your personal data when you use Hirova.
- Location: Langreo, Asturias, Spain.
- Privacy email: privacy@hirova.app. Support email: support@hirova.app.
- Hirova is not offered in the United Kingdom, so we have not appointed a UK representative.
This policy covers the Hirova iOS app, the emails it sends and our support communications. Apple and Google explain their own processing in the policies linked below.
What we collect
We receive information you provide and information needed to run the app:
- Account information: your email address, your sign-in method and the account identifier your sign-in provider gives us. Sign in with Apple may give us a private relay address instead of your usual email. From Google Sign-In we keep only the verified email address and Google's account identifier, not your name, photo or Google tokens. If you use Hirova before signing in, we create an anonymous guest account that expires after 24 hours.
- Resume content: contact details for the letterhead, employment history, education, qualifications, skills and achievements, the facts you confirm, job postings you add, your interview answers, drafts, resume versions, cover letters, the applications you track and the PDFs you save.
- Imported resumes: when you import a file, Hirova reads it on your iPhone. Text PDFs are read with Apple's PDFKit, and scans and photos with Apple's on-device text recognition (Vision). The file is not uploaded and is not sent to AI. We receive only the text you review in the app. Contact details found in it are kept for the letterhead only.
- Subscription information from Apple and RevenueCat: transaction identifiers, the product, purchase and renewal dates, trial eligibility, subscription status, currency and price. We do not receive your payment card details.
- Crash and diagnostic reports: if you turn on sharing with app developers in your iPhone settings, Apple gives us crash logs and diagnostics through App Store Connect. They include the app version, device model, iOS version and the state of the app when it failed, and are not linked to your Hirova account. Hirova has no crash-reporting SDK of its own.
- TestFlight feedback: if you test a beta through TestFlight and send feedback, Apple passes us your comments, any screenshots you attach, crash details, your device details and the email address of your TestFlight account, so that we can reply and fix the problem.
- Technical and security information: request times, the route called, response codes, error categories, app version and security events. Cloudflare processes your IP address to deliver requests and to limit sign-in attempts. Our application logs exclude your IP address, resume content, interview answers, sign-in codes and AI prompts or responses.
- AI usage counts: for each AI request, the model, the number of tokens and an estimated cost, without any content. We use them to enforce fair-use limits.
- Your privacy choices: whether you allowed AI processing and weekly suggestions, the notice version you saw and when you chose.
- Support messages and anything you choose to include in them.
We do not ask for your address book, precise location or advertising identifier. We do not sell personal information, share it for cross-context behavioural advertising, or use your documents to train our own or anyone else's AI models. We do not send your resume to employers or submit applications for you. Hirova has no analytics or advertising SDKs.
Please use your own information. Remove other people's private information from job postings and resumes before you add them. Do not include government identification numbers, financial account details, health information, racial or ethnic origin, political opinions, religious beliefs, trade union membership, information about sex life or sexual orientation, biometric or genetic data, or criminal-history information. Hirova does not need these details. If we find such content, we restrict its use and remove it unless the law requires otherwise. Contact us if you need help removing it.
Why we use data and our legal bases
The following bases apply under the EU GDPR.
| Purpose | Information used | Legal basis |
|---|---|---|
| Create and secure your account, save and edit documents, produce PDFs, export your data and provide the support you ask for | Account details, documents, support messages and essential technical information | Performance of our contract with you, Article 6(1)(b) |
| Extract facts from text you provide, run the AI interview, write and tailor resumes and draft cover letters when you ask for these functions | The text needed for the request | Performance of our contract, Article 6(1)(b). We also ask your separate permission before sending personal data to the AI provider, as explained below |
| Manage purchases, restore access and keep subscription entitlements and usage limits | Account and subscription identifiers, transactions, entitlement status and AI usage counts | Performance of our contract, Article 6(1)(b) |
| Create optional weekly suggestions and send the weekly email | Your confirmed resume facts, your choices and your account email | Your consent, Article 6(1)(a). This is optional and separate from sign-in and purchase |
| Protect accounts, prevent fraud and abuse, diagnose faults and keep the service reliable | Limited technical information and security events | Our legitimate interests, Article 6(1)(f), in protecting users and running a secure service. We keep the data used to a minimum |
| Keep tax and accounting records, answer valid legal demands and handle privacy requests | Necessary transaction, correspondence and request records | Compliance with legal obligations, Article 6(1)(c) |
| Establish, exercise or defend legal claims and show which privacy choices you made | Necessary correspondence, transaction and choice records | Our legitimate interests, Article 6(1)(f), and legal obligations where they apply |
You need an email address or a supported sign-in to create an account, and the relevant facts to create a resume. You may leave optional fields blank. Without the content a function needs, we cannot perform it. Saying no to weekly suggestions does not affect the rest of your account.
We do not rely on the contract basis to intentionally process the sensitive categories listed above. Your AI permission is not permission to process sensitive information or to use data for unrelated purposes.
AI providers
Hirova's AI features use OpenAI's API. Requests reach OpenAI through Cloudflare AI Gateway, and Cloudflare bills us for them. The model is GPT-6 Luna. OpenAI and Cloudflare act as our processors (see the table of providers below). We will tell you before a change of AI provider affects your choices, and ask again where the law requires it.
We send only the text needed for your request, such as work history, education, skills, interview answers, resume drafts and a job posting. Hirova never sends your email address, phone number or postal address to the AI, and leaves out your name and personal links. Facts you write in free text may still identify you, so review them before sending. Cloudflare passes the request to OpenAI and returns the response to us.
Your content is not used to train OpenAI's models. We use OpenAI's API without storing responses for later retrieval, and our AI Gateway keeps no request logs and no cache of your content. We have enabled Cloudflare's zero-data-retention routing for our gateway, but Cloudflare has not yet confirmed in writing that it applies to this model. Until it does, we describe OpenAI's standard API terms: OpenAI may keep requests and responses in abuse-monitoring logs for up to 30 days, or longer where required by law or needed to protect its service or others from harm. We will update this policy if the zero-retention route is confirmed.
Your AI choice
Before your first AI request, the app explains what will be sent and asks you to allow it or choose "Not now". Nothing is sent to the AI until you allow it. You can still use Hirova without AI: you can import, write and edit your resume by hand, export it and delete it.
You can turn AI processing off at any time in Settings > AI > AI processing. This stops new AI requests, including weekly suggestions. We check your current choice on our server before every request. Turning it off does not undo requests already processed. Withdrawing consent does not affect processing that was lawful before you withdrew it.
AI can produce inaccurate, incomplete or biased content. Review and correct every draft before you use it; the app labels drafts "AI-generated draft. Review before use." PDFs you export carry a machine-readable marker that they contain AI-generated text, as the EU AI Act requires. The marker records the AI system and model, never your name or content. We use AI to help you write. We do not make recruitment decisions, rank you for an employer or make decisions about you that have legal or similarly significant effects.
Weekly suggestions and email
Weekly suggestions are optional, off by default and available with Pro. If you turn them on, once a week Hirova sends selected facts from your resume to the AI provider to propose edits, even when you are not using the app. Our background scheduler, which runs on Cloudflare, starts this job and checks both of your AI choices before every request. You review each suggested edit in the app; nothing changes your resume until you accept it.
If you also turn on the weekly email, we email your account address when suggestions are ready. The email says only how many edits are waiting and contains an unsubscribe link that turns it off in one step. Turn the email or the suggestions off in Settings > AI. Sign-in codes, account-deletion confirmations and other essential service emails are not marketing and are still sent.
Service providers and other recipients
Providers acting as our processors work under data-processing terms and may use their own authorised subprocessors.
| Provider | What they receive and why | Role and further information |
|---|---|---|
| Cloudflare, Inc. and its contracted affiliates | Everything Hirova stores (D1 databases and R2 storage), app requests and responses, AI requests on their way to OpenAI through AI Gateway, PDF rendering in Cloudflare Containers, the background scheduler, network and security information, and your email address and messages for sign-in codes, the weekly email and deletion confirmations through Cloudflare Email Service, and messages you send to support@, privacy@ or dev@hirova.app, which Cloudflare Email Routing forwards to the developer's private mailbox | Processor. Customer DPA and subprocessors |
| OpenAI Ireland Ltd., with OpenAI OpCo, LLC and authorised service providers where applicable | The text needed for each AI request: resume facts, job postings, interview answers and instructions | Processor for API customer data under the OpenAI DPA. See API data controls and subprocessors |
| RevenueCat, Inc. | An app-specific user identifier, transactions and subscription status, to verify purchases, grant access and restore purchases | Processor under its DPA. RevenueCat never receives resume content or interview answers |
| Apple, including the entity responsible for your App Store storefront | Sign-in, purchases, subscription management and refunds. Where a US state law requires it, the age range you choose to share through Apple's Declared Age Range. Crash and diagnostic reports, only if you choose to share them with app developers in your iPhone settings or through TestFlight; Apple passes them to us through App Store Connect, together with TestFlight feedback you choose to send | Independent controller for its own services. Sign in with Apple privacy and App Store privacy. Reading imported files on your iPhone with PDFKit and Vision sends nothing to Apple or to us |
| Google, including the entity responsible for your Google account | Your sign-in request and the identity information you authorise through Google Sign-In | Independent controller for its Google account service. Google privacy policy and Sign in with Google |
| Purelymail (Add Rabbit LLC), which hosts the developer's private mailbox | Messages you send to support@, privacy@ or dev@hirova.app, with your email address, after Cloudflare Email Routing forwards them | Processor. Privacy policy and terms |
We may also disclose the information needed to professional advisers bound by confidentiality, or to authorities when the law requires it. If the business is transferred, we will protect your data, tell you about the new controller and explain any new choices before your data is used for a materially different purpose.
International transfers
We operate in Spain, but our providers may process data in the United States and other countries. European hosting settings do not by themselves guarantee that every support, email, AI or security operation stays in Europe.
For transfers outside the European Economic Area, we rely on an adequacy decision or approved contractual safeguards. For an eligible US recipient with an active certification covering the transfer, this may be the EU-US Data Privacy Framework. Otherwise we use the European Commission's standard contractual clauses, with transfer assessments and additional safeguards where needed. Contact us for information or a copy of the relevant safeguards, with confidential details removed.
How long we keep information
| Information | Retention rule |
|---|---|
| Account, profile, confirmed facts, documents, job postings, applications and interview answers | While your account is active, unless you delete them sooner. After 24 months without you using the app, we email you and give you 30 days to return or export your data before we delete the inactive account. We do not delete an account under this rule while a paid subscription is active |
| Guest accounts | Up to 24 hours, unless you sign in and keep the content in your account |
| Imported files | Not received. Hirova reads them on your iPhone and receives only the text you review |
| PDFs | A PDF you save stays with your documents until you delete it or your account. Unsaved PDFs are deleted within 24 hours |
| Data exports | The JSON file we prepare for Export my data is deleted within 24 hours |
| Sign-in codes | Expire after 10 minutes and are removed after use or expiry. We do not write codes to logs |
| AI usage counts | 62 days, or until your account is deleted if sooner |
| Routine security and diagnostic logs | Up to 30 days. Records needed to investigate a specific incident may be isolated and kept until that investigation and any legal retention requirement end |
| Crash reports and TestFlight feedback in App Store Connect | Kept by Apple for the period Apple sets as controller. We do not copy them into our own systems, except a minimal extract needed to fix a specific problem, deleted when it is fixed |
| Deleted accounts and content | Access ends as soon as you confirm deletion. We remove the data from our active systems within 30 days and confirm by email when this is done. We keep a record that the account was deleted, without its content, so a restored backup cannot bring it back |
| Backups and recovery copies | Never used for ordinary access. Our database's point-in-time recovery keeps past versions for up to 30 days, and every recovery copy expires within 35 days after the data leaves our active systems. Every copy of deleted data is therefore gone at most 65 days after your request. If we ever restore a backup, we reapply all deletions before normal service resumes |
| Privacy-choice and rights-request records | While your account exists and up to 3 years after it ends, to show which choices you made and how we handled requests. These records never contain your resume or interview text |
| Ordinary support correspondence | Up to 12 months after a request is closed, unless needed for an unresolved dispute or legal obligation |
| Tax and accounting records | Generally 6 years from the relevant accounting entry, longer only where a specific legal obligation, proceeding or interrupted limitation period requires it. We keep only the transaction details needed |
Where Spanish law requires data to be blocked rather than destroyed at once, we isolate the minimum necessary records, restrict them to competent authorities and the handling of liabilities for the relevant limitation period, and then destroy them. A legal hold does not justify keeping your whole resume.
OpenAI's abuse-monitoring period is explained in AI providers. Apple and Google keep data for their own services under their own policies. Deleting Hirova does not delete your Apple or Google account, cancel an Apple subscription or remove files you have already exported to your device or shared elsewhere.
Your rights and choices
In the app you can edit or delete saved information, turn AI processing and weekly suggestions on or off, and use Settings > Account > Export my data to download a machine-readable JSON copy of your account, documents, facts and choices, including a list of your saved PDFs. If you cannot sign in, contact privacy@hirova.app. Where the law provides, you can request access, correction, erasure, restriction and portability, object to processing based on legitimate interests, and withdraw consent. You can object to direct marketing at any time without giving a reason.
To delete your account, use Settings > Account > Delete account. If you last signed in more than a day ago, we ask you to sign in again first. You do not need to contact support or cancel a subscription first. The deletion screen links to Apple's subscription settings, because deleting your account does not cancel an Apple subscription.
We normally respond to rights requests within one month. If the law allows an extension because a request is complex or we receive many requests, we tell you within the first month and explain why. We do not charge for ordinary requests or treat you differently for exercising your rights. Authorised agents may contact us, subject to appropriate verification.
You can complain to Spain's Agencia Española de Protección de Datos or another competent data-protection authority, including the one where you live or work. You do not have to contact us first.
For US residents, the categories, purposes, recipients and retention rules above are also our notice at collection. We do not sell or share personal information for targeted advertising. If a state privacy law gives you an additional right or a right to appeal a denied request, email privacy@hirova.app with "Privacy appeal" and we will handle it under that law.
Age limit
Hirova is for people aged 16 and older, and the App Store lists it accordingly. The app does not ask for your age or date of birth. Where a US state law requires apps to use the App Store's age information (Texas now; Utah from 6 May 2027 and Louisiana from 1 July 2027), Hirova asks Apple through its Declared Age Range feature before you start or sign in. Apple then shows its own prompt, and you choose whether to share an age range. We use the answer only to apply that law, on your iPhone, and we do not store it or send it to our servers. If it shows that you are under 16, Hirova stops and deletes what it kept on your iPhone. The iPhone then keeps only a marker that keeps Hirova stopped, even after reinstalling; it holds no age and is never sent to us.
We do not knowingly collect personal information from anyone under 16. If we learn that a younger person has an account, we stop processing and delete the information, except records the law requires us to keep. Please contact us if you believe this has happened. People aged 16 or 17 should use the app with a parent or guardian's involvement where local law requires it. Hirova has no advertising or profiling, and weekly suggestions are off unless you turn them on.
Security and policy changes
We use access restrictions, encryption in transit and at rest, short-lived sign-in codes and sessions, content-free logs and documented incident procedures. No system can promise absolute security. We will notify affected people and authorities when a personal-data breach requires it.
We update this policy when our practices or legal obligations change. We publish the new effective date and give notice of material changes in the app or by email. A policy update does not replace a consent we must ask for a new purpose or a materially changed AI disclosure.