NotiSynk legal information
Data Retention Policy
How long each kind of record is kept
- Version:
- 1.0
- Effective date:
- 2026-08-16
Information is kept for as long as it is needed to run the Service, to keep the business and security records that have to be kept, to meet a legal obligation, to resolve a dispute and to enforce the agreement. Different categories follow different rules, and this page sets out each one.
Where the Service enforces a fixed period, that period is stated below. Where it does not, the rule that decides how long a record stays is stated instead. No period is stated here that the Service does not actually apply.
1. Retention by category
| Category | How long it is kept |
|---|---|
| Professional account and Workspace | For as long as the account is open. Deleting the account removes the Workspace and the Client records in it, other than the records listed as append-only below |
| Client, Plan and Client Subscription records | For as long as the Workspace holds them. Archived records are kept as read-only history and are not deleted by archiving |
| Session balances and session events | Append-only. A correction is recorded as a further event rather than by changing or removing an earlier one, so the history is kept for the life of the Workspace |
| Reminder activity | Kept for the life of the Workspace. There is currently no automatic cleanup of reminder history, so these records remain available until the Workspace is deleted |
| WhatsApp consent records | Kept while the Client record exists, including after consent is withdrawn, because the record of the withdrawal is what stops further messages |
| Client revenue records on Max | Append-only. Kept through a downgrade from Max to Premium and reachable again if Max is activated later. A correction is recorded as an adjustment rather than by changing the original |
| Workspace billing records | Kept as business and accounting records for the period the applicable law requires, which outlasts the account |
| Support tickets and messages | Kept while they are needed to handle the request and to keep the history of the account. A resolved ticket is kept as history and cannot be reopened |
| Legal acceptance evidence | Append-only and kept permanently. It records which version of which document was accepted and when, and it is never rewritten to a newer version |
| Security and access records | Kept while they are needed to operate and secure the Service, to investigate abuse or unauthorised access, or to establish or defend a claim |
| Sign-in sessions | A session ends when the browser closes, or after 30 days where Remember me was chosen. Signing out ends it immediately |
| Email verification records | Removed once the code has been used and has expired |
| Cookies in your browser | As listed in the Cookie Policy. The consent cookie lasts 365 days |
2. Records that cannot be changed or removed
Four kinds of record are append-only. Once written, an entry is never edited and never deleted; a change is recorded as a new entry that supersedes it. This is deliberate, because these records are evidence of what happened.
- Legal acceptance evidence, which proves which document version was agreed and when.
- Client revenue transactions on Max, so a financial history cannot be rewritten after the fact.
- Session consumption and restoration events, so a session balance can always be explained.
- Payment and refund records connected to a Workspace billing subscription.
A request to erase information does not reach these records. Where a request cannot be met for that reason, we say so and explain why rather than deleting something else instead.
3. Deleting your account
Export what you need before you delete. While the account is open you can export the exportable parts of your Workspace at any time using the tools in the Service.
After the agreement ends we keep the Workspace data for a reasonable retrieval period so that it can still be exported, then remove it, apart from the records described above.
Backups are overwritten on their own cycle rather than edited, so a record can persist in a backup for a period after it has been removed from the live system. While it does, it is not used for anything and is only restored as part of recovering from a failure.
4. Records held by providers
The providers listed in the Subprocessors notice keep their own records under their own retention rules, which NotiSynk does not control. The payment provider keeps transaction records, and the messaging provider keeps message and delivery records. Deleting a record in NotiSynk does not delete the provider's copy.
5. Asking about retention
Write to info@notisynk.com to ask how long a particular record is kept, or to ask us to correct, complete, update or erase information about you. Section 8 of the Privacy Policy describes those rights and section 9 describes where they do not reach.
Change log
- v1.02026-08-16First published version. Describes retention by category using the criteria the application actually applies, including the records that are append-only, instead of stating fixed periods that the product does not enforce.