Your daily route is a personal story.

A day’s movement can reveal familiar places, routines and time spent away from home. It deserves a different approach from an ordinary product counter.

Separate the diary from the service

Etmasha’s design keeps personal movement history and fitness processing on the phone. The owner console handles the service: support, subscription evidence, provider usage and technical operations. It is not a map of everyone’s movements.

Optional online features still have data flows. A place lookup sends a query. A support message shares the words you submit. These choices should be described directly rather than hidden behind a blanket claim that nothing ever leaves the phone.

Make sharing deliberate

Sharing a support message is a separate choice. A useful description of a problem need not contain a person’s route or Health readings. Automatic cloud AI diagnosis and customer technical-report uploads are not offered in the public first release.

You should be able to inspect what a support request includes before it is sent.

Know what recovery means

A purchase and a diary are different things. Restoring a subscription can restore access, but it does not restore a lost local history. Etmasha 1.0 keeps a separate diary on each device. A securely retained export is a separate copy you control.

Read the privacy notice for the information used by each optional service.