Legal
opsandgo Terms of Service
Effective date: 18 November 2026 · Version 1.0
These Terms of Service ("Terms") govern the managed AWS hosting service provided under the opsandgo name (the "Service"). They apply to every client, to the opsandgo website (opsandgo.com) and to the opsandgo portal (app.opsandgo.com). Please read them carefully. By signing a Service Order, paying our first invoice, or using the portal, you accept them.
Service provider ("we", "us", "opsandgo"):
Tokolics Attila e.v. (Hungarian sole proprietor)
Registered seat: 8481 Somlóvásárhely, Vásár u. 12., Hungary
Sole proprietor registration number: 26437683
Tax number: 65724473-1-39 · EU VAT number: HU65724473
Email: hello@opsandgo.com
Important points at a glance
- opsandgo is for businesses only. Consumer withdrawal rights do not apply (section 2).
- Your app runs in your own AWS account. You own the account, the servers, the database and the data, and you pay AWS directly. We work through an access role that you can revoke at any time (section 5).
- We run the infrastructure. We do not write or fix your application code, except as paid extra work you approve in advance (section 4).
- We build a new, empty database for you. Moving your data into it is your job; we give you the access (section 4.1).
- Fees: a one-time setup fee plus a fixed monthly or yearly fee. The setup fee is billed on your first invoice, together with the first period. Yearly fees are paid in advance and are not refunded (section 7).
- Emergencies (production down or data at risk) are handled as soon as possible, outside business hours too. Everything else is handled during business hours. We do not offer a service level agreement (section 8).
- When you leave, everything keeps running in your account. We hand over the documentation and revoke our own access (section 10).
- Our liability is limited (section 14). You indemnify us against third-party claims arising from your app, your content and your data (section 15).
- The Data Processing Agreement in Annex 1 applies to the personal data inside your app that we may access while operating it (section 11).
1. Definitions
- Client, you: the business that orders the Service, whether a company, an agency ordering for its own clients, or a sole trader.
- App: your product, for example a web application or a SaaS. An App is made up of one or more Services.
- Service (of an App): one deployable part of an App, for example a frontend, an API or a worker. Each Service has its own deploy pipeline.
- Environment: a production or staging copy of an App. Each Environment has its own server(s) and database.
- Client AWS Account: the Amazon Web Services account opened in your name, in which your App runs.
- Access Role: the IAM roles in the Client AWS Account that you create from our template and that let us operate the account, each tied to an external identifier unique to you.
- Plan: one of the subscription plans listed in section 6.
- Setup: the one-time work of building your Client AWS Account and moving your App into it (section 4.1).
- Included hours: the hours of change work included in your Plan each month (section 6.3).
- Portal: the opsandgo web application at app.opsandgo.com, where you see the status of your Apps, your AWS costs, and manage secrets and git access.
- Service Order: the order form we send you by email, which names your Plan, your Apps, your Environments, the fees and the start date. A signed Service Order, or the payment of the first invoice issued on its basis, forms the contract together with these Terms.
- Business hours: Monday to Friday, 9:00 to 17:00 Central European Time, except Hungarian public holidays.
- Emergency: your production Environment is down or your data is at risk.
- DPA: the Data Processing Agreement in Annex 1, which is part of these Terms.
2. Who may use opsandgo
2.1 opsandgo is a service for businesses. You may order it only for the purposes of your trade, business or profession. Companies and sole traders may order; private individuals acting as consumers may not. By ordering, you confirm that you act as a business and not as a consumer.
2.2 Because opsandgo is provided only to businesses, the consumer protection rules on distance contracts, including the right of withdrawal under Directive 2011/83/EU and Hungarian Government Decree 45/2014. (II. 26.), do not apply to the contract between you and us.
2.3 The person who signs the Service Order or pays the first invoice must be authorised to accept these Terms on behalf of the business.
3. How the contract is formed (Ptk. 6:77-6:84)
3.1 Steps. You contact us by email with a few lines about your App. If it is a fit, we send you a Service Order by email with your Plan, your Apps and Environments, the setup fee, the monthly or yearly fee and the planned start date. The contract is concluded when you return the signed Service Order, or when you pay the first invoice issued on its basis, whichever comes first. We confirm the conclusion by email.
3.2 Language. The contract is concluded in English only.
3.3 Not a written contract. Unless you return a signed Service Order, the contract is not a contract put in writing ("írásba foglalt szerződés") and is not filed by us as a separate document. These Terms are available at https://opsandgo.com/terms at any time, and you can download, save and print them. Earlier versions are available on request at hello@opsandgo.com.
3.4 Code of conduct. We do not subscribe to any code of conduct.
3.5 Standard terms. These Terms are general terms and conditions (általános szerződési feltételek) within the meaning of Ptk. 6:77. If the Service Order or an individual written agreement with you contains different terms, those prevail over these Terms (Ptk. 6:80). Your own general terms and conditions do not apply to the Service.
4. The Service
4.1 Setup. For each App named in the Service Order, we:
- (a) open a new, empty AWS account with you on a short call (you enter the card and accept AWS's terms; the root user stays yours, with your own email address and two-factor authentication);
- (b) build the infrastructure in that account: servers, a new, empty managed database per App per Environment, DNS, TLS certificates, a deploy pipeline with rollback for each Service, backups, monitoring and alerts;
- (c) deploy your App's code to the new account, and switch your domain over at a time we plan with you;
- (d) connect your Apps to the Portal.
Setup usually takes about 72 hours from the kickoff call to your App running live in the new account, provided you give us access and answers when we need them and your data is loaded in time. This is an estimate, not a deadline.
Data migration. We do not migrate your data. We give you the connection details and credentials of the new database, and you or your developers move your data into it (database contents and uploaded files) and check it before the domain is switched over. We do not access your current database. If you ask, we help with the migration as extra work under section 6.4. We are not responsible for the completeness or correctness of the migrated data.
4.2 Ongoing operations. For each App under a Plan, we:
- (a) keep the deploy pipeline working, so that your developers can ship by pushing to git (from GitHub through an AWS connection, or to AWS CodeCommit in your account);
- (b) take daily automated database backups with point-in-time restore for the retention period of your Plan, and run a restore test of the production database once a month, inside your account;
- (c) install operating system and runtime patches every week, at times of low traffic;
- (d) run monitoring and alerts, and act on them;
- (e) handle Emergencies as described in section 8;
- (f) send you a monthly report on uptime, deploys, backups, restore tests, patches and your AWS costs;
- (g) give you and your team access to the Portal;
- (h) answer your questions within 3 business hours during business hours.
4.3 Supported apps. We run React, Next.js and Node.js applications with PostgreSQL or MySQL, or with an external database that you already have. We do not take on other languages or frameworks, and we do not take on apps built around AWS Lambda functions. We decide whether an App is a fit before we send a Service Order.
4.4 What is not included. We do not develop, debug or fix your application code, and we are not responsible for how your code behaves. We can help with code as extra work under section 6.4, if you ask and approve the hours in advance. We do not provide design, content, SEO or marketing services.
4.5 How we work. We build every account from the same templates and run them the same way, so that each setup is one we know. We may change our tooling and templates over time; if a change requires work in your account, we do it as part of the Plan and tell you about it in the monthly report.
5. Your AWS account and our access
5.1 Ownership. The Client AWS Account is yours. It is opened in your company's name, with your payment card, and the root user and its credentials stay with you. Everything we create in the account (servers, databases, pipelines, configuration, backups, logs) belongs to you.
5.2 AWS costs. AWS bills you directly for everything that runs in your account. We do not re-bill AWS costs and we add no markup. Before Setup we give you an estimate of the expected monthly AWS cost; it is an estimate, and the actual cost depends on your traffic, your data and the resources you ask for. You are responsible for keeping your AWS account in good standing, including payment of AWS invoices and compliance with the AWS Customer Agreement.
5.3 Access Role. To operate the account, you create two IAM roles from the template we give you: one for the Portal (reading status and costs, writing secrets, restarting services) and one for operations (deployments, maintenance, Emergencies). Both can be assumed only from our AWS account and only with an external identifier that is unique to you. The roles carry the permissions needed for the work in section 4, and no more.
5.4 Revoking access. You can revoke or narrow the Access Role at any time in your AWS console. While it is revoked, we cannot perform the Service, our obligations under section 4.2 are suspended, and fees remain due. If you revoke it because you are leaving, section 10 applies.
5.5 Changes you make. You and your team keep full access to the account. If you change resources that we manage without telling us first, we may have to repair them before we can continue our work; we charge that repair as extra work under section 6.4, and we are not responsible for problems the change causes. Tell us before you change managed resources, and we will help you do it safely.
5.6 Root user. We never use the root user and never ask for its password. Keep it protected with two-factor authentication and use it only when AWS requires it.
5.7 Your agreement with AWS. You hold the Client AWS Account under your own agreement with Amazon Web Services (the AWS Customer Agreement or another agreement that applies to you). You are the AWS customer for that account; we are not a party to that agreement, we do not resell AWS services, and the account is not part of any AWS organization we control. We act in the account only through the Access Role, on your behalf and on your instructions. Towards AWS, you remain responsible for all use of the account, including the work we do through the Access Role. opsandgo is an independent service provider and is not affiliated with, endorsed by or a partner of Amazon Web Services. Amazon Web Services and AWS are trademarks of Amazon.com, Inc. or its affiliates.
6. Plans, limits and extra work
6.1 Plans. The Plans at launch are:
| Plan | Monthly | Yearly | Setup | Scope |
|---|---|---|---|---|
| Essential | USD 490 | USD 5,390 | USD 1,490 | 1 App with 1 Service, production only, 7-day backup retention, 1 included hour a month |
| Growth | USD 890 | USD 9,790 | USD 2,490 | 1 App with up to 3 Services, production and staging, 14-day backup retention, 3 included hours a month, priority Emergency handling |
| Scale | USD 1,990 | USD 21,890 | USD 3,990 for the first App, USD 990 for each further App | Up to 3 Apps with up to 7 Services in total, production and staging, 35-day backup retention, 8 included hours a month, priority Emergency handling, monthly cost and architecture review |
| Agency | USD 1,290 | USD 14,190 | USD 990 per App | 5 client Apps with 1 Service each, production only, one AWS account per client, 7-day backup retention, 1 included hour per App a month, one invoice; USD 250 a month for each further App |
- Plan
- Essential
- Monthly
- USD 490
- Yearly
- USD 5,390
- Setup
- USD 1,490
- Scope
- 1 App with 1 Service, production only, 7-day backup retention, 1 included hour a month
- Plan
- Growth
- Monthly
- USD 890
- Yearly
- USD 9,790
- Setup
- USD 2,490
- Scope
- 1 App with up to 3 Services, production and staging, 14-day backup retention, 3 included hours a month, priority Emergency handling
- Plan
- Scale
- Monthly
- USD 1,990
- Yearly
- USD 21,890
- Setup
- USD 3,990 for the first App, USD 990 for each further App
- Scope
- Up to 3 Apps with up to 7 Services in total, production and staging, 35-day backup retention, 8 included hours a month, priority Emergency handling, monthly cost and architecture review
- Plan
- Agency
- Monthly
- USD 1,290
- Yearly
- USD 14,190
- Setup
- USD 990 per App
- Scope
- 5 client Apps with 1 Service each, production only, one AWS account per client, 7-day backup retention, 1 included hour per App a month, one invoice; USD 250 a month for each further App
Every Plan includes your own AWS account, a deploy pipeline with rollback, one database per App per Environment, daily backups with point-in-time restore, a monthly restore test on production, weekly patching, monitoring and alerts, git access for your developers, the Portal, the monthly report, and a reply within 3 business hours. The current Plans and prices are always shown on our pricing page (https://opsandgo.com/#pricing). The Service Order names your Plan.
6.2 Limits. If you need more Apps, Services or Environments than your Plan includes, you upgrade to the next Plan, add Apps where the Plan allows it, or we agree an individual price. A second Service for an Agency client App is priced individually. We tell you when you are about to exceed your Plan.
6.3 Included hours. Each Plan includes a number of hours a month for change work in your account: configuration changes, new environment variables, scaling, DNS changes, help with a deploy that failed because of the infrastructure, and similar. Unused hours do not carry over to the next month and are not refunded. We tell you before a request would exceed your Included hours.
6.4 Extra work. Work beyond your Included hours, repairs under section 5.5, and help with your application code are charged at USD 120 per hour, in units of 15 minutes, only after you approve the estimate in writing (email is enough). Extra work is added to your next invoice.
7. Fees, billing and invoicing
7.1 Prices and taxes. All prices are in US dollars. We are a Hungarian small business exempt from VAT (alanyi adómentes), so our invoices carry no Hungarian VAT. If your business is established in another EU Member State, the reverse charge applies: you account for VAT in your own country under your own VAT number, which you must give us, and the invoice says so. If your business is established outside the EU, Hungarian VAT does not apply. Where the law requires us to charge VAT in the future, it is shown on your invoice.
7.2 Setup fee. The setup fee is due once per App and is billed on your first invoice, together with your first monthly or yearly period. Setup starts after the first invoice is paid. The setup fee is not refunded once Setup has started.
7.3 Subscription. The Plan fee is charged in advance for each billing period (one month or one year). The first period starts on the start date in the Service Order, or on the day your first App goes live in the new account if that is earlier. The subscription renews automatically for the same period until you cancel it (section 10).
7.4 Payment. You pay by card or bank debit through Stripe, in the Portal or through the payment link in our invoice email. By adding a payment method you authorise us to charge the Plan fee, extra Apps and approved extra work to it. Monthly Plans are paid by card or bank debit only. For yearly Plans we can invoice by bank transfer on request, with 8 days' payment term.
7.5 Invoices. We issue invoices through our invoicing provider Billingo, which reports invoice data to the Hungarian tax authority (NAV) as required by Hungarian law, and send them by email to your billing email address.
7.6 Changing your Plan. An upgrade takes effect immediately; you pay the difference between the two Plans for the rest of the current period. A downgrade or a switch between monthly and yearly billing takes effect at the end of the current period. Nothing is refunded for the current period.
7.7 Refunds. Fees already paid are not refunded, including on downgrade or cancellation, unless the law requires otherwise or we agree otherwise in writing. Yearly fees are paid for the whole year.
7.8 Failed payments. If a charge fails, we tell you by email and Stripe retries the charge over the following two weeks. If the invoice is still unpaid 14 days after its due date, we may suspend our services under section 9.3 until it is paid. Your infrastructure keeps running in your account; only our work stops. Unpaid amounts remain due, with the statutory default interest.
8. Response, Emergencies and availability
8.1 Business hours. We answer your messages within 3 business hours, during business hours. Change requests are scheduled within business hours.
8.2 Emergencies. If your production Environment is down or your data is at risk, we start working on it as soon as possible after we learn about it, outside business hours too, including nights and weekends. Alerts from our monitoring and emails to hello@opsandgo.com with "emergency" in the subject are the ways to reach us. Growth and Scale Plans are handled first when several Emergencies happen at the same time. We do not promise a response time in minutes or hours, and we do not provide guaranteed around-the-clock staffing.
8.3 No SLA. We aim to keep your App available and secure, but we do not guarantee uninterrupted or error-free operation, and we do not offer a service level agreement, uptime percentage or service credits, unless an individual written agreement says otherwise. Availability depends on AWS, on your code and on your traffic, which we do not control.
8.4 Maintenance. Weekly patching and other maintenance may cause short restarts. We do them at times of low traffic and tell you in advance about maintenance that needs downtime.
8.5 Backups and data. Backups and the retention period are described in section 6.1. We can restore your database to any point within the retention period of your Plan. We cannot restore data older than that, and we are not responsible for data that is stored outside the managed database and its backups unless we agreed in writing to back it up.
9. Your responsibilities
9.1 Your App. You are responsible for your application code, its dependencies, its licences and its security, for the content you publish with it, and for the lawfulness of your App and of the data you process with it.
9.2 Cooperation. You give us what we need to do the work on time: access to your repository and the configuration of your current hosting during Setup, the migration of your data under section 4.1, decisions when we ask for them, a working contact who can answer during business hours, and the DNS changes we ask for if your DNS is not in the Client AWS Account.
9.3 Suspension by us. We may suspend our services under section 4.2, in whole or in part, with notice to you by email, if:
- (a) your invoice is unpaid 14 days after its due date (section 7.8);
- (b) you seriously breach these Terms, in particular sections 9.1 or 9.5;
- (c) your App or your use of the Service is unlawful, or we receive a substantiated notice that it is; or
- (d) your App endangers the security of other systems or of our tooling.
We lift the suspension once the reason no longer exists. Your infrastructure keeps running in your account during a suspension; we only stop working on it.
9.4 Secrets. You enter the secrets of your App (API keys, database passwords, tokens) in the Portal. They are written to the Parameter Store of your AWS account and are not kept by us. You are responsible for keeping them confidential, for rotating them when needed, and for the access you give your team members in the Portal.
9.5 Acceptable use. You must not use the Service, or allow others to use it, to run unlawful content or activities, to send spam, to mine cryptocurrency, to attack or scan other systems, or to circumvent the limits of your Plan. You must not reverse engineer our tooling, except as the law expressly allows.
9.6 Team members and agencies. You are responsible for the people you invite to the Portal and for what they do there. If you are an agency ordering for your own clients, you remain our client and our only contact; you are responsible for your agreements with your clients, including the ownership of their AWS accounts, and you warrant that you are authorised to order the Service for them.
10. Term, cancellation and handover
10.1 No minimum term. There is no minimum contract term. The contract runs until it is cancelled or terminated.
10.2 Cancellation by you. You can cancel at any time by emailing hello@opsandgo.com. Cancellation takes effect at the end of the current billing period, monthly or yearly, without refund. Until then everything works as before.
10.3 Termination by us. We may terminate the contract with 30 days' notice by email, without giving reasons; in that case we refund the part of any yearly fee that relates to the period after termination. We may terminate with immediate effect if you seriously breach these Terms and do not remedy the breach within a reasonable deadline we set, or if the breach cannot be remedied.
10.4 Handover. When the contract ends, for whatever reason:
- (a) everything keeps running in your account: servers, database, pipelines, backups and data are yours and stay where they are;
- (b) we hand over the documentation of your setup (the runbook), so that any AWS engineer you choose can take over;
- (c) we revoke our own access and ask you to delete the Access Role;
- (d) your access to the Portal ends, and we delete your Portal data under section 7 of the Privacy Policy;
- (e) we do not delete, stop or change anything in your account unless you ask us to in writing.
After the end date we no longer monitor, patch, back up or support your infrastructure, and the costs of running it continue to be billed to you by AWS until you change or close the resources.
10.5 Survival. Amounts already due remain payable. Sections 11, 13, 14, 15 and 18 survive the end of the contract.
11. Data protection
11.1 Your data. You keep all rights to your code, your content and the data in your App.
11.2 Data processing agreement. Your App may process personal data of your users and customers. While operating your infrastructure we may access that data, for example when we restore a backup, debug a failed deploy or look at logs. For that data you are the controller and we are your processor. The DPA in Annex 1 forms part of these Terms and applies automatically when the contract is concluded (GDPR Article 28(3)).
11.3 Our own processing. We process the personal data of you and your team members as controller, as described in our Privacy Policy (https://opsandgo.com/privacy).
12. Intellectual property
12.1 Your rights. Your code, content and data remain yours. The infrastructure configuration we deploy into your account (pipelines, server configuration, scripts, templates) becomes yours to use, modify and keep in that account, also after the contract ends.
12.2 Our rights. Our tooling, templates, the Portal, its software and design, and the opsandgo name and logo belong to us. You may not resell them or offer them to third parties as a service of your own. The licence in section 12.1 does not extend to the Portal.
12.3 References. We may name you as a client and show your logo in our references with your prior consent, which you can withdraw at any time by email.
12.4 Feedback. If you send us ideas or feedback, we may use them freely, without obligation to you.
13. Confidentiality
Each party will keep confidential the non-public information it receives from the other party in connection with the Service, including your secrets, code, data and business information, and our templates and procedures, and use it only to perform the contract, unless it is publicly available or must be disclosed by law. This obligation survives the end of the contract.
14. Liability
14.1 We are liable for damage caused by our breach of contract under the rules of the Hungarian Civil Code (Ptk. 6:142 and following), subject to the limits below.
14.2 To the extent permitted by law, we are not liable for:
- (a) loss of profit, loss of revenue, loss of data that lies outside the backups described in section 8.5 or that is older than your retention period, or loss of goodwill;
- (b) indirect or consequential damage;
- (c) outages, changes or decisions of AWS, Stripe or other third parties, or the costs AWS bills you;
- (d) damage caused by your code, your content, your data migration, your changes under section 5.5, or your breach of section 9;
- (e) damage arising while the Access Role was revoked or our services were suspended; and
- (f) vulnerabilities in third-party software (operating systems, runtimes, libraries, AWS services) and attacks that exploit them, unless the damage results from our failure to install, within the weekly patching under section 4.2(c), an operating system or runtime patch that was available.
14.3 To the extent permitted by law, our total liability for all claims arising out of or in connection with the contract is limited to the total fees you paid us in the 3 months before the event giving rise to the claim.
14.4 No limitation where the law prohibits it. Nothing in these Terms excludes or limits our liability for a breach of contract caused intentionally, or for a breach that causes damage to human life, physical integrity or health (Ptk. 6:152). Any limitation applies only to the extent it does not violate mandatory law, including Ptk. 6:102 on unfair standard terms.
15. Indemnity
You will indemnify us and hold us harmless against all claims, damages, fines and reasonable costs (including legal fees) that third parties, including your users, your clients, AWS and authorities, raise against us because of your App, your content, your processing of personal data, or your breach of these Terms or of the law.
16. Force majeure
Neither party is liable for delay or failure to perform caused by circumstances beyond its reasonable control, including outages of AWS or network providers, natural disasters, epidemics, war, strikes and acts of authorities. Payment obligations for periods already used are not affected.
17. Notices and changes
17.1 Notices. We send notices to the email address named in the Service Order and show them in the Portal where relevant. A notice sent by email counts as received when it becomes accessible in the recipient's mailbox. Keep that address up to date. You can send notices to us at hello@opsandgo.com.
17.2 Changes to these Terms. We may change these Terms, including Plans and prices. We email you about the change at least 30 days before it takes effect and publish the new version with its effective date. Price changes apply from your next billing period after the change takes effect; for yearly Plans, from your next yearly period. If you do not agree with a change, you may cancel before it takes effect. If you keep using the Service after the effective date, you accept the changed Terms. We may make changes with shorter notice where the law or an authority requires it, or where a change is needed to address a security risk.
18. Governing law and disputes
18.1 These Terms and the contract are governed by Hungarian law, excluding its conflict-of-law rules and excluding the UN Convention on Contracts for the International Sale of Goods.
18.2 We will try to settle disputes amicably first; please contact us at hello@opsandgo.com.
18.3 For disputes that cannot be settled amicably, the parties agree on the exclusive jurisdiction of the Ajka District Court (Ajkai Járásbíróság) or, depending on the value of the claim, the Veszprém Regional Court (Veszprémi Törvényszék), the courts competent for our registered seat, to the extent the law allows such a choice.
19. Final provisions
19.1 Whole agreement. These Terms, the Service Order, the DPA, the Privacy Policy and any individual written agreement form the entire agreement between you and us about the Service.
19.2 Assignment. You may not transfer the contract to another party without our prior consent. We may transfer the contract to a successor of the opsandgo business, with notice to you.
19.3 Severability. If any provision is invalid, the rest of the Terms remain in force, and the invalid provision is replaced by a valid provision closest to its purpose.
19.4 No waiver. If we do not enforce a right, we do not waive it.
Annex 1: Data Processing Agreement
This Data Processing Agreement ("DPA") is part of the Terms and is concluded between you, the Client, as controller, and opsandgo as processor, under Article 28 of the GDPR. Terms defined in the Terms have the same meaning here.
1. Subject matter and duration
We operate the infrastructure of your App inside your own AWS account. While doing so we may access the personal data your App stores or processes: in its database, its backups, its logs, its files and its queues. The DPA covers that access. It applies for as long as the contract is in force and we hold an Access Role in your account.
2. Nature and purpose of the processing
Access to, and where needed copying within your account of, the data, solely to provide the Service: deployments, backups and restore tests, patching, monitoring, debugging failures, and Emergencies. We do not copy your users' data out of your AWS account, we do not use it for our own purposes, and we do not analyse it beyond what a specific operation requires.
3. Categories of data subjects
The users, customers and other persons whose data your App processes, and your own team members whose data appears in your App or its logs.
4. Categories of personal data
Whatever your App stores. Typically account and contact data, order and usage data, and technical data such as IP addresses in logs. You must tell us before Setup if your App processes special categories of data (Article 9 GDPR) or data subject to specific confidentiality rules, so that we can agree additional measures.
5. Your obligations as controller
You are responsible for the lawfulness of the processing in your App, including a valid legal basis, informing data subjects, and answering their requests. Your instructions to us are the Terms, this DPA, the Service Order and the requests you send us by email or through the Portal.
6. Our obligations as processor (Article 28(3) GDPR)
We will:
- (a) access and process the data only on your documented instructions, unless EU or Member State law requires otherwise, in which case we inform you before processing, unless the law prohibits this;
- (b) ensure that every person who accesses the data on our side is bound by confidentiality;
- (c) take the security measures described in section 8;
- (d) engage subprocessors only under section 9;
- (e) help you, as far as possible and taking the nature of the processing into account, to respond to data subject requests under Articles 15-22 GDPR, for example by restoring or exporting data on your request;
- (f) help you meet your obligations under Articles 32-36 GDPR (security, breach notification, data protection impact assessment and prior consultation), taking into account the information available to us;
- (g) end the processing at the end of the contract under section 11;
- (h) make available the information needed to demonstrate compliance with Article 28 and allow and contribute to audits under section 10; and
- (i) inform you immediately if we consider that an instruction infringes the GDPR or other data protection law.
7. Personal data breaches
We will notify you without undue delay, and at the latest within 48 hours of becoming aware of it, of a personal data breach that affects the infrastructure we operate for you, by email to your notice address, with the information available to us at that time, and provide further information as it becomes available. You are responsible for notifying the supervisory authority and the data subjects where required.
8. Security measures (Article 32 GDPR)
We apply at least the following measures: all access to your account goes through the Access Role with an external identifier unique to you, from our AWS account, and is logged by AWS CloudTrail in your account; we never use your root user; encrypted connections (TLS) for every service; encrypted storage for databases and backups; secrets kept in the Parameter Store of your account, not in our systems; servers reachable for administration only over AWS Systems Manager or restricted SSH; weekly security patches; daily backups with point-in-time restore and a monthly restore test; restore tests run inside your account on a temporary database that is deleted afterwards; and a documented setup handed over to you.
9. Subprocessors
Your users' data stays in your own AWS account, which you hold under your own agreement with Amazon Web Services; AWS is your provider, not our subprocessor. We engage no subprocessor for your users' data. For the Portal, which stores only your team's account data, the status of your Apps and your AWS cost totals, we use Amazon Web Services EMEA SARL (region eu-central-1, Frankfurt), as described in section 5 of our Privacy Policy. If we ever need a subprocessor for your users' data, we will inform you by email at least 30 days in advance; you may object on reasonable data protection grounds within that period, and if we cannot offer a solution, you may terminate the contract before the change takes effect.
10. Audits
On request, at most once a year, we provide you with the information needed to show that we comply with this DPA; the CloudTrail logs in your own account show every action we take. Where that is not sufficient, you or an independent auditor bound by confidentiality may audit our processing, with at least 30 days' notice, during business hours and without disrupting the Service; you bear the costs of the audit.
11. End of processing
When the contract ends, we revoke our own access and ask you to delete the Access Role. Because the data never left your account, there is nothing for us to return or delete; backups and restore-test copies are in your account and under your control. Any temporary copies made during a specific operation (for example a database dump used for a migration) are deleted by us at the end of that operation, at the latest when the contract ends.
12. Transfers outside the EEA
We access your data from the European Union. Your AWS account is in the region you chose with us, by default eu-central-1 (Frankfurt). We do not transfer your users' data outside the EEA.
13. Liability and precedence
Section 14 of the Terms applies to liability under this DPA. If this DPA conflicts with the Terms, this DPA prevails for the processing of your users' data.