Cookie Policy

What gets stored on your device and why.

InAppCode is designed to minimise data storage. The app does not require an account, which means we have no persistent identity profile to maintain. This page explains what is stored on your device for the website and app to function.

Last updated May 2025 — Chapterfeed Learning Space Private Limited

The Website

What inappcode.com stores in your browser

The InAppCode public website does not use tracking cookies, advertising cookies, or third-party analytics scripts that place persistent cookies in your browser.

The website loads resources from:

  • Google Fonts (fonts.googleapis.com, fonts.gstatic.com): Font files may be cached by your browser. Google may log access to their CDN per their own privacy policy. No personally identifying information is deliberately sent by us to this service.

If you use the language selector or interactive demo on the homepage, state is kept in memory only and cleared when you close the tab. Nothing is written to browser storage for those features.

The Android App

What InAppCode stores on your phone

The InAppCode Android app uses React Native AsyncStorage to persist practice progress locally on your device. This includes:

  • Your attempt history (which questions you have tried and when)
  • Practice streak data derived from attempt timestamps
  • Your most recently selected programming language

This data is stored entirely on your device. It is not synced to any server, is not associated with an identity, and can be cleared by uninstalling the app or clearing app data through Android Settings.

The app also uses a Monaco Editor loaded from a CDN (cdnjs.cloudflare.com). If you lose connectivity while the editor is loading, a graceful offline message is shown instead. Cloudflare may log CDN access per their own privacy policy.

AI Requests

What happens when you submit code for feedback

When you tap Submit in the app, your code, selected language, and question metadata are sent to the InAppCode backend API to generate AI feedback. The backend may cache the AI response in Redis (a server-side cache) keyed by a hash of the code and question — this reduces redundant AI calls and improves response speed.

The cache key is a one-way hash. No account or identity is associated with the cached entry. Cache entries expire automatically.

No cookies are used in the API request path. The app uses a server-side API key for authentication, which never appears in your device storage.

Your Choices

How to manage stored data

  • Website: Use your browser's built-in cookie and cache management tools to clear any cached resources from third-party CDNs.
  • App — practice history: Clear app data via Android Settings → Apps → InAppCode → Storage → Clear Data.
  • App — full removal: Uninstall the app to remove all locally stored data.