Privacy Policy

Ruqelo Arabic is committed to data minimization and learner privacy. When you create an account, profile, progress, and preferences may be stored securely through our backend services. The sections below describe how we handle information.

When accounts and backend services are connected, we may process:

• Account data — name, email, authentication identifiers, and verification status
• Learning progress — lesson completion, streaks, and practice time
• Roleplay data — scenario IDs, scores, and optional transcript text from practice sessions
• Pronunciation data — attempt counts, scores, and weak-sound flags — not raw audio by default
• Voice usage metadata — session duration, credits consumed, and quota events for billing fairness
• Billing metadata — subscription status, purchase references, and refund request records (when billing is connected)
• Reminder preferences — schedule, timezone, and notification settings you choose

No raw audio is stored by default. Realtime and pronunciation features may process audio transiently to deliver the service.

If optional audio retention is ever offered, it will require explicit consent with clear controls to delete stored recordings.

We use learner data to provide and improve the service, including:

• Personalizing dialect tracks and recommendations
• Enforcing voice credit limits server-side
• Processing subscriptions and support requests
• Sending practice reminders you opt into
• Protecting against abuse and fraud

We aim to collect only what is needed for learning, billing fairness, and security. Retention periods will be defined before launch and aligned with legal requirements.

At launch, signed-in users will be able to request account deletion and, where required by law, export of personal data. Deletion workflows will be documented before production auth ships.

Some billing or fraud-prevention records may be retained as required by law after account closure.

We may use third-party processors for authentication, hosting, billing, analytics, and AI infrastructure. Processors will be bound by contractual safeguards appropriate to the data they handle.

User-facing policy copy describes categories of processors — not vendor names — unless required by law at launch.

We design for server-side quota enforcement, access controls, and encryption in transit. No system is perfectly secure; report concerns through our Contact page.

The service is not directed to children under 13 (or the applicable age in your region) without parental consent. Age requirements will be confirmed during legal review.

This Privacy Policy is draft placeholder text. Final wording, regional notices, and data processing agreements require qualified privacy counsel before production launch.