Privacy Policy
Here you can learn what personal data Loopiva processes, why we use it and what rights you have.
Controller
Langvis UG (haftungsbeschränkt), Floningweg 7A, 12107 Berlin, Germany, is responsible for processing personal data in connection with Loopiva.
The company is represented by its managing director, Marek Iwaszkiewicz.
You can send privacy requests to datenschutz@langvis.ai.
What this policy covers
Loopiva is an online service for interview training, feedback and evaluation. This privacy policy explains what data we process when you use the service and how we handle it.
Loopiva is not an employer or recruiting system. Its evaluations support your personal training and do not make binding decisions about hiring, suitability, health, personality, origin or similar characteristics.
Data we process
The data involved depends on the features you use.
- Account and contact data, such as your name, email address, sign-in, language and session data.
- Purchase and payment data, such as the package, credits, price, currency, order status and internal checkout, wallet and booking references.
- Interview and coaching data, such as answers, audio recordings, transcripts, feedback, evaluations and technical session metadata.
- Support data, such as contact requests, messages, processing status and related references.
- Technical operations, security and non-content quality telemetry, such as timestamps, request IDs, playback phases, latency, message lengths, error codes, provider or voice identifiers, rate-limit and abuse-prevention signals. This quality telemetry does not contain raw answers, transcript text, prompts, raw model output or raw audio.
Why we process data
We only process personal data where there is a legal basis for doing so.
- Contract performance under GDPR Article 6(1)(b): for accounts, sign-in, interview training, feedback, evaluations, credits and payments.
- Legal obligations under GDPR Article 6(1)(c): particularly for tax, accounting and required evidence.
- Legitimate interests under GDPR Article 6(1)(f): particularly for security, abuse prevention, error analysis, support traceability, payment recovery and legal defence.
- Consent under GDPR Article 6(1)(a) and section 25 TDDDG: for optional analytics and non-essential storage on your device.
How long we keep data
We only keep data for as long as it is needed for the relevant purpose or required by law.
- Raw interview messages are deleted 48 hours after a session is completed or cancelled.
- Raw coaching messages are deleted 15 minutes after a coaching block ends.
- Recorded input audio and temporary transcription files are deleted after transcription. A technical safety net removes any remaining files after one day at the latest.
- Non-content interaction data and derived audio summaries of evaluations are deleted after 90 days.
- Free mini-interview diagnostics record technical stages of recording, submission, transcription, message persistence, playback, completion and evaluation attempts, including timestamps, identifiers, lengths, durations, fixed error codes and available usage measurements. Based on our legitimate interests in reliability and support, these records are retained for up to 90 days without answer, transcript, audio, prompt or model-output content. Missing measurements remain unknown. Interview content is still deleted after 48 hours, including after errors.
- Financial, tax, purchase, payment and accounting evidence is kept for the applicable statutory periods, generally until the end of the eighth calendar year and, for certain records, until the end of the tenth calendar year.
Your rights
To exercise your rights, contact datenschutz@langvis.ai.
- Access to your personal data.
- Correction of inaccurate data.
- Erasure, unless statutory retention duties or other overriding reasons apply.
- Restriction of processing.
- Data portability.
- Objection to processing based on legitimate interests.
- Withdrawal of consent with effect for the future.
- A complaint to a data-protection supervisory authority, in particular Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59-61, 10555 Berlin, Germany; mailbox@datenschutz-berlin.de.
Providers, payments and AI processing
Loopiva uses AWS in the eu-central-1 region for hosting, databases, object storage, logs and email delivery. Where a relevant feature is used, AWS also processes data through Bedrock for language models, Transcribe for speech-to-text and Polly for speech output.
OpenAI may receive text to generate speech output when you use an OpenAI voice.
Stripe processes checkout, payment, tax and payment-method data. PayPal may be offered as a payment method within Stripe Checkout. In that case, payment handling still runs through Stripe and PayPal receives the data required for the selected payment method.
Loopiva does not use customer interview content for model training, fine-tuning or general product improvement. We do not perform emotion recognition, biometric identification or inferences about health, origin, accent, personality or suitability for employment.
Cookies and similar storage technologies
Essential cookies and storage technologies secure your sign-in, store your language and privacy choice, and support checkout, product state, error handling and the prevention of duplicate telemetry events.
Optional product and web analytics remains disabled until you explicitly consent. After consent, Loopiva loads Cloudflare Web Analytics from static.cloudflareinsights.com to measure page views, referrers, approximate country and browser information, and page performance. Beacon data is sent to cloudflareinsights.com.
Cloudflare states that Web Analytics uses no cookies, does not collect or use visitors’ personal data, does not track individual users across customer sites and does not log query strings. It retains unsampled beacon data for seven days and provides dashboard access for the previous six months using aggregated and sampled data after the initial period. Loopiva does not use tools that record complete sessions.
Transfers outside the EU and EEA
Data may be processed outside the EU and the European Economic Area where providers, their subprocessors, support access or processing through Cloudflare, Stripe, PayPal or OpenAI require it.
Loopiva relies on the applicable contracts, data-protection terms, transfer clauses and supplementary safeguards for such transfers.
Data you need to provide
Without an email address and authentication data, we cannot provide an account. For a purchase, Stripe and, where applicable, the selected payment method require the necessary payment data.
We only need interview answers, audio and transcripts when you use the relevant interview, speech-input, feedback or coaching features. Please do not provide unnecessary personal data about third parties or particularly sensitive data.
Minimum age
Loopiva is intended exclusively for people aged 18 or older. Minors are not permitted to use the service.
Security and automated evaluations
We use technical and organisational measures to protect personal data against unauthorised access, loss, misuse and unauthorised alteration.
Loopiva creates automated training evaluations and feedback. These results are for your personal preparation and have no legal effect. Loopiva does not make automated decisions about hiring, rejection, creditworthiness, health or similarly significant consequences.
Optional campaign and journey measurement
For later campaign attribution, initially unknown normalized UTM names and values may be retained with their capture time and related measurement contributions for up to 90 days. Any shorter existing period still applies; registration and retries do not extend it. New taxonomy values can correct the attribution of already measured steps. The original measurement is preserved; full URLs and form values are not stored for this purpose.
Only with your analytics consent do we associate campaign parameters and measured steps using a random first-party cookie identifier. Steps include landing-page visits, registration links, opening and starting the form, social sign-up entry, account creation, activation, first interview start and completion, and purchase. Registration links the journey to the new account. We do not collect form values or interview content for this purpose or merge devices.
A journey covers at most 30 days from entry. Its details and account link are retained for at most 90 days and aggregate counts for at most 13 months. Existing account-level campaign attribution may remain for up to 180 days. Processing uses our AWS hosting; this internal report sends no additional data to Google.
The legal bases are GDPR Article 6(1)(a) and section 25(1) TDDDG. You can withdraw consent at any time in the privacy settings in the footer. Further measurement stops and reachable optional links are deleted; existing aggregate counts remain within their retention period. You can use the product without this consent.
Google Ads conversion measurement
Allows Google to connect ad clicks with account creation, activation and first interview use. Technical browser and click data and pseudonymous success signals are processed, not interview content or email addresses; no personalised advertising. Technical page-view and consent signals also go to Google, with fixed page paths (including login and dashboard) and permitted advertising and campaign parameters. Google cookies may be used for up to 30 days after each permitted write. A short-lived identifier lasts five minutes at a time; a technical counter initially lasts up to 30 days and up to 90 days after conversion-related updates. These periods may restart, so the total duration may be longer. Without another visit, local data may remain on your device longer. Independent of product analytics and revocable here at any time.
The recipient is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, acting as an independent controller. Our advertising measurement relies on your consent under GDPR Article 6(1)(a); storing or accessing information on your device relies on section 25(1) of the German TDDDG. You can use Loopiva without this consent.
Google processes technical connection data, such as the IP address; transmission starts only after your separate consent. Processing outside the EU/EEA is possible. Our pending measurement receipts expire after 24 hours and our duplicate-prevention data after at most 30 days without renewal. Separate limits apply to Google local storage (_gcl_ls): gsid_dc lasts five minutes at a time; gcl_ctr initially lasts at most 30 days and at most 90 days after permitted conversion-related updates. Renewal of the same still-valid supporting data and Google cookie writes lasting up to 30 days each are allowed; these are not maximum periods from the first creation. Other Google storage entries receive no blanket renewal exception. Expired or invalid data is removed before reuse; without another visit, LocalStorage data may physically remain longer. Withdrawal or expiry of your consent, valid for at most 365 days, ends use and removes accessible optional advertising data. A new consent period does not inherit old identifiers or measurement receipts. Data already sent to Google is not automatically deleted and remains subject to Google’s privacy rules.
Your advertising consent lasts at most 365 days. Loopiva records a random reference, time, choices, language and notice version, and receipt of withdrawal where applicable. The record contains no account ID, email, IP address or interview content. It is used for accountability and defending legal claims (GDPR Articles 7(1) and 5(2), and Article 6(1)(f) for subsequent retention). It is scheduled for deletion three years after withdrawal or expiry. Physical deletion is asynchronous, normally within a few days; backups then expire within 35 days. If withdrawal cannot be delivered, the original expiry remains the retention anchor; measurement on your device stops immediately. A withdrawal retry retains the reference for at most 24 hours.
Google: processing on partner websitesGoogle: international data transfers
Google may also process data in the USA. For transfers to certified US entities, Google identifies the EU-US Data Privacy Framework; where it does not apply, Google’s applicable data-protection terms provide for standard contractual clauses. Google provides further information about these safeguards.
Google: international data transfersAccount closure and erasure
You may request closure and erasure of your account. Once confirmed, product access is blocked immediately; a self-initiated closure may be withdrawn within 30 days after re-authentication.
After finalization, direct account data and ordinary product data are erased or anonymized. Financial or evidentiary records required by law may remain purpose-limited, access-restricted and pseudonymized until their deadline under GDPR Article 17(3) and, in particular, German Commercial Code section 257. If you cannot access your account, contact datenschutz@langvis.ai.
