Security Policy
Last updated: 8 October 2026
The short version:
- Everything runs over HTTPS. Bot tokens are encrypted at rest. There are no passwords to steal: you log in with one-time codes, Telegram or your VooSquare Voo ID.
- You can see every logged-in device and log any of them out. We email you about logins from a new device or country.
- Staff access is limited by role and every staff action is logged.
- Found a vulnerability? Tell us at [email protected]. We will not take legal action against good-faith research that follows the rules below.
1. How we protect Castvoo
Practical, layered protection.
- Encryption in transit. All connections to Castvoo use HTTPS.
- Encryption at rest for secrets. Bot tokens and the keys for our payment and AI providers are stored encrypted with AES-256-GCM.
- Login without passwords. You sign in with a one-time code sent to your email, with Telegram, or with your VooSquare Voo ID, the single sign-on shared across Zedapex tools.
- Devices and alerts. Settings → Security lists every device logged in to your account. You can log out one or all of them. We email you when your account is used from a new device or country.
- Staff access. Our team sees only what their role needs, and staff actions are recorded in an audit log.
- Protection against abuse. Rate limits, request checks against cross-site attacks and strict browser security headers protect the website and dashboard.
- Payments. Card and bank payments happen on our payment partners' own checkout pages. We never receive or store full card numbers.
- Uploads. We remove photo metadata, such as location, from screenshots you send to support.
2. Your part
Security works best when we both play our part.
- Never share your login codes with anyone, including people who say they are from Castvoo. We will never ask for them.
- Keep your email account and Telegram account secure, since they are how you log in.
- Keep your bot tokens private outside Castvoo. If a token leaks, revoke it in @BotFather and connect the new one.
- Give teammates and setup helpers their own access, and remove them when they no longer need it.
- Tell us straight away at [email protected] if you think someone got into your account.
3. Reporting a vulnerability
We welcome reports from security researchers. If you believe you have found a security vulnerability in Castvoo, email [email protected] with the subject "Security report". Please include:
- a description of the issue and where it is;
- the steps to reproduce it, and a proof of concept if you have one; and
- what an attacker could do with it.
We will confirm that we received your report, keep you updated while we investigate, and tell you when it is fixed.
4. Rules for good-faith research
Test responsibly and we will treat you as a partner, not a threat. When researching Castvoo:
- use only accounts you own or have permission to test, and never access, change or delete other customers' data;
- stop as soon as you reach data that is not yours, and tell us;
- do not run denial-of-service attacks, spam, social engineering or physical attacks, and do not test against our providers (such as Telegram, payment partners or hosting);
- do not send messages to real Telegram users as part of a test; and
- give us reasonable time to fix the issue before telling anyone else about it.
If you follow these rules, we will not pursue legal action against you for your research. We do not currently run a paid bug bounty, but we are glad to thank researchers publicly with their permission.
5. If there is a breach
We tell you, and the authorities where required. If a breach affects your personal data, we will tell you without undue delay and notify the relevant authorities as the law requires. Our Data Processing Addendum explains what we do when your subscribers' data is affected.
6. Contact
Security reports: [email protected]
Privacy questions: [email protected]
Zedapex Limited, Lagos