Last updated: December 25, 2025
Publisher: CEOTXT® (Rokter AS)
Contact: post@ceotxt.com
CEOTXT is built for founders and leadership teams who want clarity without chaos. That only works if you can trust how we handle data. This page explains, in plain language, how we protect your information and where it is stored.
This page is informational and not legal advice. For legal details, see our Privacy Policy.
At a glance
- Encryption: Data is encrypted in transit, and sensitive credentials are protected using strong hashing and encryption practices.
- EU data residency (primary): Core CEOTXT application data is stored in the European Economic Area (EEA).
- No selling of data: We don’t sell personal data. We use data to provide and improve the Service.
What data CEOTXT stores
CEOTXT typically stores:
- Account data: name, email address, login identifiers, organization name (if provided)
- Recipient data (if you add recipients): phone numbers and/or emails you provide for sending summaries
- Customer Content: business metrics, notes, targets, and reporting rules you enter
- Operational data: basic logs needed for security, abuse prevention, and troubleshooting (e.g., sign-in events, error logs)
What we do NOT store:
- Full payment card numbers (payment details are handled by payment providers)
- Government ID numbers (not required)
- Sensitive categories of personal data by design (please don’t submit it)
Data residency: where your data lives
Core CEOTXT application data
Our primary systems that store core CEOTXT application data are hosted within the EEA.
When data may be processed outside the EEA
Some parts of the Service rely on third-party providers to function globally (for example, payments, communications delivery, analytics, and customer support). Depending on your location and your configuration, limited data may be processed outside the EEA.
When cross-border processing is required, we use appropriate safeguards consistent with applicable law (for example, contractual protections and other lawful transfer mechanisms).
If you’re doing procurement or diligence and need specifics, contact us.
SMS delivery: what happens (plain language)
If SMS features are enabled, CEOTXT must transmit certain information to deliver messages:
- Recipient phone number
- Message content (e.g., your weekly summary text)
- Delivery metadata (delivery status, timestamps)
SMS delivery involves mobile network operators and delivery partners. Delivery can be delayed or fail for reasons outside our control (carrier filtering, coverage, device settings, etc.).
If you add recipients, you are responsible for ensuring you have the right to message them (see our Terms of Service).
How we protect your data
Security is a moving target. We focus on practical controls that reduce real risk.
Encryption
- In transit: We use HTTPS/TLS to encrypt traffic between your device and our servers.
- Credentials: Passwords (where applicable) are stored as hashed values, not plaintext.
Access control
- We apply least-privilege access: only people who need access to operate/support the Service get it.
- Administrative access is protected with strong authentication and access controls.
Monitoring and logging
- We monitor systems for reliability and unusual activity.
- We keep logs needed to investigate incidents and prevent abuse.
Secure development & updates
- We patch and update dependencies and infrastructure as needed.
- We review changes before deployment and prioritize fixing security issues.
Data separation
- Customer Content is logically separated within our systems to prevent accidental cross-access.
Backups and disaster recovery
We maintain backups to protect against accidental deletion and system failure.
- Backups are stored securely and retained for limited periods.
- Backups are used for recovery, not for day-to-day operations.
- Deleted data may persist in backups until backups rotate out.
Your controls
Depending on your plan and current features, you may be able to:
- Update account settings and notification preferences
- Add/remove recipients
- Export your data (where available)
- Request account deletion (subject to legal retention requirements)
If you need help with data export, deletion, or access, email post@ceotxt.com.
Compliance and documentation for procurement
For organizations that require formal documentation, we can provide:
- Data Processing Addendum (DPA) (on request)
- Security questionnaires (reasonable scope)
- A subprocessor overview (and a detailed list where required / appropriate)
Reporting security issues
If you believe you’ve found a security issue, please email post@ceotxt.com with:
- a clear description
- steps to reproduce (if applicable)
- screenshots/logs (if safe to share)
Please do not publicly disclose vulnerabilities before we’ve had a chance to investigate and resolve them.
Contact
Rokter AS (CEOTXT)
Solbakken 2, 8516 Narvik, Norway
Email: post@ceotxt.com
