Privacy Policy

This Privacy Policy applies to:

• the QuriOS AI Android and iOS mobile applications
• Firebase Authentication, Firestore, Storage, Analytics, Crashlytics, and App Check used by QuriOS AI
• QuriOS AI backend APIs used for login, password reset, chat, projects, account deletion, and profile-linked learning features
• school-managed QuriOS AI deployments

It does not govern separate records maintained independently by a school, institution, or other third party outside QuriOS AI.

QuriOS AI is operated by Akcero Private Limited.

For privacy, support, or deletion requests, contact:

• Email: info@akcero.ai
• Website: https://www.akcero.ai

QuriOS AI is designed for school-managed educational use.

• Students under 18 should use QuriOS AI only under the authorization, consent, and supervision model required by their school, parent or guardian, and applicable law.
• Schools and institutions remain responsible for school-owned rosters, education records, and systems they manage outside QuriOS AI.
• Where a school provides user or profile data to QuriOS AI, the school may be the primary organization responsible for that data under its own policies and legal obligations.

We collect only the data reasonably necessary to operate QuriOS AI as currently implemented.

4.1 Account, identity, and profile data

This may include:

• Firebase user ID
• role
• school ID
• display name
• username
• class and section
• subject preferences
• linked child IDs for parent-linked flows, where applicable
• account state flags such as password-reset or account-status information

4.2 Learning, chat, and project data

This may include:

• questions, prompts, and other text entered into chat
• assistant responses
• conversation titles and conversation history
• project titles, descriptions, and project memory summaries
• saved or starred study items stored on device
• Study Hub interactions and content state

4.3 AR and study-content data

This may include:

• installed AR pack metadata
• grade-linked AR content availability
• downloaded AR and Study Hub content files stored on the device
• AR session metadata such as pack ID, subject, grade, and launch state

4.4 Device, analytics, and diagnostics data

This may include:

• app events and screen interactions
• session identifiers
• school ID, grade, and section attached to analytics context
• crash logs and custom diagnostic keys
• connectivity state, latency, and reliability metrics
• device memory usage figures collected for query-performance monitoring

4.5 Authentication and support data

This may include:

• login requests using school ID, username, and password
• password-reset requests
• audit-log entries related to login and password reset
• account-deletion request metadata and deletion results

4.6 Voice input and microphone access

QuriOS AI includes an optional voice-input feature for chat.

• The app can request microphone permission.
• Speech input is converted into text for use in the chat composer.
• The app does not intentionally store raw audio recordings in its own backend based on the current implementation.
• The resulting transcript text may be used like any other chat input if the user sends it.

We collect data:

• directly from users when they sign in, ask questions, use Study Hub, create projects, use password reset, or use AR features
• from Firebase and school-linked profile records needed to resolve the correct user, role, school, and class
• automatically through analytics, diagnostics, connectivity monitoring, and operational logging used to run and secure QuriOS AI

We use data to:

• authenticate users and restore the correct school-linked profile
• provide AI tutoring, Study Hub, saved history, project memory, and AR experiences
• download and manage grade-linked learning content
• maintain app continuity through secure local caching
• measure app usage, performance, and reliability
• detect crashes, investigate failures, and improve stability
• operate password-reset and account-deletion flows
• maintain security, auditability, and abuse prevention

This section is limited to personal data processing governed by Indian law.

Where the Digital Personal Data Protection Act, 2023 or other applicable Indian law applies, we generally process personal data on one or more of the following grounds, depending on the context:

• consent given by the user, parent or guardian, or the relevant school or institution through the onboarding, login, or school-managed deployment model used for QuriOS AI
• processing that is reasonably necessary to provide the specific educational and account services requested through QuriOS AI, such as authentication, profile resolution, AI chat delivery, Study Hub access, AR content delivery, password reset, and account deletion
• compliance with legal obligations, lawful requests, court orders, or regulatory requirements applicable in India
• uses reasonably necessary to protect rights, detect or prevent fraud, secure the Services, investigate misuse, or maintain operational integrity where permitted by applicable Indian law

If a school or institution provides personal data to QuriOS AI as part of a school-managed deployment, that organization may also have independent responsibilities for the notice, authorization, or consent model it uses under applicable Indian law.

QuriOS AI relies on third-party infrastructure and service providers to operate.

Based on the current implementation, this includes services such as:

