Wiesselen Privacy Policy
Effective date: 25 October 2026. Developer: SAIFULLAH.
Device-local planning
Wiesselen records building layouts, passages, sign text, access requirements, revisions, proposed plans, inspections, action history and notes on your device. Names you enter for coordinators or reviewers are local labels, not authenticated accounts. We operate no Wiesselen account, cloud database, advertising or analytics service. The app does not automatically transmit these records to the developer.
Storage and protection
Record contents are encrypted in the app's private Android database with random project keys wrapped by Android Keystore. Record relationships, project identifiers, timestamps and revision/step numbers remain storage metadata. Existing records are upgraded locally; no records are sent to the developer. The optional local PIN is a screen lock, not an encryption password. Its salted hash is stored locally. Android handles biometric matching; Wiesselen receives the authentication result, not fingerprint or face templates. Real projects hide screenshots and Recents previews by default, independently of the optional app lock. Only eligible fictional-sample views permit capture. Keep your device protected.
Files and messages you choose to send
You can export a PDF or JSON record through Android's document picker. PDF and JSON exports keep building/sign labels and route details. Personal-name fields and free-text notes are removed by default; you can include them explicitly after reviewing the export. Names entered inside building or sign labels remain. Photos and background attachments are not supported or included. The provider you choose may upload or synchronize the file under its own policy. PDF and JSON copies are not encrypted and are not remotely revocable. An optional protected backup encrypts the full model and history using a separate passphrase (12 to 256 characters). Wiesselen never saves that passphrase and cannot reset it. Protected backups exclude device keys, app PIN and permission to resume old work. Restores create new local identities and require a new plan and building inspection. Importing JSON creates local records. Feedback and safety reports open your email app; review the message before sending it to [email protected]. Your email provider and the recipient then process the message.
Permissions and libraries
Optional biometric authentication uses Android biometric permissions. Document access is limited to the destination you select; no broad storage or camera permission is requested. Wiesselen does not request internet, location, contacts or advertising permissions. AndroidX, Kotlin, Tink and Bouncy Castle are local application libraries; their presence does not mean your project is uploaded. See the release notices for resolved versions.
Retention, deletion and loss
Local records remain until you delete them or remove the app's storage. Use Delete for the selected project; its database records and wrapped project key are removed. Flash secure erasure cannot be guaranteed. Clearing the app's storage or uninstalling removes its app-private data; delete exported files separately in the provider that holds them. Wiesselen disables Android app backup and excludes its database, files and preferences from configured cloud and device-transfer backups. Manufacturer behavior has not been verified on every device. We cannot remotely recover or erase a lost device. Do not assume that a restored record describes the present building.
Children and safety
Wiesselen has no public feed, messaging service or user accounts. Do not enter unnecessary personal information about children. It is a supervised, non-emergency planning tool, not a safety certification or an emergency navigation service. Our child-safety standards prohibit child sexual abuse and exploitation.
Contact and changes
For privacy requests or questions, contact [email protected]. Requests about local records must be handled on the device because the developer has no copy. Messages sent to us are retained only as needed to respond and meet applicable obligations. Material policy changes will be reflected in the effective date.