Blockkeeperprivacy streetbook

A calm map of information boundaries

What stays on the block, what reaches the web, and what remains in your hands.

This notice describes the Blockkeeper Android app and this two-route static website. It explains the small action cards a reader may save, the controls for removing them, the device features the app does not use, and the ordinary request involved in loading a website.

Last updated 26 August 2026

Scope

What this notice covers

This page covers the current Blockkeeper Android package and the static files in this website revision. Device software, app stores, hosting infrastructure, and any destination reached outside these files follow their own practices.

Two separate cardboard blocks representing the app and static website

People

People and shared context

Blockkeeper can be used by adults, families, educators, and community learners. A responsible adult should add context when age, traffic, property, weather, sharp objects, chemicals, or another safety condition makes that appropriate.

Fictional paper neighbors sharing a planning table with personal space

Purpose

Purpose of the block tool

The app presents an illustrated library and a four-choice planning activity. It helps a reader consider what to pick up, sort, leave, or hand off. It does not take reports, dispatch help, arrange property access, or record completed work.

Four unlabeled object bays forming a cardboard decision tool

Collection

Information you do not enter

The app has no registration, free-text field, message, upload, form, donation flow, or remote intake. It does not ask for a name, address, email, phone number, precise location, contacts, photos, audio, files, or identity documents.

Empty cardboard clipboard beside a closed intake slot

Saved state

What a saved action card contains

When a reader saves an action card, the app records four selected image identifiers and a time value used to order saved cards. A card does not include free text, a person’s name, a location, a photo, or an account identifier.

Small cardboard action card with four abstract colored selection marks

Storage

Where a card stays

Saved cards are written to the app’s private preferences on that device. The current app keeps up to twenty-four cards. It has no built-in synchronization, shared account, or recovery path on another device.

Action card resting inside one device-shaped paper cabinet

Control

Remove and clear controls

A reader can remove one saved card or clear the complete drawer inside the app. Clearing Android app data or uninstalling also removes the app’s local preferences. Because the app creates no remote copy, there is no separate server deletion request.

One card being removed beside an emptied cardboard drawer

Device features

Device access

The current Android manifest does not request camera, microphone, location, contacts, photos, media, storage, calendar, phone, Bluetooth, notification, advertising identifier, or payment access. The images and written material are packaged with the app.

Device-feature objects positioned outside a closed cardboard gate

Connections

Android connection behavior

The current Android manifest does not request network access. Browsing scenes, building a card, saving, removing, and clearing use bundled resources and local preferences.

Self-contained miniature street kit with no cable leading outward

Website

Website requests

Loading a hosted page requires an ordinary request to its host, which may receive technical request information under its own practices. These page files add no cookie, local storage, form, analytics script, advertising script, or account flow.

Paper browser window sending a neutral parcel toward a generic host frame

Identity

Accounts and identity

Blockkeeper has no sign-in, password, profile, public username, follower list, organization roster, or identity-verification flow. A saved card is not attached to an app account.

Open cardboard planning table without roster cards or profile badges

Measurement

Measurement and advertising

The Android app contains no analytics, advertising, attribution, audience profiling, or crash-report upload component. The static page files contain no analytics or advertising script.

Quiet cardboard street without billboards or audience counters

Disclosure

Sharing and outside systems

The app does not send saved cards or personal information to another party, and it has no sale or rental mechanism. Device software, stores, hosts, and destinations outside these files may process information under their own terms.

Closed cardboard transfer chute separating app pieces from outside systems

Shared use

Families and shared devices

The app does not knowingly collect children’s personal information. On a shared unlocked device, another person may be able to open the app and view its saved cards. Families can clear the drawer after a shared activity and use device access controls appropriate to their household.

Family and adult partner reviewing an action card on a shared-device board

Sensitive material

Sensitive stories and hazards

Blockkeeper is not designed to receive medical, legal, financial, educational, immigration, employment, crisis, identity, or incident-report details. Keep those details out of the app and use an appropriate trusted channel. Do not use a saved card as a substitute for an emergency or hazard report.

Bright hazard boundary keeping personal papers away from a cleanup tool table

Outside action

External action and services

The app does not dispatch, report, schedule, or route a request. For sharps, chemicals, unknown containers, traffic danger, private-property questions, or another unsafe condition, step back and use the current local service appropriate to that situation.

Safe step-back path leading toward an unnamed generic local destination

Updates

Changes to this notice

If app behavior or the static page files change, this notice should be revised to match before the changed version is distributed. The updated date at the top identifies the edition being read.

Contact

Privacy contact

No current privacy contact is embedded in this local revision. Add a working contact here and in the app listing before publishing the site.

Return to the block atlas