CONSERVATION EDGE EDITION · AUGUST 26, 2026
Privacy, layer by layer.
This folio records what the packaged Android app keeps, what it never asks for, and what changes only if a publisher places these static pages on a public host.
Define the object
Scope
This policy applies to the Gesso Echo Android app in this package and its introduction and policy pages. It does not govern unrelated organization systems, stores, products, hosts, or third-party services.
Publisher boundary
This package is not proof of live publication or organizational authority. A future publisher controls hosting, store records, public contact details, and later product changes, and must keep those statements accurate.
App purpose
Gesso Echo presents eighty illustrated, fictional study surfaces across eight fragments. A person changes the reveal position, reads built-in observation and evidence prompts, moves between fragments, and may choose one built-in Ground Note.
User input
Input consists only of taps and a reveal slider using built-in content. The app contains no free-text field, form, camera capture, microphone capture, location prompt, contact import, document upload, or personal profile.
Examine what remains
Local state
The app saves three small values in device preferences: the selected fragment number, the reveal position, and either one built-in Ground Note key or no note. It does not create an object record or history of prior notes.
Sensitive information
Gesso Echo is not designed to receive names, contact details, ownership records, cultural-property records, condition reports, health data, credentials, payment details, or other sensitive information. Do not use it as a conservation or institutional record.
Permissions
The packaged app does not request camera, microphone, photos, contacts, precise or approximate location, storage, calendar, notification, Bluetooth, or similar runtime permissions.
Network
The Android manifest has no Internet permission, and this build includes no feature that sends reveal position or Ground Note state to a server. A later connected build would require a new assessment and updated notice.
Look for unseen layers
Accounts
No registration, sign-in, profile, social identity, cloud synchronization, or membership feature exists in this app build.
Analytics
No analytics, attribution, diagnostics-upload, or behavioral measurement SDK is included. The app does not send interaction events or create an analytics identifier.
Advertising
The app contains no advertising SDK, sponsored placement, ad personalization, in-app billing, subscription, or purchase flow.
Sharing
The app does not sell, rent, or share personal information with advertisers, data brokers, analytics providers, or the supplied organization profile because it does not collect or transmit that information.
Record the outer edge
Website hosting
If a publisher hosts these static pages, the chosen host may process standard request data such as IP address, request time, requested path, browser information, and security logs under its own terms. These local pages contain no form, analytics script, advertising tracker, or account system.
External links
A future release may link to a store, host, or organization-controlled destination. Those external surfaces apply their own practices. Check the destination before submitting information.
Retention and erasure
Local preferences stay until you use the in-app clear control, clear app storage in Android settings, or uninstall the app. Because this build has no server store, it has no server-side app-data retention period.
Shared devices and children
Another person using the same Android profile may see the selected fragment, reveal position, or Ground Note. Clear local state when this matters. The app is general educational material, not directed to children, and it does not knowingly collect children's personal information.
Security
Data minimization and device-local preferences reduce exposure, but no device or future host can promise absolute security. Protect access to the device and use trusted destinations for any external communication.
Changes and contact
The publisher should update this folio before adding collection, permissions, connected behavior, or a different provider, and should revise the effective date. A public release must supply an accurate, monitored publisher contact; this local package does not invent one.
