Privacy Policy
What Daysway records, where it stays, and what happens when you back it up.
Not final. This policy is written from the current Android source and the app's documented architecture: a SQLCipher database, a Keystore-backed key, encrypted local export/restore, Android device authentication for App Lock, and optional billing components. Production Plus billing is not live. Items marked To confirm need an owner or legal decision before this page is published as final. Nothing here is legal advice.
The short version
Daysway is a private record of your working days. It stores your shifts, earnings, moods and diary entries in an encrypted database on your Android phone. There is no Daysway account and no hosted copy of your app records.
You control backups by exporting an encrypted file. The core record-keeping features work offline. The app requests Android internet and network-state permissions for optional billing; production Plus billing is not configured in the current build, and the RevenueCat Test Store integration is restricted to development and test builds. We do not operate a server that receives your work, mood or diary records. If you email support, that message is handled separately and is described below.
Who is responsible
Daysway is published by Cipher Sector. For data-protection purposes, the publisher is the data controller for the limited information described here. To confirm legal entity name, registered address and data-protection contact.
Because the app does not send us your records, we cannot read, correct, export or delete them for you. Those actions happen on your device and are described below.
What Daysway records
The app records the information you enter so it can show your day, calendar and insights. You choose what to enter; mood and diary are optional.
| Category | Examples | Where it goes |
|---|---|---|
| Work records | Shift date and times, breaks, job, optional notes | Device only, encrypted |
| Earnings | Rates, currency, expected and received amounts, extra income | Device only, encrypted |
| Mood | Mood label, optional note, time | Device only, encrypted |
| Diary | Free-text entries | Device only, encrypted |
| App settings | Theme, currency, selected job, App Lock enabled/timeout | Device only; App Lock uses Android authentication, not a Daysway PIN |
| Purchase state | Plan, entitlement and product identifier, when billing is live | Local cache; Google Play and a subscription provider may process purchase data |
Daysway does not require your name, email address, phone number or contacts to work. You can use the app without creating an account. If you choose to email support, your email address, message and any attachments you send are handled by the support channel described under Contact; they are not added to the encrypted app database.
Where it is stored
- Private records are kept in a local database encrypted with SQLCipher. A 32-byte key is generated on the device with a secure random generator and stored in Keystore-backed secure storage, marked for use only on this device. The key is not kept in the database, plain preferences or logs. If a database exists but its key is missing, the app fails closed and does not silently generate a new key over the data; recovering may require an explicit destructive reset and a restore from your backup.
- The encrypted database and its key are deliberately excluded from Android automatic backup and device-to-device transfer. That protects the records, but it also means there is no system copy to restore from.
- There is no hosted account and no automatic sync of your work, mood, diary or earnings. Optional billing services are separate; see Network and third parties.
- Deleting all data in the app removes the encrypted database and its database key. Uninstalling the app or clearing Android's app storage does the same.
Network and third parties
The core record-keeping features work offline. The app requests Android
INTERNET and ACCESS_NETWORK_STATE permissions. The current
build has no production Plus billing configured. A RevenueCat Test Store integration
exists only in development and test builds, and release builds refuse a Test Store key.
Network permission is present so optional billing can work when it is enabled.
This is not a promise that the app never uses the internet. Google Play may process installs and updates; a future billing flow may contact Google Play and a subscription provider; and other approved services may use a connection. We do not operate a server that receives your work, mood, diary or earnings records.
When production billing is enabled, Google Play will process the payment and a subscription management provider may validate the entitlement. RevenueCat is the provider present in the current source, but only its Test Store path is implemented. Those services may process purchase, entitlement, app and device information under their own privacy policies; the exact production data flow and final provider list still require confirmation. To confirm
The app's manifest removes broad storage, media, overlay and vibration permissions; exports use Android's system file picker. The merged release manifest also includes system permissions and components contributed by device-authentication, screen-capture, document-picker and billing libraries. The final merged permission list and Play Data Safety disclosure must be checked against the release build. To confirm
- No advertising network is configured.
- No analytics, behavioural-profiling or crash-reporting SDK is configured in the current build.
- No data brokers, profiling or sale of personal information.
- Google Play may process install, update, account and purchase information under Google's privacy policy.
- RevenueCat is the subscription SDK present in the source. It is restricted to a debug/test integration today; a production configuration and its data practices require confirmation before billing is enabled.
- If you email support, the message is handled by the support channel described under Contact, which uses Gmail/Google.
Export, restore and data loss
Export and restore are free on Free and Plus. Current backups are encrypted local
.daysway files. The app derives the backup key from your password with
Argon2id (m=19456, t=2, p=1) and encrypts the payload with XChaCha20-Poly1305 using a
random 16-byte salt and 24-byte nonce. The password must be at least eight characters,
is never stored by Daysway and cannot be recovered. Anyone with the file and the
password can read it, so keep both safe.
- Export. Choose Backup & restore in Settings, pick where to save the file through Android's file picker, and set a password. The current export path writes only the encrypted envelope; no plaintext export is written.
- Restore. Choose the backup file, enter its password, review the preview and confirm. Restoring replaces all current local records with the contents of the backup. The file is validated before any write, and a failed restore should leave the previous records intact.
- Legacy files. For compatibility, the app may still read older plaintext export files. A plaintext file is not protected by backup encryption and should be treated as sensitive.
- Storage. The file is saved where you choose. If you put it in a cloud drive or send it to someone, that service's terms apply. Daysway does not upload it for you.
There is no server copy. If you uninstall the app, clear its storage, reset or lose the device without a usable backup file, the records cannot be recovered. The backup FAQs explain the steps in plain language.
What we do not do
- We do not create a Daysway account for you or ask you to sign in.
- We do not sync your app records to a cloud database.
- We do not serve advertising or build an advertising profile.
- No advertising, behavioural-analytics or crash-reporting SDK is configured in the current release.
- We do not sell, rent or share your app records.
- We do not send mood or diary text to an AI model or cloud service.
- We do not turn moods into a clinical score or diagnosis.
Insights and totals are calculated on the device from the records you entered. They are a personal summary, not financial, medical or legal advice.
Your choices
- Edit or delete individual shifts, mood check-ins and diary entries in the app.
- Export your records at any time as an encrypted backup.
- Delete all data from Settings. This removes the encrypted database and its database key.
- Turn on Private App Lock if you have Plus. It uses Android biometric or device-credential authentication and shields the app's screens; it is not a Daysway PIN or a second database-encryption layer.
- Uninstall the app to remove its local data, subject to the backup warning above.
Because we do not hold your app records, we cannot complete an access or erasure request for them centrally. Export and delete-all-data are the controls that act on your copy.
Retention and deletion
Your app records remain on the device until you delete them individually, delete all data in the app, clear the app's storage or uninstall the app. We do not keep a server copy, so there is no separate retention period for the encrypted database on our side. Backups are files you keep and control; we do not retain them.
A cached plan/entitlement may remain in secure storage so Plus can work offline; it is removed when the app is uninstalled or its storage is cleared. If you email support, Cipher Sector receives your email address, message and any attachments through Gmail. Support messages are kept only as long as needed to handle and keep a record of the request, subject to legal requirements; the exact retention period still needs confirmation. To confirm
The website host, Cloudflare, may keep request logs under its own policy; final retention details require confirmation. The site itself sets no analytics or tracking cookies.
Your privacy rights
Depending on where you live, you may have rights to access, correct, delete, port or restrict the use of your personal information, or to object to certain processing. Because the app stores your records on your device, the practical way to exercise those rights for app records is to use the app's edit, export and delete controls. You can contact us about support messages through the email below.
We may need to verify that a request relates to you and may apply lawful exceptions. We do not sell your personal information or use it for behavioural advertising. The regional rights, legal bases, response periods, representative and supervisory-authority details have not yet been finalised. To confirm
Security and its limits
Records are stored in a SQLCipher database with a 32-byte, device-generated key held in Keystore-backed secure storage. Current backups use Argon2id-derived keys and XChaCha20-Poly1305 authenticated encryption. The app fails closed if the database key is missing or the cipher is unavailable, rather than silently replacing the key or opening an unencrypted database. A damaged or wrongly-passworded backup is rejected before any records are replaced. To confirm final security wording against the release build.
Release builds request Android's screen-capture protection (FLAG_SECURE) and use the Private App Lock shield when enabled. Test and QA builds may allow screenshots for synthetic-data testing. App Lock uses Android biometric or device-credential authentication; there is no separate Daysway PIN. It is a UI access shield: it does not re-key, close or re-authenticate the SQLCipher database, which is opened during app startup. The records are therefore protected at rest by SQLCipher and by the Android app sandbox, not by App Lock as a second encryption layer.
No app or device is perfectly secure. Your device lock, operating-system updates and the people who can physically use your phone matter. Keep your backup password somewhere safe; support will never ask for your device unlock credentials or backup password.
The app includes a local Diagnostics screen that runs security, schema and calculation checks and writes metadata such as record counts and pass/fail results to the device console. Those diagnostics are not sent to us, and no crash-reporting or analytics service is configured. Final release logging should be checked before publication. To confirm
Age and wellbeing
Daysway is intended for people aged 16 and over, including younger workers. It asks for no account, name or email, and mood and diary entries stay on the device. No age gate is currently implemented. To confirm whether an age gate, parental-consent flow or regional restriction is required, and the final Google Play age rating.
Daysway is not a mental-health or clinical service. Mood and diary are a personal record, not a diagnosis, treatment or crisis service.
This website
This marketing site uses no analytics, no tracking cookies and no third-party scripts. Fonts, images and the theme toggle are served locally. Your theme preference is stored in your browser's local storage, not in a cookie, and is never sent to us.
The site is hosted on Cloudflare Pages, which may process request and device information to deliver and protect the site under Cloudflare's own policies. To confirm the hosting disclosure, retention details and final provider plan.
The support email link opens your own email app; the website does not submit a form. If you send a message, Gmail/Google and Cipher Sector process it as described under Contact.
Changes to this policy
We will update this page when the app's data practices change, and change the date at the top. Because there is no account, we cannot email you about changes; material changes will be noted on this site before they take effect. To confirm the notice period and any legal review required.
Contact
Questions about this policy, your privacy rights or the app's records can go to the Daysway support inbox below. If you email, Cipher Sector receives your email address, the message and any attachments you choose to send. The inbox is provided through Gmail/Google, which processes the message under its own terms and privacy policy. We use the message to respond to you and keep a support record; the exact retention period still needs confirmation. To confirm
Support email
ciphersector.support@gmail.com
Use the guidance on the Support page when reporting an issue. Do not send diary text, mood notes, device unlock credentials, backup passwords or backup files.
Review notes before launch
These items are deliberately left open. They must be confirmed by the owner and, where appropriate, a qualified legal reviewer.
- Legal entity name, registered address and data-protection contact.
- Production Plus billing status, Google Play/RevenueCat data flow and final third-party service list.
- Final merged Android permission list, including network, biometric, screen-capture and billing components.
- Age rating and whether an age gate or parental consent is required.
- Regional privacy rights, lawful bases, response periods and any representative or supervisory-authority details.
- Retention for support emails, Cloudflare request logs and any other limited record.
- Security, App Lock and screen-capture wording re-checked against the release build.
- Hosting and Cloudflare disclosure wording.
- Full legal review of the final published text, including consistency with the Terms of Service.