Why this is difficult
Travel history is sensitive. Automatic location collection can feel disproportionate, while an ordinary spreadsheet can be easy to overwrite, duplicate, or separate from supporting notes.
Worked example
Fictional simplified workflow: Lee adds a Spain stay manually, attaches a selected ticket in Pro, reviews the Schengen explanation offline, enables App Lock, and later exports a password-encrypted backup. StayCount does not infer an unrecorded trip from location history.
What to record or check
- Enter only the travel facts you want in the ledger.
- Review dates after itinerary changes.
- Use App Lock when device-sharing risk warrants it.
- Create and protect an encrypted backup before changing devices or deleting data.
Common mistakes
- Assuming no account means backups happen automatically.
- Expecting the app to detect missing trips from GPS.
- Attaching more sensitive evidence than needed.
- Forgetting the backup password or storing it beside the backup.
How StayCount helps
StayCount stores its ledger locally, performs core calculations offline, requests no location permission, and requires no account. Selected attachments and password-encrypted export/restore are initiated by you.
Official reference
StayCount Privacy Policy. Read the current official material for definitions, exclusions, and personal conditions.
Frequently asked questions
Does StayCount track my location?
No. It has no location-tracking workflow; you enter stays manually.
Do I need an account?
No account is required for the app's local ledger and calculations.
Is backup automatic?
No. Backup export and restore are user-initiated and password encrypted.
Can I attach evidence?
StayCount Pro lets you select supporting files. Add only what you need and manage those files as sensitive records.
Important boundary
StayCount results depend on the facts you enter. StayCount is a planning tool, not immigration, legal, tax, or financial advice, and it does not guarantee an official outcome.