Plain-language privacy information for the website and app.

Scope

What this policy covers

This privacy page applies to the public InAppCode website and the publicly described Android app experience. It is written as a plain-language overview for buyers, learners, and program operators evaluating the product.

If you operate a custom or managed deployment, your organization may have additional retention, logging, or support obligations beyond what is summarized here.

Data Categories

Information the app and website may process

• Code submissions, selected languages, challenge choices, and AI-feedback requests.
• Usage signals such as basic interaction events, performance flow, or session diagnostics.
• Technical information needed to keep the service reliable, secure, and abuse-resistant.
• Support messages, security reports, or deployment-related questions sent through official channels.
• Google Play or hosting-provider metadata required to distribute, secure, or monitor the service.

Use of Information

How information may be used

• Operate the coding-practice experience and generate AI feedback.
• Recommend the next challenge or difficulty level based on recent performance.
• Debug service issues, monitor uptime, and protect the product from abuse.
• Respond to support requests, rollout questions, or security disclosures.
• Improve product quality, learner experience, and deployment reliability over time.

Providers

Sharing and service-provider processing

InAppCode may rely on infrastructure, AI, analytics, app-distribution, or monitoring providers to operate the service. Information is shared only as needed to deliver the requested product experience, maintain reliability, investigate abuse, or satisfy applicable legal obligations.

Because code may be processed by AI systems to generate feedback, users should avoid submitting secrets, regulated data, or confidential material in prompts or code samples.

Retention and Controls

How retention and user control work

Since core practice does not require a user account, profile-style identity data is minimized. Some progress or temporary state may be stored locally on a device, while operational logs may be retained server-side for reliability, support, and security.

Managed deployments may apply their own retention, audit, or deletion workflows. Organizations evaluating rollout should confirm those requirements before launch.

Education Settings

Minors, classrooms, and school-managed use

If InAppCode is used in a school, lab, or bootcamp setting, the institution may have separate responsibilities around notices, acceptable use, supervision, or parent communication. This page is not a substitute for institution-specific compliance review.

Teams using the product in education environments should also review the trust center and support page before rollout.