1. Who may use the service
ElectraDB is offered to businesses and professionals only, not to consumers. By signing up you confirm that you act for a company or in your trade, business or profession, and that you may bind the company you name at signup (“you”, the “customer”). You must be at least 18.
Keep your account details correct, keep your password and API keys secret, and tell us at [email protected] if you think they were exposed. You are responsible for what happens under your account and for the people you give access to.
2. The service
We run PostgreSQL databases for you in the region you choose (EU, US or Asia). High-availability plans keep a synchronous standby in a second site of the same region and fail over automatically; single-node plans run on one server and are restored from backup on another server if that one fails. Every PostgreSQL plan includes continuous encrypted backups and point-in-time restore for the last 7 days.
Key-value databases (Redis-compatible, on Valkey), where we offer them, keep data differently. Their replication is never synchronous, so on high-availability plans a failover can lose writes we had already acknowledged: in the asynchronous mode, the last moment of writes the replica had not received; in the bounded modes, at most about 1 or 5 seconds of them (while the replica is gone or that far behind, writes are briefly refused, then continue unreplicated). Like PostgreSQL databases they include encrypted point-in-time restore for the last 7 days, to a moment about a minute behind the present at the latest (changes reach the archive every 30 seconds), and also an encrypted snapshot of the whole dataset taken once a day, the latest 7 kept.
MariaDB databases (MySQL-compatible), where we offer them, run the MariaDB server, which works with MySQL clients, drivers and most MySQL applications; we do not promise that every MySQL feature behaves the same. On high-availability plans a replica in a second site of the same region takes over automatically. In the semi-synchronous mode (the default), a commit is acknowledged only once the replica has received it, so a failover loses no acknowledged commit; if the replica stops acknowledging for 10 seconds, the primary carries on alone and the replica does not take over until it has caught up again. In the asynchronous mode, a failover can lose the last commits the replica had not received (a replica more than 1,000 transactions behind does not take over). Like PostgreSQL databases they include continuous encrypted backups and point-in-time restore for the last 7 days, to the second, to a moment about a minute behind the present at the latest (changes reach the archive every 30 seconds). MariaDB and MySQL are trademarks of their owners: we use the names only to say which software we run and what it is compatible with, and we are not affiliated with or endorsed by them.
Plan sizes, prices and features are those shown on the pricing page when you order. We may improve or change the service; we will not reduce a paid plan's size or core features during a billing period, and we give at least 30 days' notice of material reductions.
You are responsible for your data, its lawfulness and your own copies of anything you cannot afford to lose. Our backups protect against failures of our infrastructure; they are not a substitute for your own exports.
3. Dev plan
The Dev plan is for development and testing: one server with a shared CPU and small limits, shown on the pricing page. It is a paid plan, billed like the others. An account can have up to 2 Dev databases of each kind (PostgreSQL, key-value, MariaDB). A Dev database cannot be resized in place; to move to a bigger plan, restore it into a new database on that plan. Dev databases have no SLA.
4. Fees, invoices and payment
Every plan is billed monthly in advance in euros through our payment provider Stripe, prorated to the day when you create, resize or delete a database. Prices exclude VAT and other taxes, which are added as the law requires (reverse charge where it applies: give us your VAT id).
If a payment fails we tell you by email and keep your databases running for a 7-day grace period. After that you cannot create new databases, and if the invoice stays unpaid we may suspend the service after further notice. We delete suspended databases only after at least 30 more days' written notice.
15-day money-back guarantee. If you are not satisfied in the first 15 days after your first payment, tell us and we refund what you paid.
5. Referrals
Every account has a referral link, on the Billing page. An account that signs up with it (the “referred account”) gets its first month free: from the day it creates its first database until the same day of the next month, 00:00 UTC, every database it runs is free, on any plan. A card is still needed, the usual account limits apply, and the free month is given once per referred account; a code can only be entered when signing up.
When the referred account's first paid month (the month after the free one) is over, the account that referred it earns a credit equal to what the referred account paid for invoices issued in that month, before VAT and leaving out anything paid with its own credit. The credit is added to your balance with Stripe and taken off your next invoices; it is not paid out in cash, cannot be transferred and lapses when you close your account. If the referred account pays nothing that month, there is no credit.
Referring yourself or accounts you control to get credit, or signing up repeatedly for free months, breaks these terms: we may refuse or reverse such credits and free months. We may change or end the referral program with 30 days' notice; credit already earned stays on your balance.
6. Acceptable use
You may not use the service to:
- store or distribute content that is illegal, or infringes someone else's rights;
- attack, scan or disrupt our systems, other customers or any third party;
- send spam, run malware or command-and-control servers, or mine cryptocurrency;
- get around plan limits, the Dev plan's per-account limit or our security measures;
- process special categories of personal data without the safeguards the law requires.
Report illegal content or abuse to [email protected] (see the Legal notice). We may restrict or suspend a database or account that breaks these rules, with a statement of reasons, and immediately when it is needed to stop harm.
7. Your data
You own the data in your databases. We process it only to provide the service and as the Data Processing Agreement describes; we do not look at it except when you ask us to, or when the law or an incident requires it. Your data stays in the region you choose.
When you delete a database it goes offline at once; its backups are kept for 7 days so you can restore it if the deletion was a mistake, then deleted permanently. Our handling of account data (your name, email, billing details) is described in the Privacy Policy.
8. Availability and support
Paid databases are covered by the Service Level Agreement: 99.9% monthly uptime, backed by service credits. Monitoring, automatic failover, backups and restores run around the clock, and you can start a restore yourself at any time. Our on-call team works business days, 09:00–18:00 CET, and answers at [email protected]; outside those hours we respond on a best-effort basis. We announce planned maintenance that may interrupt a database at least 48 hours in advance.
9. Term and termination
You can delete databases and close your account at any time; paid time is not refunded except under the money-back guarantee. We may end the agreement with 30 days' notice, or immediately if you seriously breach these terms (including non-payment after the notice above). After termination you can still restore or export for the 7 days the backups are kept; after that they are deleted.
10. Liability
Neither party is liable for indirect or consequential loss, lost profits or lost data that proper backups of your own would have avoided. Each party's total liability in a 12-month period is limited to the fees you paid us in that period. The service credits of the SLA are your remedy for unavailability.
These limits do not apply to liability for intent or gross negligence, for death or personal injury, to your payment obligations, or where the law does not allow limiting liability.
11. Confidentiality
Each party keeps confidential what it learns about the other that is not public, uses it only for this agreement, and protects it at least as well as its own confidential information.
12. Changes to these terms
We may update these terms. We email you material changes at least 30 days before they apply; if you do not agree, you can close your account before then. The version and date at the top show which terms are current; the one you accepted at signup is recorded on your account.
13. Law and courts
These terms are governed by the laws of Spain. The courts of Madrid have exclusive jurisdiction. Questions about these terms: [email protected].