privacy policy

There is nothing in me for them to take.

COCO has no accounts, no ads and no analytics. It remembers two things on your device: your sound settings and whether you've already heard the prologue. Your program and your run aren't saved at all yet, and nothing is ever sent to us.

Effective October 31, 2026 Web · iOS · Android Early prototype Developer: Jan Aguja

The short version

// if you only read one thing, read this
DEBRIEF · PRIVACY

DATA COLLECTED: 0

0accounts
0ads
0analytics
0crash reports
0data sold
2settings, on device
Normally, COCO will keep everything on your device. UNLESS… (no exceptions)

It remembers two settings

Whether music and sound effects are on, and whether you've seen the prologue, so it doesn't replay every time. Both stay on your device. No name, no scores, no program.

It doesn't phone home

No servers of ours, no online play, no leaderboards. The game's art, music, voices and fonts ship with it, so it never calls out to font or media services.

The web playtest will have a password

It isn't open yet. When it opens it'll be for testers, behind a password, like Barangay Defense. This policy will say exactly what that check stores before it does.

Nothing is watching

No ad networks, no analytics, no crash-reporting SDKs, no purchases, and no access to your camera, microphone, contacts, photos or location. COCO talks; it never listens.

Where does it go?

// pick a piece of data and track it

Everything COCO touches ends up in one of four places. Pick one to see where it lands and how long it stays.

Sector 1
💾 Your device

Browser storage on the web, the app's own storage on iOS and Android. Never uploaded by the game.

Sector 2
☁️ Web host

Cloudflare, once the web playtest opens. Serves the game files and checks the tester password.

Sector 3
🗄️ Your phone's backup

Only if you use iCloud or Google backup. Held by Apple or Google, never by us.

Sector 4
🚫 Nowhere

Never collected. The mothership doesn't get it, and neither do we.

  • Sound settings (music on/off, sound effects on/off) → Your device. Kept until you clear site data or uninstall.
  • "Prologue seen" → Your device. So the prologue doesn't replay on every run.
  • Your program and your run → Your device's memory only, while you play. Not saved; closing the game clears them.
  • Taps, clicks and key presses → Nowhere. Read in the moment to play.
  • The tester password check (web) → Web host, once the playtest opens. This policy will be updated first.
  • Connection info (web) → Web host. Like any website, it sees your IP address and browser to deliver the files.
  • A backup copy of your settings (apps) → Your phone's backup, if you use iCloud or Google backup.
  • Name, email, location, contacts, photos, microphone, payment details, usage analytics → Nowhere.

The full policy

// same story, every detail

01Who we are

COCO ("the game") is a spaceship programming game for the web, iOS and Android, developed and published by Jan Aguja, an independent developer in the Philippines ("we", "us"). It is an early prototype and isn't available to the public yet on any platform. This policy covers every version of the game and explains what it handles, where it goes and how long it stays.

02What we collect

Nothing that identifies you. I do not even know your name, Doctor.

The game does not require an account, sign-in, email address, phone number or any other personal detail. We do not collect information that identifies you, and the game has no server of ours to send anything to.

03What stays on your device

Two settings. That is the whole save file.

The game saves the following on your device: in your browser's local storage on the web, or in the app's own storage on iOS and Android.

sound: music on / off, effects on / offprologue seen: yes / no

It does not save:

a name or nicknameyour programyour run or scoresdevice identifierslocation

The program you write in the Programming Bay and the state of your run (legs flown, enemies defeated, EMP charges left) live only in memory while the game is open. Closing or reloading the game clears them. If a later version saves runs or programs, they'll be stored the same way, on your device, and this section will list them before that ships.

Your taps, clicks and key presses are read by your device in the moment to play. They are not recorded or sent anywhere. COCO's voice, the music and the sound effects are recordings that ship with the game; it never listens to you.

04The web playtest

Not open yet. When it is, it will be for testers, behind a password.

The web version of COCO isn't available yet. When the playtest opens, it will ask for a tester password before loading the game, as Barangay Defense does. Before that happens we will update this section to say exactly what the password check stores (for example, a cookie so you aren't asked every visit) and for how long. The iOS and Android apps will not have a password gate.

05Network & hosting

The game makes no network requests of its own beyond loading its own files: pictures, music, voices, sound effects and fonts. The iOS and Android apps carry those inside the app; the web version will load them from our web host. The fonts are bundled with the game, so it doesn't contact font services.

The web version will be hosted on Cloudflare, which serves janapps.com. Like any web host, Cloudflare processes connection information (such as your IP address and browser type) to deliver the files and protect the site from abuse, under its own privacy policy. We don't use that information to identify or track you.

06Third-party services

The game includes no advertising networks, analytics SDKs or crash-reporting SDKs, and no social or sign-in services. We do not sell, rent or share your information with anyone.

When the apps are published, Google Play and the Apple App Store may give us aggregated statistics such as install counts and crash rates, under their own policies. These don't identify you.

07Purchases

The game has no in-app purchases. Pricing for the store versions hasn't been decided. If that ever involves a purchase, the App Store or Google Play will handle the payment, and this policy will be updated first.

08Permissions

The iOS app requests no permissions, and the web version asks for none. The game does not access your camera, microphone, contacts, photos, files or location. The Android version isn't built yet; this section will list anything it declares before it's published.

09Retention & deletion

Want your settings gone? Clear them the way you would clear any app.

  • Web: clear this site's data in your browser settings.
  • iOS and Android: uninstall the app, or clear its data in your device's settings.

If you use iCloud or Google backup, your device may include the app's saved settings in that backup and restore them on a new phone. Those backups are held by Apple or Google under your own account, not by us. There's no copy anywhere else for us to delete.

10Your rights

Depending on where you live, including under the Philippine Data Privacy Act of 2012, the GDPR or similar laws, you may have the right to access, correct or delete personal data held about you. We don't hold any, so the quickest route is on your own device, as described above. For anything else, email us and we'll respond.

11Children's privacy

COCO is not directed at children under 13. We do not knowingly collect personal information from children, and the game doesn't collect personal information from anyone.

12Changes to this policy

If this policy changes, the updated version will be posted here with a new effective date. If a change affects what data leaves your device, such as the web playtest gate, saved runs, online features or purchases, the policy will be updated before that change ships.

13Contact

Questions about privacy? Email [email protected]. It goes straight to Jan.