Data Exitbook stores
Exitbook stores its application database in the iPhone app’s private storage. The database can contain the Account name and public address entered by the user, durable Import progress and public blockchain activity returned by Routescan, derived Ledger records, and Readiness results.
Exitbook does not ask for a name identifying the person, email address, Apple account, wallet private key, seed phrase, exchange credential, or payment information. It cannot sign or submit blockchain transactions.
Provider requests
Exitbook sends the public Avalanche C-Chain address and requested block ranges to Routescan over HTTPS only after the user explicitly starts or resumes an Import. Routescan returns public blockchain activity and token information used to build the local Ledger and Readiness results. Exitbook does not operate an intermediary server and does not receive or retain the request or the local database.
Routescan may retain technical and request-log information, including the source IP address associated with API usage, for service delivery, security, abuse prevention, and service analytics. Its current policy says raw server logs are typically retained for at least five days and can be retained differently when investigating security or application incidents. Routescan’s handling of that information is governed by its privacy policy.
Analytics, advertising, and tracking
Exitbook does not include an Exitbook account service, analytics SDK, advertising, tracking, crash-reporting service, hosted storage, or synchronization. Exitbook does not sell data or share it with advertisers or data brokers. The Routescan requests described above are used for Import functionality; they are not used by Exitbook for advertising or tracking.
Apple may process TestFlight, App Store, device, and diagnostic information under Apple’s own terms and privacy policy. Exitbook does not add a third-party analytics or diagnostic SDK to receive that information.
Choices, retention, and deletion
Creating an Account saves it locally and does not contact Routescan. The user chooses whether to start or resume an Import. Cancelling an Import stops the active foreground request sequence; activity and completed block coverage already saved on the iPhone remain available for an explicit resume.
Local data remains in the app’s private storage until the app removes it or the user deletes the app and its data through iOS. This build has no remote Exitbook account or Exitbook server-side data to delete. Routescan controls the retention and deletion of information it processes under its own policy.
Security
The app relies on the security protections provided by iOS and the app’s private container. Public watch-only addresses and public blockchain activity are not transaction-signing secrets. The app does not store exchange secrets, wallet private keys, or seed phrases.
Changes
This policy will be updated when Exitbook adds another provider, source type, analytics or diagnostics, accounts, payments, hosted storage, synchronization, or other materially different data handling.
Contact
Questions about this policy can be sent to contact@exitbook.io.