• Google Firebase for authentication, app integrity checks, Firestore, Storage, Analytics, and Crashlytics
• QuriOS AI backend infrastructure and databases operated by or for Akcero
• AI model providers used by the backend to generate tutoring responses, including Amazon Bedrock and Google Gemini depending on runtime availability and fallback behavior

When users send study prompts or chat questions, that content may be processed through QuriOS AI backend systems and the configured AI model providers needed to generate a response.

We share data only where reasonably necessary to operate QuriOS AI, comply with law, or support school-managed use.

This may include sharing:

• with the school or institution operating the relevant QuriOS AI deployment
• with cloud, authentication, database, storage, analytics, crash-reporting, and AI service providers acting on our behalf
• with authorized Akcero personnel who need access for operations, support, reliability, or security work
• where required by applicable law, legal process, or valid governmental request

QuriOS AI is not currently implemented as an advertising product, and we do not describe it as selling personal data or sharing data for third-party advertising.

The current app implementation stores some data on the device for continuity and performance.

This may include:

• cached profile data in encrypted local storage
• cached conversation summaries, project lists, and conversation history in encrypted local storage
• starred responses in local preferences
• queued performance metrics awaiting upload
• downloaded AR and Study Hub content files stored in app-managed local storage

This local data is intended to support app functionality and may remain on the device until logout, app deletion, cache cleanup, or account deletion.

QuriOS AI uses technical and administrative safeguards appropriate to the current implementation, including:

• HTTPS-required production API traffic
• release-build restrictions for the production API host
• Firebase authentication and App Check integration
• encrypted local storage for profile and conversation caches
• release crash reporting and diagnostics controls

No system can be guaranteed to be completely secure.

We retain personal data only for as long as it is reasonably necessary for the purposes described in this Privacy Policy, including service delivery, security, troubleshooting, legal compliance, dispute resolution, and deletion processing.

The current implementation maps to the following retention guidance:

12.1 Account and profile records

• App-owned account and profile records may remain in Firebase and backend systems while the account is active.
• Those records may also remain for a limited period after suspension, inactivity, or a deletion request where needed to complete deletion workflows, investigate misuse, maintain backups, or satisfy legal obligations.

12.2 Learning, chat, and project records

• Chat history, conversation titles, project records, and project memory may remain available until deleted through account or product workflows or until no longer needed to operate the relevant feature.
• Where a delete-account workflow succeeds, app-owned student chat and project records are intended to be removed by the current backend implementation described in this Policy.

12.3 Diagnostics, analytics, and operational logs

• Diagnostics, analytics events, audit logs, connectivity metrics, and related operational records may be retained for a longer period where reasonably needed for service reliability, abuse prevention, product improvement, and security review.
• These records may persist after certain content is deleted if retained in aggregate logs, backups, or incident records for legitimate operational reasons.

12.4 Local device data

• Cached profile data, encrypted conversation caches, starred responses, queued metrics, and downloaded Study Hub or AR content may remain on the device until logout, app deletion, explicit cleanup, cache replacement, or account deletion.

12.5 School-managed records outside QuriOS AI

• Records maintained independently by a school or institution outside QuriOS AI follow that organization's own retention practices and are not automatically deleted by QuriOS AI account actions.

QuriOS AI includes an in-app "Delete Account / Delete My Data" flow.

Based on the current implementation, that flow is designed to:

• delete the app-owned `users/{uid}` Firestore profile
• delete the Firebase Auth account
• for student users, delete app-owned student profile, conversations, turns, and projects stored in the backend SQL database
• clear local cached profile and conversation data on the device after sign-out

This flow does not automatically delete separate school-managed roster or institutional records maintained outside QuriOS AI.

QuriOS AI is intended for classroom and school-managed learning use.

• We expect minors to use QuriOS AI only under the authorization model required by their school, parent or guardian, and applicable law.
• We seek to limit collection to data reasonably necessary for the educational services QuriOS AI provides.
• Questions about school-controlled records may need to be directed to the relevant school or institution where that organization controls the data.

Based on the current mobile implementation, QuriOS AI is not described as using:

• in-app advertising SDKs
• location tracking
• contacts, calendars, or SMS access
• payment card storage or in-app billing
• cross-app behavioral advertising identifiers

Depending on deployment and provider configuration, data may be processed in jurisdictions where Firebase, cloud infrastructure, database services, logging services, and AI model providers operate.

We may update this Privacy Policy from time to time to reflect product, operational, legal, or compliance changes. When we make material changes, we will update the effective date above and publish the revised version before relying on the updated terms for production use.