Website and demo (information we control)
| Data | Kept for | Then |
|---|---|---|
| Consultation requests (form fields and IP address) | Up to 2 years from receipt | Deleted automatically, or sooner on request |
| Demo sign-in sessions | 12 hours (idle sessions end sooner) | Expired and removed |
| Demo sample data (fictional) | Reset every night | Rebuilt from scratch |
| Hosting provider server logs | Provider's standard short retention period | Rotated out by the provider |
| Invoices and tax records, if you become a customer | At least 7 years, as the law requires | Deleted after the legal period |
Customer deployments (information we process for a customer)
When ODYSSEYDEVELOPMENTS LLC hosts NewBoarding for a business, the customer owns its data and decides what is kept. By default: stored logins for an employee whose directory account is disabled are deleted automatically 30 days later; notifications are deleted after 180 days; closed password-reset requests and the security audit log after 365 days. A customer's agreement may set different periods.
When a customer ends its subscription
On request during the term we export the customer's data. Within 30 days after the term ends we return or permanently delete it at the customer's choice, except routine backups (which are overwritten in the ordinary course of our database provider's backup cycle) and data we must keep by law.
Asking us to delete your information
- Email newboarding@odysseydevelopments.dev from the address you used, saying what you want deleted. We confirm your identity, delete the information within 30 days (we will tell you if we need up to 45), and confirm when it is done.
- We may keep limited records where the law requires or allows, such as a record that a deletion request was made, tax records, and information needed to defend legal claims.
- If you are an employee of a customer, ask your employer first; we delete or return the customer's data on its instructions.
How deletion works
Records are removed permanently from the database. Stored passwords in customer deployments are encrypted per user and system, so a deleted record cannot be read back from a backup without the encryption key and its original owner binding, and backups are overwritten on the provider's normal schedule.