
Getar Privacy Policy
Effective 26 September 2026 · Developer: Saifullah Ahad1. What Getar does
Getar records ambient movement using a phone's accelerometer during a user-started, charging night. It retains derived measurements to compare nights in the same recording place. Optional invitation-only building groups compare observations from different floors. Getar is not an engineering instrument or a replacement for a structural inspection.
2. Information used by the app
- On this device: storey count, approximate building height, construction type, recording floor, a random placement identifier, selected duration, optional room temperature, an unusual-occupancy selection, dates, sample counts, accepted/rejected window counts, derived frequency spectra and comparison results.
- Sensor processing: acceleration samples and their timestamps are processed in bounded memory. Raw acceleration is not written to storage or sent to the relay. If the device has a separate ambient-temperature sensor, Getar can use that reading; battery temperature is not used as room temperature.
- Optional group connection: the relay holds random group and member identifiers, authentication-token hashes, public signing keys, invitation expiry information, encrypted invitations, encrypted measurement envelopes, delivery cursors and encrypted push-registration tokens. The server can observe group membership and request timing. It cannot decrypt the floor or measurement content inside an envelope.
- Service metadata: network providers necessarily process IP addresses and connection metadata. Firebase Cloud Messaging and its Installations dependency use an app-installation identifier, push token, app version and SDK/device metadata to deliver group-update hints. Push registration is requested when a building group is created or joined.
Getar does not request microphone, camera, contacts or location permissions, and does not ask for a building address, resident name or account password. There is no analytics or advertising SDK.
3. Why information is used
Local information supports recording, signal rejection, frequency comparison, temperature/time adjustment, interrupted-session recovery and evidence export. Group identifiers authenticate invited devices and route encrypted observations. Local Wi-Fi timing exchanges support optional comparisons of aligned windows; inadequate timing causes those comparisons to be withheld.
4. Sharing and service providers
Cloudflare Workers, Durable Objects and D1 provide the encrypted group relay. Google Firebase Cloud Messaging and Firebase Installations provide optional group-update delivery. Firebase is not used for storing the measurements. HTTPS protects internet transport. Authorised group members hold the keys needed to read observations they receive. A member can retain a received copy; removing a connection cannot remotely erase another person's copy.
Saving evidence writes a JSON file to the destination you choose through Android's document picker. You control any onward sharing of that file. It contains measurement summaries and spectra, not raw acceleration.
5. Retention and removal
Detailed local spectral windows are retained for up to 30 days, with an additional storage bound that may remove older windows sooner. Nightly summaries can be retained for up to five years. Aligned shape packets have a 30-day local limit; group shape history is bounded, preserving the current placement's initial reference. Temporary raw-sample buffers are discarded after processing.
The relay removes measurement envelopes older than 30 days and also bounds the number retained per group. Expired invitations are removed. Group/member records remain while the connection exists. Use Across the floors → Leave this building group, or End this building group if you started it, to remove the corresponding server connection. The connection removal requires the relay to be reachable; a failure leaves the credentials available so you can retry.
Use Notebook settings → Erase this notebook to remove the local notebook and app lock after ending any group connection. End an active recording first. Exports and copies held by other people are not removed. Android's Clear storage or uninstall removes local app data; it does not by itself tell the relay to delete a group. Contact us if you need help ending a connection. Firebase may retain service identifiers according to its service retention practices; Getar does not claim that erasing its notebook deletes all provider records.
6. Optional app lock and protection
Fingerprint/face unlock and a separate Getar PIN are optional, independent methods. Android's biometric prompt does not provide biometric templates to Getar and does not offer device-PIN fallback. A Getar PIN is stored only as a SHA-256 hash with a fresh random 16-byte salt, within the app's encrypted local record store; the plain PIN is not stored or transmitted. Getar cannot read your device PIN. Choose a different PIN for Getar.
Local records use Android Keystore-backed encryption. Android cloud backup is disabled. The app marks its window as protected against screenshots and screen recording. These measures do not prevent an authorised person from viewing or separately recording information displayed to them.
7. Feedback and concern reports
Send feedback and report controls open an email app addressed to [email protected]. Getar does not automatically attach measurements or send a message. Your email provider handles the message you choose to send. We receive its sender address and the contents you include, and retain support correspondence only as needed to respond and meet legal obligations.
8. Children
Getar is intended for adults considering building observations. It has no public posts, chat, photos or personal profiles. Child sexual abuse and exploitation are prohibited. See the separate child-protection standards for reporting. Do not send abusive imagery or unnecessary personal information in a report.
9. Changes
This page will be updated if the app's data handling changes. The effective date above identifies the current version.
10. Contact
Saifullah Ahad
[email protected]
saifullah.ai