Terms of Service

Use of service

• dont is a product made and operated by dont SIA. The official dont support mailbox is assist@dont.lv.
• Use dont only for lawful business operations and authorized internal workflows.
• Do not misuse the service to spam, harass, disrupt, or overload the platform.
• Company admins are responsible for the users and data they permit into their workspace.

Protected materials

• Do not mirror, clone, reverse engineer, mass-extract, or systematically copy dont workflows, interfaces, outputs, or proprietary logic except where law cannot restrict it.
• Do not use dont data, workflows, or protected content to train third-party models or create competing replicas without written permission.

Accounts and company workspaces

• Access is company-scoped and may be suspended, limited, or removed to protect workspace integrity or prevent abuse.
• Only authorized company admins may add users to an existing company workspace.
• If a company VIP period ends without payment, authenticated users may be limited to billing, logout, and legal routes until the company subscription is activated.

Personal integrations and account security

• When a user connects a personal OAuth account such as Gmail or Google Calendar, that connection is private to the connecting user and must not be accessed by company admins through password resets, saved browser passwords, shared devices, or impersonation.
• dont uses individual user OAuth for Google integrations and does not use Google Workspace domain-wide delegation or a service account to impersonate Workspace users for Gmail or Calendar access.
• An dont superadmin or company admin role does not by itself grant the ability to browse or connect another user's Google mailbox or calendars; access requires that Google account holder's OAuth consent or content already synced into an authorized company workspace.
• Private Gmail and Calendar integrations require two-factor authentication before OAuth connection, display, sync, or management.
• If an dont admin/support account attempts unauthorized access to another user's private Google data through the application or admin tools, dont blocks the request, locks that user's private Google integrations, clears stored Google OAuth tokens, records a security audit event, and requires the user to reconnect Google.
• dont may also lock private integrations and require reconnection after an dont password change, a 2FA reset, or repeated failed private-integration 2FA attempts.
• Users are responsible for keeping their dont credentials, two-factor codes, backup codes, browser profiles, and connected third-party accounts under their control.
• Company-owned channels, shared inboxes, or business messaging accounts may be connected only by authorized users and must not be used to access another person's private third-party account.

Retention and locked workspaces

• dont may retain company, user, billing, login, and business records for up to 10 years where legal, accounting, security, audit, or operational obligations require it.
• Non-payment, cancellation, or workspace lock does not automatically delete company data before the applicable retention period ends.

Abuse and impersonation

• Do not impersonate another company, submit misleading identity data, or use shared/public routes to test unauthorized access.
• dont may block automated extraction, public-form harvesting, or repeated access attempts that bypass intended workflow controls.
• Questions about lawful use or public launch access should be sent to dont support.