Notificare privind limba
Această politică este furnizată momentan doar în limba engleză pentru a asigura precizia juridică. Navigarea și funcționalitățile platformei rămân în limba selectată de tine.
Legal / Privacy policy
Last updated
Privacy policy
Built around transparency, data minimisation, and user control under the principles of the European GDPR. Your account and the career content you create remain under your control.
Who is responsible for your data
Lyrra, a Dutch sole proprietorship registered under KVK number 99866161, is the controller of personal data processed for this service. Contact support@lyrra.io for privacy requests. See our Legal Information for registration details.
Why we process personal data
- Account authentication, saving and managing your career content, and features you request: performance of our contract with you (GDPR Article 6(1)(b)). Account information is needed to provide these features; career content is supplied at your choice.
- Preventing abuse, enforcing request limits, and investigating security incidents: our legitimate interest in protecting the service and its users (Article 6(1)(f)).
- Records we must keep for tax, accounting, or other legal requirements: compliance with legal obligations (Article 6(1)(c)).
- Optional product analytics: with your consent, we use PostHog EU to understand how features are used and improve the service (GDPR Article 6(1)(a)). You can refuse or withdraw consent through Privacy preferences without losing access to Lyrra.
Browser permission for an optional feature, such as the microphone, lets you control access to that device capability. Where processing relies on consent, you may withdraw it without affecting processing that was lawful before withdrawal. Lyrra does not make recruitment decisions or decisions with legal or similarly significant effects about you through the capture feature.
1. Optional analytics and privacy
Lyrra is designed with a strict privacy-by-default architecture in accordance with the European GDPR / AVG.
We use PostHog EU for optional product analytics only after you agree. CookieHub manages your consent choices. You can accept or reject optional analytics, or withdraw consent, through Privacy preferences in the footer and account settings. Session replay is currently disabled. We do not use this data for advertising or track you across unrelated websites.
To maintain platform security and protect against bots, we utilize Cloudflare Turnstile. This is a functional security tool that does not utilize tracking cookies or process data for marketing purposes.
What optional analytics collects
With your consent, PostHog processes feature actions, task outcomes, page categories, approximate device category, interface language, plan category, approved campaign labels, timing and limited technical error information. Events include timestamps and pseudonymous browser, session and analytics identifiers. Account activity can be associated with your Lyrra account. These records are personal data, not anonymous statistics.
We use this information to understand feature adoption, task completion, reliability and conversion, and to improve the service. We exclude document text, interview answers, prompts, notes, salary figures, signatures, payment details and authentication tokens from analytics event content. Session replay is disabled. Any future introduction requires separate informed permission.
When you withdraw consent, collection stops in the browser immediately. Once your withdrawal reaches our server, we queue deletion of the associated analytics. Account deletion also queues erasure. PostHog processes deletion asynchronously; submission is not proof of completion. If you are offline, the browser keeps collection off and retries synchronisation when connectivity returns. Already transmitted requests cannot be recalled.
We limit each analytics identifier to a 90-day collection window and schedule deletion at its end, or earlier on withdrawal or an applicable erasure request. The daily deletion process submits and checks pending work. Physical removal depends on PostHog completing its asynchronous process; the plan’s reporting window is not a deletion guarantee. Minimal completed deletion records are kept for 30 days for verification. Renewed consent uses a fresh identifier. We do not join visitor history to a signed-in account in this implementation.
Analytics is sent to PostHog’s EU service. EU storage does not exclude international transit or access by subprocessors; see International processing below. To request access, correction or deletion, contact support@lyrra.io. The account download covers saved career content; analytics and consent records are handled through this support route. We normally respond to rights requests within one month, subject to the lawful extension and notice rules.
Cookie choices and consent records
Optional analytics relies on consent (GDPR Article 6(1)(a)). Refusing does not prevent you from using Lyrra. CookieHub processes consent preferences and evidence on our behalf. Its consent log includes a consent token, choice and notice information, time, URL and technical metadata. CookieHub documents 12-month log retention and up to 90 days for deleted data to expire from encrypted backups. We keep a server-side history of account and visitor analytics choices for 12 months, including the policy version and time, to meet our accountability and consent-evidence obligations under GDPR Articles 5(2) and 7(1). This evidence is restricted to authorised personnel and kept separately from optional usage analytics.
Necessary storage supports authentication, security and privacy choices. A two-minute consent cookie tells our server your effective browser choice. Signed-in preferences are stored with your account. After visitor opt-in, a protected browser cookie allows us to retrieve the visitor analytics identity and honour withdrawal without accepting arbitrary identifiers. It lasts up to 180 days and is cleared after withdrawal is saved; the analytics collection window remains 90 days. PostHog also uses localStorage and sessionStorage after consent; these identifiers are cleared when collection is refused. CookieHub asks you to renew your choice after 180 days.
We remember interface settings when you select them: your language for up to 365 days, your document-library view for up to 365 days, and your sidebar state for up to 7 days. Your chosen theme, tracker layout, signature input method and floating-checklist preference use persistent local storage until changed, cleared or, for the floating panel, closed. Simply loading a page does not save a default theme or language. These settings provide the interface you requested; they are not analytics and are not removed when you reject analytics.
Supabase authentication cookies keep you signed in and refresh your session. Their maximum browser lifetime is 400 days, renewed with the session; signing out clears authentication. Document, profile, interview and practice editors also use tab/session storage to continue work and recover pending actions. Browser session restoration can preserve that storage. Unsaved notes and canvas recovery use account-scoped local storage without a fixed time expiry, until saved, discarded or browser data is cleared. Signing out resets the visible notes/canvas workspace but preserves recovery for the same account; it does not erase every functional storage item. None of this unfinished content is included in analytics.
Withdrawing does not make earlier lawful processing unlawful. It does require stopping consent-based processing and deleting the relevant personal analytics unless a separate lawful purpose requires retention. This exception does not allow us to switch analytics silently to another legal basis.
See CookieHub’s retention information and PostHog’s subprocessors. The cookie declaration in Privacy preferences describes the deployed storage inventory.
2. Artificial intelligence & your data
Our application utilises advanced AI models to process resumes and facilitate simulations.
- AI training privacy
Lyrra does not use your resumes, documents, notes, transcripts, prompts, or generated content to train AI models.
- Secure transit
Your data is transmitted securely to the AI API only when you purposefully initiate an analysis or simulation.
3. Voice features
Voice interview features require your permission to use the microphone. Speech-recognition services convert your speech into text, and Lyrra receives the resulting transcript when you submit it.
Lyrra does not store raw microphone recordings in the interview flow. When spoken responses are enabled, voice service providers process generated response text to produce audio. Generated audio is not stored as career content.
4. Minimal data collection
We subscribe to the principle of data minimisation, collecting only what is strictly necessary:
Account & auth
We collect your email address for secure authentication. Payment information is securely handled by Stripe. We never touch or store your raw credit card data.
Career portfolio
Resumes, cover letters, and notes that you explicitly create. You maintain full ownership over this content at all times.
5. Lyrra Capture Chrome extension
Lyrra Capture receives temporary access to the active browser tab only after you explicitly click the extension. It reads job-listing fields such as the company, position, location, salary, description, source, and URL so that you can review them before saving a tracker entry.
Automatic capture is disabled on linkedin.com, indeed.com, workopolis.com, simplyhired.com, resume.com, and their subdomains. On these sites, Lyrra does not inject its extraction script or read page content; it displays an empty manual form. This is a fixed list, not an automatic check of other sites’ terms. Only save information you are entitled to use, including when entering it manually.
We do not collect unrelated browsing history, monitor tabs in the background, submit applications, sell extension data, or use captured information for advertising. Page content is not sent to Lyrra until you choose to save it. Authentication tokens are revocable, are kept in Chrome session storage, and expire from the device when the browser session ends.
Saved tracker fields are sent to Lyrra over encrypted HTTPS. Supabase processes account, authentication, database, and storage data; Vercel and Cloudflare provide hosting, delivery, and security services. Saved role context is sent to Mistral only if you later initiate a related AI feature, and generated response text is sent to voice service providers only if you initiate supported voice playback. Stripe does not receive captured listing content.
API requests also carry security metadata such as your IP address, browser user agent, and request origin. We derive a hashed identifier from these values for abuse prevention. Upstash processes rate-limit identifiers and request counters, which may also be keyed by your account ID. The extension rate limiter uses a 60-second sliding window with expiring counters and analytics disabled. This short rate-limit window does not describe the retention of hosting or security logs, which are separate records. Hashing these identifiers does not make them anonymous.
Lyrra personnel do not read extension-derived user data except with your explicit consent for a specific support request, when required to investigate security or abuse, to comply with law, or after the data has been aggregated and anonymised for permitted internal operations.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
6. Your privacy rights
We grant all Lyrra users the highest standard of privacy rights outlined by the GDPR:
Right to portability
Download your career, practice, canvas, interview, negotiation, and tracker data in a machine-readable ZIP/JSON format via Data Management.
Right to be forgotten
Permanently delete your account directly through your dashboard. This removes your account data and user-owned avatar and signature files, and cancels or deletes billing data where applicable.
You also maintain the Right to Access, Right to Rectification, and the Right to Withdraw Consent at any time.
Where applicable, you may request restriction of processing and object to processing based on legitimate interests. You may complain to the Dutch supervisory authority, the Autoriteit Persoonsgegevens, or the supervisory authority where you live, work, or believe an infringement occurred. Contact support@lyrra.io to exercise your rights; we may need to verify your identity.
Purchase confirmations and support
We use Resend to send purchase confirmations and refund-request acknowledgments to your verified account email. Resend receives the recipient address, sender, subject, confirmation text, purchase references and amounts, and the applicable terms attachment. It also processes delivery, bounce and technical sending information so authorised staff can investigate delivery problems. These transactional messages support our contract and statutory information obligations; they do not depend on optional analytics consent.
We use ClickUp (Mango Technologies, Inc.) to organise support and refund review. A refund copy includes your account identifier and email, the request type and reference, receipt time, purchase name, amount and payment reference, and a link to a protected Lyrra review page. We do not copy AI prompts, interview content or raw usage records into these refund tasks. Authorised owner/support staff review billing and usage information in Lyrra. ClickUp and Resend act as processors under their applicable data-processing agreements; authorised provider personnel and subprocessors may access data to operate and secure these services.
Resend delivery records are used for sending and investigation, with retention governed by the configured provider plan and applicable legal holds. Immutable confirmations and required contractual evidence remain in Lyrra separately. Contact support@lyrra.io for access, correction, deletion or current provider-retention details. International access or transfers use the safeguards described below. See the Resend DPA and ClickUp DPA.
7. Data retention & lifecycle
We retain your account and saved career content to provide the service until you delete the content or close your account. Signing out or uninstalling Lyrra Capture does not delete tracker entries already saved in your Lyrra account.
Deletion and exceptions: Use Data Management to request account deletion. Records needed for legal obligations or a specific security investigation may need to be retained for those purposes. Backup and infrastructure-log retention is separate from removal of active account records. Contact support@lyrra.io for information about records retained in your case. We do not promise automatic deletion after a fixed period of account inactivity.
International processing
Our service providers operate internationally. Processing or access outside the European Economic Area may occur depending on the service and its configuration. Such transfers require an applicable GDPR transfer mechanism, such as an adequacy decision or the European Commission’s standard contractual clauses, with additional safeguards where required. Contact support@lyrra.io to request information about the transfer arrangements and a copy of applicable safeguards for your data.
8. Contact us
Data protection inquiries
For any inquiries regarding your data, privacy, or GDPR compliance.