This policy explains how OMCONEX DIGITAL TECHNOLOGY COMPANY LIMITED (“Omconex”) protects your account, content and connection credentials, how it handles incidents, and how you can report a security vulnerability.
Article 1. Principles
1.1. Omconex applies technical and organisational measures to protect accounts, content, credentials and the continuity of the service. Omconex does not publish infrastructure details, keys or internal addresses because that information could help an attacker.
1.2. Omconex has not published ISO, SOC or PCI certification. If it obtains a certification or service-level commitment (SLA), it will publish it separately.
Article 2. Protecting accounts
2.1. Access is checked by account, workspace and resource. Sign-in sessions are short-lived and renewed automatically; you can see and sign out of open sessions in your account settings, and turn on two-factor authentication.
2.2. Omconex staff access your data only when needed for a support request or incident, and only within their duties. Omconex never asks for your password or OTP.
Article 3. Protecting data
3.1. Data between you and Omconex travels over HTTPS.
3.2. Tokens, API keys and service account key files you provide for connections are encrypted and stored separately, and are not shown again in the app.
3.3. Omconex logs requests, errors, sign-ins and important changes to detect and investigate incidents. Omconex makes regular backups to recover from system failures; backups do not replace keeping your own copies of important documents.
3.4. Do not put keys, passwords or OTPs into article titles, URLs, AI requests or support emails.
Article 4. Providers and external connections
4.1. Omconex requests only the permissions it needs when connecting to Google, Meta, your website or other providers, and chooses providers that suit its data-protection requirements.
4.2. When an outside platform fails or changes permissions, Omconex checks the real state before retrying to avoid duplicate posts, duplicate charges or data exposure.
Article 5. Handling incidents
5.1. When Omconex sees signs of an incident it verifies, contains (which may mean pausing related tasks, connections or sessions), assesses the scope and remediates.
5.2. Omconex notifies affected people and the competent authority as the law requires. The notice states what has been confirmed, what you should do and how to reach us.
Article 6. What you should do
6.1. Protect your sign-in email, devices and connected accounts; turn on two-factor authentication; review members when staff change.
6.2. If you suspect unauthorised access: sign out your sessions, remove unneeded access, change or revoke keys where they were issued (Google, Meta, your website), pause risky publishing schedules and tell Omconex. Act only on requests that come through Omconex’s official channels.
Article 7. Reporting a vulnerability
7.1. Email [email protected] with the subject “Security report”, including the feature or URL, time and time zone, the shortest steps to reproduce, and screenshots or error codes (with data masked). Do not send session cookies, tokens, API keys, passwords or private keys.
7.2. When testing security, please do not access or download other people’s data, disrupt the service or install malware. If you come across data that is not yours, stop and tell Omconex. Omconex acknowledges each report it receives.
Article 8. Contact details
8.1. Operator: OMCONEX DIGITAL TECHNOLOGY COMPANY LIMITED (CÔNG TY TNHH CÔNG NGHỆ SỐ OMCONEX), enterprise code 0111674029, address Unit 6B, Floor 6, Song Da mixed-use building, 131 Tran Phu Street, Ha Dong Ward, Hanoi, Vietnam, email [email protected].
8.2. Website: https://omconex.com. App: https://app.omconex.com.
Policy enquiries
Contact Omconex about this policy, personal data or a transaction. Do not send passwords, OTPs or connection secrets.
[email protected] →