Identity shape inside Campora
Campora does not require you to register an email address or pick a password to use the core planning flow. There is no in-app social graph where strangers follow your trips. The app treats you as the person holding the unlocked phone, not as a row in a remote profile database that Campora itself hosts for login purposes.
That design choice has a trade-off: if you replace your phone, factory-reset, or delete app data, you may lose continuity unless you manually export screenshots or other artifacts you care about.
What stays on your device by default
Layout plans, element lists, gear checklist rows, thumbnail paths, and similar structured information are stored locally using the on-device database features Campora is built with. Photographs you associate with plans are saved inside the application sandbox so the editor can reopen them.
We do not operate a Campora-branded cloud sync service as part of this description. Your campsite sketches remain yours in the everyday sense: they live next to the app until you remove them or the operating system reclaims space.
Camera and photo library access
When you start a new plan, Campora may ask the system to open the camera or photo picker. Those moments are governed by the permission dialogs your phone already shows. Grant access if you want Campora to read pixels you capture or select. Deny access if you prefer not to share images with the app.
Campora resizes large images before storing them to reduce storage pressure. That processing happens for usability, not for building an advertising dossier about your face.
Screen content you type
Notes you attach to elements, plan titles you invent, and gear names you enter are stored as part of your local records. Treat those fields like markings on a paper map: anyone who unlocks your device and opens Campora can read what you wrote.
Optional tracking transparency prompts
On platforms that expose tracking consent prompts, Campora may request permission to read an advertising-related identifier. Your operating system stores your answer. If you tap ask not to track, Campora should respect that choice within the limits of what Apple or Google exposes to developers.
Campora is not described here as a massive data brokerage product. Still, platform vendors have their own analytics and crash pipelines that may observe anonymized stability signals when you install any app.
In-app purchases and store receipts
If you buy digital items through the platform store, Apple or Google processes payment details. Campora receives coarse signals such as whether a purchase succeeded so it can update an on-device balance or unlock a feature. Campora does not type your credit card number into its own custom form inside this product description.
Embedded web content
When you open agreement screens that load a URL in a web view, the remote server may see standard web information such as IP address, user agent string, and TLS metadata, the same way any website would when you visit it in a browser. If you dislike that exposure, do not open those screens.
Crash logs and diagnostics outside Campora
Modern mobile operating systems sometimes upload crash reports or energy diagnostics to the vendor. Those uploads are controlled at the device level in settings menus that mention analytics, diagnostics, or privacy. Campora cannot disable the entire operating system telemetry stack from inside the app.
Children and family devices
Campora is a layout sketchpad, not a messaging toy aimed at collecting contact books from kids. Parents who hand a device to a younger camper should still use parental controls built into the phone, because photos may include location metadata depending on camera settings outside Campora.
How long data lingers
Local data remains until you delete it inside Campora, delete the app, or clear storage. There is no guarantee of infinite retention on a finite phone. If you want a plan to outlive a single device generation, export it using screenshots or any future export tools the app provides.
Changes to this journal
We may revise this page when features shift, for example if a future build introduces optional backup hooks. The top of the HTML file or the in-app screen should show a refreshed date when that happens. Continued use after an update means you read the refreshed journal, the same way you would read a new insert tucked into your trail guide.
Last updated: