Privacy Policy

Who is responsible

Loopify is owned and operated by Mario Martinez in Spain. For privacy questions or requests, email support@loopify.amberwake.com.

Information Loopify handles

• Account and access data: your email address, magic-link records and session records. Loopify uses passwordless email access and does not ask you to create a password.
• Learning data: selected languages, answers, lesson activity, vocabulary, progress and settings needed to provide and restore your learning experience.
• Content you provide: words, sentences, feedback and audio you choose to submit when using relevant learning or pronunciation features.
• Technical and security data: app and device information, request information such as IP address and approximate location derived from it, and service logs needed to operate, diagnose and protect Loopify.
• App usage and diagnostics: application lifecycle events, installation or device identifiers, crash reports and related diagnostic information. This information helps us understand use of the app and investigate faults.
• Purchase data: app-store transaction and entitlement information associated with your Loopify account. Loopify does not receive your full payment-card details.

Why it is used

Information is used to provide accounts and magic links, deliver lessons and audio, save and restore progress, check purchase access, answer support requests, prevent abuse, diagnose faults and comply with applicable obligations. Processing is based on providing the service you request, your consent for sharing text or recordings for AI processing, legitimate interests in security and reliable operation, and legal obligations where applicable.

Service providers

Loopify uses PostgreSQL for application data; Amazon Simple Email Service (SES) to deliver account emails; Google services for storage and app learning features such as audio and language processing; RevenueCat and the relevant app store to manage purchases and entitlements; Sentry for error diagnostics; and infrastructure providers to run and secure the service. These providers may process information in the countries where they operate.

Dictionary and written exercises

Some dictionary requests and written-answer checks use Google Gemini to generate definitions, translations, grammar information or feedback. Before an operation that may send your text for AI processing, Loopify asks for permission to share the submitted text together with the relevant exercise and language context. You can cancel without submitting that text for AI processing. Existing dictionary entries can be viewed without generating a new entry.

Words, phrases and generated entries submitted through dictionary generation may become part of Loopify's shared dictionary or learning catalogue and be available to other users. Do not submit personal or confidential information as dictionary content. Written learning answers and progress can be associated with your account to provide feedback and track learning.

Speaking exercises and AI

Before a recording is submitted for a pronunciation check, Loopify asks whether you want to share that recording with Loopify and Google Gemini. The request includes your voice recording and the exercise text and language context needed to evaluate your pronunciation. You can decline or close the request without sending the recording for AI processing. Permission applies to that submission; it is not permission to send future recordings automatically.

Loopify deletes its temporary server-side audio files when processing ends, including when an error occurs. This does not mean that Google immediately deletes all request data: Google may retain requests and responses under its service terms, including for security and abuse monitoring. See Google's Gemini API terms and abuse monitoring information. Loopify does not add your email address or account identifier to the pronunciation request sent to Google.

App diagnostics and analytics

Sentry receives error reports and diagnostic context to help investigate faults. Reports can be associated with your Loopify account identifier. Earlier app versions may also have attached your email address. PostHog is not included in Loopify version 1.0.0 (14). Builds 12 and 13 included optional PostHog usage analytics, disabled until enabled in Settings on that installation. If you use one of those builds, you can turn it off in Settings or update to a version without PostHog when available. Removing PostHog does not automatically delete previously collected information; contact us for a deletion request. Those builds had session replay disabled. These app services are separate from the public website.

RevenueCat associates purchase history and entitlement information with your Loopify account to validate access, restore purchases and provide subscription reporting.

This website

The public website does not use analytics, advertising trackers or forms. The magic-link fallback page does not read, redeem, display or log a login token. Requests are still handled by hosting infrastructure for delivery and security.

Retention

Information is kept only while it is needed to operate Loopify, maintain security and integrity, resolve support or legal matters, and meet applicable obligations. Timing depends on the type and status of the data. Deletion from backups may follow the backup lifecycle rather than occurring immediately.

Your choices and rights

Depending on applicable law, you may request access, correction, deletion, restriction, portability or objection. You may also complain to a competent supervisory authority, including the Spanish Data Protection Agency (AEPD). To make a request, email support@loopify.amberwake.com. We may need to verify that the request concerns your account.

Security

Loopify uses measures intended to protect information, including encrypted network connections and access controls. No system can guarantee absolute security. Contact support if you believe your account or information may be at risk.

Changes

This policy may be updated as Loopify or its legal obligations change. The current version and effective date will be published on this page.