Legal
opsandgo Privacy Policy
Effective date: 18 November 2026
This Privacy Policy explains how opsandgo processes personal data, in line with Articles 13 and 14 of Regulation (EU) 2016/679 (General Data Protection Regulation, "GDPR"). It covers our website (opsandgo.com), our portal (app.opsandgo.com), our emails, and the data we handle while providing the managed hosting service.
1. Who we are
opsandgo is a managed AWS hosting service for React, Next.js and Node.js applications. Clients pay a fixed fee, and their app runs in their own AWS account, which we build and operate.
Controller: Tokolics Attila e.v. (Hungarian sole proprietor)
Seat: 8481 Somlóvásárhely, Vásár u. 12., Hungary
Registration number: 26437683 · Tax number: 65724473-1-39 · EU VAT number: HU65724473
Contact for privacy requests: hello@opsandgo.com
We have not appointed a data protection officer, as the law does not require one for our activity.
2. Our two roles
opsandgo as controller. We decide how and why data is processed for:
- visitors to our website and the measurement of our own marketing (section 3.2),
- people who contact us about the service (section 3.3),
- our clients, their team members and their portal accounts (section 3.4),
- billing of the service (section 3.5),
- the emails we send in our own name (section 3.6).
opsandgo as processor for the users of our clients' apps. Our clients' apps run in the clients' own AWS accounts. While operating that infrastructure (deployments, backups and restore tests, patching, monitoring, debugging) we may access the personal data those apps store: their databases, backups, logs and files. For that data the client is the controller, and we process it only on the client's behalf, under the Data Processing Agreement that forms part of our Terms of Service (GDPR Article 28). We do not copy it out of the client's account and do not use it for our own purposes. If you are a user of an app hosted through opsandgo, please contact the company that runs that app to exercise your rights; if you contact us, we forward your request to them.
3. What data we process, why, and on what legal basis
3.1 Website visitors
| Data | Purpose | Legal basis |
|---|---|---|
| Server logs (time of the request, requested address, response status, IP address and browser User-Agent), kept on our AWS hosting in Frankfurt for 30 days | Delivering, operating and securing the website | Art. 6(1)(f), our legitimate interest in operating a secure website |
- Data
- Server logs (time of the request, requested address, response status, IP address and browser User-Agent), kept on our AWS hosting in Frankfurt for 30 days
- Purpose
- Delivering, operating and securing the website
- Legal basis
- Art. 6(1)(f), our legitimate interest in operating a secure website
Our website loads its fonts from our own servers, not from Google. It sets no cookie until you make a choice in the cookie banner (section 10).
3.2 Website analytics and advertising measurement
| Data | Purpose | Legal basis |
|---|---|---|
| Visitor statistics with Umami on our website: page address, referring website, screen size, language, and the IP address and browser details used to tell your device type and approximate country and to group page views into a visit; clicks on our "Email Us" and "See Pricing" buttons | Understanding how our website is used, as totals | Art. 6(1)(f), our legitimate interest in understanding how our website is used (details in section 10) |
| Google Analytics 4, only after you accept analytics cookies: pages viewed, button clicks, screen size, browser, language, approximate location derived from your IP address (not stored by Google), a random visitor identifier in the _ga cookie | Understanding how the website is used and which campaigns bring visitors | Art. 6(1)(a), your consent given in the cookie banner; you can withdraw it at any time with "Cookie settings" in the footer |
| Meta Pixel, only after you accept marketing cookies: your page views on our website, the _fbp and _fbc cookies, your IP address and browser; if you are logged in to Facebook or Instagram, Meta can link these to your account | Measuring our ads on Facebook and Instagram | Art. 6(1)(a), your consent given in the cookie banner |
- Data
- Visitor statistics with Umami on our website: page address, referring website, screen size, language, and the IP address and browser details used to tell your device type and approximate country and to group page views into a visit; clicks on our "Email Us" and "See Pricing" buttons
- Purpose
- Understanding how our website is used, as totals
- Legal basis
- Art. 6(1)(f), our legitimate interest in understanding how our website is used (details in section 10)
- Data
- Google Analytics 4, only after you accept analytics cookies: pages viewed, button clicks, screen size, browser, language, approximate location derived from your IP address (not stored by Google), a random visitor identifier in the _ga cookie
- Purpose
- Understanding how the website is used and which campaigns bring visitors
- Legal basis
- Art. 6(1)(a), your consent given in the cookie banner; you can withdraw it at any time with "Cookie settings" in the footer
- Data
- Meta Pixel, only after you accept marketing cookies: your page views on our website, the _fbp and _fbc cookies, your IP address and browser; if you are logged in to Facebook or Instagram, Meta can link these to your account
- Purpose
- Measuring our ads on Facebook and Instagram
- Legal basis
- Art. 6(1)(a), your consent given in the cookie banner
Nothing optional loads or is collected before you choose in the cookie banner, and "Necessary only" declines all of it. For the collection of data through the Meta Pixel and its transmission to Meta, we and Meta Platforms Ireland Limited are joint controllers under Meta's Controller Addendum (https://www.facebook.com/legal/controller_addendum); Meta is solely responsible for what it does with the data afterwards, as described in its privacy policy (https://www.facebook.com/privacy/policy). Google Analytics processes data as our processor under the Google Ads Data Processing Terms (https://business.safety.google/adsprocessorterms/); we have switched off Google Signals and the sharing of data with other Google products. We do not use any of this for automated decisions about you. Details of the cookies are in our Cookie Policy (https://opsandgo.com/cookies).
3.3 People who contact us
| Data | Purpose | Legal basis |
|---|---|---|
| Your name, email address, company, and what you write to us about your app, your current hosting and your needs; our reply and the Service Order we send you | Answering your request, assessing whether your app is a fit, and preparing an offer | Art. 6(1)(b), steps prior to entering into a contract at your request; for contacts that do not lead to a contract, Art. 6(1)(f), our legitimate interest in answering enquiries |
| Access you give us to your repository and the configuration of your current hosting during setup | Moving your app to your new AWS account | Art. 6(1)(b), contract |
- Data
- Your name, email address, company, and what you write to us about your app, your current hosting and your needs; our reply and the Service Order we send you
- Purpose
- Answering your request, assessing whether your app is a fit, and preparing an offer
- Legal basis
- Art. 6(1)(b), steps prior to entering into a contract at your request; for contacts that do not lead to a contract, Art. 6(1)(f), our legitimate interest in answering enquiries
- Data
- Access you give us to your repository and the configuration of your current hosting during setup
- Purpose
- Moving your app to your new AWS account
- Legal basis
- Art. 6(1)(b), contract
Every "Email Us" button on our website opens your own email program; the website itself has no contact form and stores nothing when you click.
3.4 Clients, team members and portal accounts
| Data | Purpose | Legal basis |
|---|---|---|
| Business details of the client (legal name, address, tax number, contact person, notice email address) and the Service Order | Concluding and performing the contract | Art. 6(1)(b), contract |
| Portal accounts: email address (also used as username), first and last name, password (stored only as an argon2 hash), role, account creation and modification times, email confirmation and password reset tokens with their expiry | Creating and running your portal account, logging you in, managing access within your company | Art. 6(1)(b), contract |
| Session data: IP address, browser User-Agent, session expiry | Keeping you logged in, protecting accounts and detecting misuse | Art. 6(1)(b) for the login session; Art. 6(1)(f), our legitimate interest in the security of the service, for the IP address and User-Agent |
| Git access you create in the portal for your developers (name, the AWS IAM user or credential created in your own AWS account, creation and revocation times) | Letting your developers push to the CodeCommit repository in your account and letting you revoke that access | Art. 6(1)(b), contract |
| Status of your apps (deployments, the commit that is live, health checks), the daily AWS cost totals of your account retrieved through Cost Explorer, and the monthly report | Showing you the state and cost of your infrastructure | Art. 6(1)(b), contract |
| Secrets you enter in the portal (API keys, database passwords, tokens) | Writing them to the Parameter Store of your own AWS account | Art. 6(1)(b), contract; the values are written straight through and are not stored by us, and the portal cannot read them back |
| Actions you and we take in your AWS account | Logged by AWS CloudTrail in your own account, which you control | Not processed by us as controller |
- Data
- Business details of the client (legal name, address, tax number, contact person, notice email address) and the Service Order
- Purpose
- Concluding and performing the contract
- Legal basis
- Art. 6(1)(b), contract
- Data
- Portal accounts: email address (also used as username), first and last name, password (stored only as an argon2 hash), role, account creation and modification times, email confirmation and password reset tokens with their expiry
- Purpose
- Creating and running your portal account, logging you in, managing access within your company
- Legal basis
- Art. 6(1)(b), contract
- Data
- Session data: IP address, browser User-Agent, session expiry
- Purpose
- Keeping you logged in, protecting accounts and detecting misuse
- Legal basis
- Art. 6(1)(b) for the login session; Art. 6(1)(f), our legitimate interest in the security of the service, for the IP address and User-Agent
- Data
- Git access you create in the portal for your developers (name, the AWS IAM user or credential created in your own AWS account, creation and revocation times)
- Purpose
- Letting your developers push to the CodeCommit repository in your account and letting you revoke that access
- Legal basis
- Art. 6(1)(b), contract
- Data
- Status of your apps (deployments, the commit that is live, health checks), the daily AWS cost totals of your account retrieved through Cost Explorer, and the monthly report
- Purpose
- Showing you the state and cost of your infrastructure
- Legal basis
- Art. 6(1)(b), contract
- Data
- Secrets you enter in the portal (API keys, database passwords, tokens)
- Purpose
- Writing them to the Parameter Store of your own AWS account
- Legal basis
- Art. 6(1)(b), contract; the values are written straight through and are not stored by us, and the portal cannot read them back
- Data
- Actions you and we take in your AWS account
- Purpose
- Logged by AWS CloudTrail in your own account, which you control
- Legal basis
- Not processed by us as controller
The daily AWS cost retrieval and the status checks run through the access role you created in your AWS account; they read totals and status, not the data of your app's users.
3.5 Billing
| Data | Purpose | Legal basis |
|---|---|---|
| Billing name, address, tax number and email of the client; payment method (held by Stripe, not by us) | Charging the setup fee and the plan fee | Art. 6(1)(b), contract |
| Invoice data (buyer name, address, tax number, email) | Issuing invoices and keeping accounting records | Art. 6(1)(c), legal obligation under Hungarian tax and accounting law |
- Data
- Billing name, address, tax number and email of the client; payment method (held by Stripe, not by us)
- Purpose
- Charging the setup fee and the plan fee
- Legal basis
- Art. 6(1)(b), contract
- Data
- Invoice data (buyer name, address, tax number, email)
- Purpose
- Issuing invoices and keeping accounting records
- Legal basis
- Art. 6(1)(c), legal obligation under Hungarian tax and accounting law
Billing details are stored with Stripe, not in our database. Invoices are issued and emailed through Billingo, which reports invoice data to the Hungarian tax authority (NAV) as required by Hungarian law.
3.6 Emails we send
| Sent to | Legal basis | |
|---|---|---|
| Replies to your enquiry, the Service Order, and emails during setup | The person who contacted us and the client's contact person | Art. 6(1)(b), steps prior to a contract and the contract itself |
| Portal emails: email confirmation, password reset, team invitation | Portal account holders | Art. 6(1)(b), contract |
| Service notices: deployment failures, Emergencies, maintenance that needs downtime, changes to the Terms, unpaid invoices | The client's notice address | Art. 6(1)(b), contract |
| Monthly report | The client's notice address | Art. 6(1)(b), contract |
| Invoices | The client's billing email address | Art. 6(1)(b) and (c) |
- Replies to your enquiry, the Service Order, and emails during setup
- Sent to
- The person who contacted us and the client's contact person
- Legal basis
- Art. 6(1)(b), steps prior to a contract and the contract itself
- Portal emails: email confirmation, password reset, team invitation
- Sent to
- Portal account holders
- Legal basis
- Art. 6(1)(b), contract
- Service notices: deployment failures, Emergencies, maintenance that needs downtime, changes to the Terms, unpaid invoices
- Sent to
- The client's notice address
- Legal basis
- Art. 6(1)(b), contract
- Monthly report
- Sent to
- The client's notice address
- Legal basis
- Art. 6(1)(b), contract
- Invoices
- Sent to
- The client's billing email address
- Legal basis
- Art. 6(1)(b) and (c)
Automated emails (portal and service notices) are sent through Amazon Simple Email Service (AWS SES) in the EU. Personal correspondence from hello@opsandgo.com is sent and received through our own mail server, which we run ourselves in Hungary. We do not track whether you open our emails or click the links in them. We send no newsletter.
4. Where the data comes from
Most data comes directly from you. Data about team members may come from the client who invites them. Data about your AWS account (cost totals, status) comes from AWS through the access role you created. Billing details come from you through Stripe.
5. Recipients and subprocessors
We share personal data only with the service providers we need to run opsandgo:
| Recipient | What for | Data | Location |
|---|---|---|---|
| Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg | Hosting of our website and portal, database, job queue, server logs and backups; sending automated emails (SES) | Website logs, portal account data, app status and cost totals, email contents | Region eu-central-1 (Frankfurt, Germany) |
| Our own mail server, run by us in Hungary | Mailboxes for hello@opsandgo.com | Your correspondence with us | Hungary (EU) |
| Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland | Charging the setup fee and the plan fee (Stripe Billing) | Billing details and payment method of the client | Ireland (EU); see section 6 |
| Billingo Technologies Zrt., 1133 Budapest, Váci út 76, Hungary | Issuing and emailing invoices | Invoice buyer name, address, tax number, email | Hungary (EU) |
| Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (Google Analytics 4), only after your consent on our website | Website analytics, as our processor | Pages viewed, button clicks, visitor and session identifiers, approximate location (Google does not store the IP address) | Ireland (EU); may be processed by Google LLC in the United States, see section 6 |
| Meta Platforms Ireland Limited, Merrion Road, Dublin 4, Ireland (Meta Pixel), only after your consent on our website | Measuring our ads; joint controller for the collection and transmission, independent controller afterwards | Page views, _fbp and _fbc identifiers, IP address, browser | Ireland (EU); may be processed by Meta Platforms, Inc. in the United States, see section 6 |
- Recipient
- Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg
- What for
- Hosting of our website and portal, database, job queue, server logs and backups; sending automated emails (SES)
- Data
- Website logs, portal account data, app status and cost totals, email contents
- Location
- Region eu-central-1 (Frankfurt, Germany)
- Recipient
- Our own mail server, run by us in Hungary
- What for
- Mailboxes for hello@opsandgo.com
- Data
- Your correspondence with us
- Location
- Hungary (EU)
- Recipient
- Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland
- What for
- Charging the setup fee and the plan fee (Stripe Billing)
- Data
- Billing details and payment method of the client
- Location
- Ireland (EU); see section 6
- Recipient
- Billingo Technologies Zrt., 1133 Budapest, Váci út 76, Hungary
- What for
- Issuing and emailing invoices
- Data
- Invoice buyer name, address, tax number, email
- Location
- Hungary (EU)
- Recipient
- Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (Google Analytics 4), only after your consent on our website
- What for
- Website analytics, as our processor
- Data
- Pages viewed, button clicks, visitor and session identifiers, approximate location (Google does not store the IP address)
- Location
- Ireland (EU); may be processed by Google LLC in the United States, see section 6
- Recipient
- Meta Platforms Ireland Limited, Merrion Road, Dublin 4, Ireland (Meta Pixel), only after your consent on our website
- What for
- Measuring our ads; joint controller for the collection and transmission, independent controller afterwards
- Data
- Page views, _fbp and _fbc identifiers, IP address, browser
- Location
- Ireland (EU); may be processed by Meta Platforms, Inc. in the United States, see section 6
Your own AWS account is yours, under your own agreement with Amazon Web Services; we are not a recipient of your users' data in the sense of this section, we access it only as your processor (section 2).
We may also disclose data to authorities where the law requires it. We do not sell personal data.
6. International transfers
Our hosting provider is an EU company (Amazon Web Services EMEA SARL, Luxembourg), and our data is stored in its Frankfurt, Germany region. Its US parent company, Amazon Web Services, Inc., is covered by the EU-U.S. Data Privacy Framework certification of Amazon.com, Inc., so any transfer to it is covered by the European Commission's adequacy decision for the Framework (GDPR Art. 45). Stripe's US company, Stripe, Inc., Google LLC (Google Analytics) and Meta Platforms, Inc. (Meta Pixel) are also certified under the EU-U.S. Data Privacy Framework. Billingo is a Hungarian company and processes data in the EU. You can check certifications at https://www.dataprivacyframework.gov. The Framework was upheld by the General Court of the European Union in September 2025 (case T-553/23); an appeal is pending before the Court of Justice (case C-703/25 P). If the Framework is invalidated, we will rely on the standard contractual clauses approved by the European Commission that form part of our agreements with these providers (GDPR Art. 46(2)(c)), or stop the transfer. You can ask us for a copy of the relevant safeguards at hello@opsandgo.com.
7. How long we keep data
| Data | Retention |
|---|---|
| Invoices and accounting documents | Until the tax authority's right to assess the tax lapses: 5 years from the last day of the calendar year in which the tax return was due (Act CL of 2017 on the Rules of Taxation, Sections 78 and 202), so up to 6 years |
| Service Orders and contract correspondence | 5 years after the end of the contract (general limitation period, Ptk. 6:22) |
| Enquiries that do not lead to a contract | 12 months after our last reply, then deleted |
| Portal account data | While the contract is in force, then deleted within 30 days of the end of the contract, except data we must keep for the periods above |
| Session and security data (IP, User-Agent) | For the lifetime of the session (24 hours, or 14 days with "remember me"), then deleted within 30 days |
| App status and AWS cost totals in the portal | While the contract is in force, then deleted within 30 days of its end; the monthly reports we sent you stay in our mailbox under the contract correspondence rule |
| Server logs and backups of our website and portal | 30 days |
| Your cookie choice in your browser (opsandgo-consent) | 180 days, then the banner asks again |
| Umami visitor statistics | 12 months |
| Google Analytics user- and event-level data | 14 months (Google Analytics retention setting), aggregated reports longer |
| Data received by Meta through the Pixel | Kept by Meta under its own policy |
- Data
- Invoices and accounting documents
- Retention
- Until the tax authority's right to assess the tax lapses: 5 years from the last day of the calendar year in which the tax return was due (Act CL of 2017 on the Rules of Taxation, Sections 78 and 202), so up to 6 years
- Data
- Service Orders and contract correspondence
- Retention
- 5 years after the end of the contract (general limitation period, Ptk. 6:22)
- Data
- Enquiries that do not lead to a contract
- Retention
- 12 months after our last reply, then deleted
- Data
- Portal account data
- Retention
- While the contract is in force, then deleted within 30 days of the end of the contract, except data we must keep for the periods above
- Data
- Session and security data (IP, User-Agent)
- Retention
- For the lifetime of the session (24 hours, or 14 days with "remember me"), then deleted within 30 days
- Data
- App status and AWS cost totals in the portal
- Retention
- While the contract is in force, then deleted within 30 days of its end; the monthly reports we sent you stay in our mailbox under the contract correspondence rule
- Data
- Server logs and backups of our website and portal
- Retention
- 30 days
- Data
- Your cookie choice in your browser (opsandgo-consent)
- Retention
- 180 days, then the banner asks again
- Data
- Umami visitor statistics
- Retention
- 12 months
- Data
- Google Analytics user- and event-level data
- Retention
- 14 months (Google Analytics retention setting), aggregated reports longer
- Data
- Data received by Meta through the Pixel
- Retention
- Kept by Meta under its own policy
Data in your own AWS account (your app, its database, backups and CloudTrail logs) is yours and is not deleted by us when the contract ends.
8. Your rights
Under Articles 15-22 GDPR you have the right to:
- access your data and receive a copy (Art. 15),
- have inaccurate data rectified (Art. 16); you can also edit your name and email in your portal account,
- have your data erased (Art. 17),
- restrict processing (Art. 18),
- data portability (Art. 20),
- object to processing based on legitimate interest (Art. 21),
- withdraw consent at any time, without affecting the lawfulness of processing before withdrawal (Art. 7(3)); for analytics and marketing cookies, use "Cookie settings" in the website footer.
Your right to object
- Where we process your data on the basis of our legitimate interest (website server logs, visitor statistics, session security data, and enquiries that did not lead to a contract), you can object at any time by emailing hello@opsandgo.com. We will then stop that processing unless we can show compelling legitimate grounds that override your interests, rights and freedoms (Art. 21(1)).
We do not make decisions based solely on automated processing, including profiling, that produce legal or similarly significant effects for you (Art. 22).
To exercise your rights, email hello@opsandgo.com. We handle requests manually and respond without undue delay and within one month; where necessary we may extend this by two further months and will tell you why (Art. 12(3)). We may ask you to confirm your identity.
9. Right to lodge a complaint
You can lodge a complaint with a supervisory authority, in particular in the EU country where you live or work, or where you think the infringement happened. In Hungary this is:
Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH), Hungarian National Authority for Data Protection and Freedom of Information
Address: 1055 Budapest, Falk Miksa utca 9-11, Hungary
Postal address: 1363 Budapest, Pf. 9.
Phone: +36 (1) 391 1400
Email: ugyfelszolgalat@naih.hu
Website: https://naih.hu
You can also go to court.
10. Cookies and visitor statistics
Strictly necessary cookies need no consent: the session cookie that keeps you logged in to the portal (opsandgo-session) and the cookie that stores your cookie choice (opsandgo-consent). On our website a consent banner asks whether you accept Google Analytics (analytics) and the Meta Pixel (marketing); nothing optional loads before you choose, and you can change your choice at any time with "Cookie settings" in the footer. In the portal we use no analytics or advertising tools. The full list of cookies, their lifetimes and purposes is in our Cookie Policy (https://opsandgo.com/cookies).
Visitor statistics. On our website we use Umami, an open-source analytics tool that we run on our own server (analytics.creati.dev), hosted by Amazon Web Services in Frankfurt, Germany. It sets no cookies, does not track you across websites and does not run if your browser sends a Do Not Track signal. It records the page address, referrer, screen size and language, and uses your IP address and browser details to estimate your device type and approximate country and to group page views into a visit. Our analytics server may briefly log IP addresses for security purposes. We use these only as totals, never for advertising, and never link them to a client. Legal basis: our legitimate interest in understanding how our website is used (Art. 6(1)(f)). You can object under Art. 21 by writing to hello@opsandgo.com. We keep the statistics for 12 months.
11. Is providing data required?
Contact details, contract details and billing data are needed to conclude and perform the contract and to meet our legal obligations; without them we cannot provide the service. Analytics and marketing cookies are optional; declining them does not limit anything.
You must be at least 18 years old to hold a portal account. opsandgo is a service for businesses.
12. Security
We protect personal data with appropriate technical and organisational measures, including encrypted connections, hashed passwords, access to client accounts only through IAM roles with a unique external identifier, secrets written straight to the client's own Parameter Store without being stored by us, and access controls on our own systems.
13. Changes to this policy
We may update this Privacy Policy. We will publish the new version on this page with its effective date, and notify clients by email of material changes.