Privacy Policy
Last updated: September 2, 2026
This Privacy Policy describes how QuymnyDB (“we”, “us”, “our”) collects, uses, and protects information when you use our cloud SQL database platform and related services (the “Service”).
1. Information We Collect
We may collect:
- Account information — name, email address, company name, and authentication credentials.
- Billing information — plan selection, payment references, and limited transaction metadata needed to fulfill subscriptions. Card details are processed by our payment provider (e.g. Notch Pay) and are not stored in full on our servers.
- Usage and technical data — database usage metrics, query counts, bandwidth, IP address, browser type, and logs necessary to operate and secure the Service.
- Support communications — messages you send to support or via tickets.
- Security data — two-factor authentication (2FA) configuration and recovery keys when you enable them.
2. How We Use Information
- To provide, maintain, and improve the Service.
- To authenticate users and protect accounts (including optional and recommended 2FA).
- To process payments and manage subscriptions.
- To respond to support requests and send service-related notices.
- To detect abuse, fraud, and security incidents.
- To comply with applicable law.
3. Your Database Content
You control the data you store in databases you create on QuymnyDB. We process that content only to operate the Service (e.g. execute queries you request, backups where applicable, and infrastructure management).
4. Sensitive and Prohibited Data
You are solely responsible for the content of your databases. Without limitation, you should not use the Service to store or process:
- Sensitive personal data that you are not lawfully entitled to process.
- Stolen account credentials, password dumps, or data obtained through unauthorized access.
- Licensed, copyrighted, or patented material belonging to third parties without authorization.
- Any data whose storage or distribution is illegal in your jurisdiction or ours.
QuymnyDB does not monitor every row of customer data by default. Responsibility for legality and rights clearance of stored content remains with you.
5. Account Security and 2FA
You are responsible for protecting your account credentials. We strongly recommend enabling two-factor authentication (2FA) for stronger security. When 2FA is enabled, access may require a time-based code or recovery key in addition to your password.
If you disable 2FA or fail to secure recovery keys, you accept the increased risk of unauthorized access. We are not liable for losses arising from compromised credentials where reasonable security measures (including available 2FA) were not used.
6. Sharing of Information
We do not sell your personal information. We may share limited data with:
- Infrastructure and payment processors necessary to run the Service.
- Authorities when required by law or to protect rights, safety, or security.
- Successors in the event of a merger, acquisition, or asset transfer, subject to this policy.
7. Data Retention
Account and billing records are retained while your account is active and for a reasonable period afterward for legal, tax, and security purposes. Database content is retained according to your plan and account status; deletion of an account or database removes associated content subject to residual backups and legal holds.
8. International Transfers
The Service may be hosted or processed in multiple regions. By using QuymnyDB you understand that your information may be transferred to and processed in countries other than your own.
9. Your Choices
- Update profile and security settings from your dashboard.
- Enable or manage 2FA where available.
- Request account deletion subject to the Terms of Service and verification steps.
- Contact us about privacy requests at the email below.
10. Contact
For privacy questions or requests, contact:
Email: info@quymny.com
11. Changes
We may update this Privacy Policy from time to time. Continued use of the Service after changes take effect constitutes acceptance of the updated policy. The “Last updated” date at the top will be revised accordingly.