Terms & Conditions
Last updated: 2026-09-29 · Version 2.0
These Terms & Conditions (the "Terms") set out the rules for using the SGTM.space server-side tagging platform (the "Service") operated by BEO TECHNOLOGY SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ, including the rules of the Partner Programme. They are the terms for services provided electronically within the meaning of Article 8 of the Polish Act of 18 July 2002 on providing services by electronic means. The Service is for businesses only (section 4).
1. Definitions
- Operator, we, us: BEO Technology sp. z o.o., the company described in section 2.
- Customer, you: the business that registers an Account or uses the Service and, for matters of an Organization, the business on whose behalf that Organization acts (section 6).
- Account: an account in the Service assigned to one person and their e-mail address.
- Organization: a workspace in the Service that owns Containers, their plans, invoice details, discount codes and Cloudflare connections.
- Member: an Account added to an Organization. Organization Admin: a Member with the admin role.
- Service / Platform: SGTM.space with the customer dashboard, APIs, Containers, Add-ons, the website audit, the public scanner, the Academy and support chat and tickets.
- Container: the setup in the Service for one of the Customer's websites. It covers the edge (Custom domain, Cloudflare Worker, Better Loader) and, once a Google Tag Manager container config is pasted, a hosted server-side Google Tag Manager (sGTM) tagging server.
- Custom domain: a domain or sub-domain you connect to a Container through Cloudflare custom hostnames.
- Add-on: an optional Container feature you switch on and configure in the dashboard (section 7).
- Plan: the pricing plan of one Container, either free (the Free plan) or paid.
- Request: an HTTP request counted against the plan limit, as set out in section 13.
- Visitor / End User: a visitor to your websites whose requests pass through a Container.
- DPA: the Data Processing Agreement that governs our processing of Visitor personal data on your behalf.
- Dodo Payments: the payment provider that sells the plans as merchant of record.
- Partner Programme, Partner: the programme described in section 27 and a Customer who has joined it.
2. Who we are
The Service is operated by:
- BEO TECHNOLOGY SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ
- Prezydenta Gabriela Narutowicza 40 / 1, 90-135 Łódź, Poland
- KRS 0001103255 · NIP (Polish tax ID) 7252343252 · EU VAT PL7252343252 · REGON 528493956
- Contact: [email protected]
3. Acceptance, documents and language
These Terms, together with the Privacy Policy, the Cookie Notice and the Data Processing Agreement, form the entire agreement between the Customer and the Operator regarding the Service. You accept all four documents in full by ticking the required box when you create an Account, also when you sign up with Google or GitHub. The agreement is concluded when the Account is created, for an indefinite period. If any conflict arises, the DPA prevails on matters of Visitor personal-data processing, and these Terms prevail on all other matters, unless a separately signed agreement states otherwise.
At registration we record the versions of all four documents that you accepted, with the date, IP address and browser identifier. That contractual acknowledgement is separate from optional analytics or advertising cookies consent, which you control through CookieTip, and from marketing e-mail consent. You may withdraw either at any time.
We publish these Terms in Polish and in English. The Polish version is binding and the English version is a translation. The website in its other languages (German, French, Spanish and Dutch) shows the English version. These Terms are available free of charge at https://sgtm.space/nl/terms in a form you can download, save and print.
4. Business customers only
The Service is intended for businesses only, for purposes related to their business or professional activity. By creating an Account you declare that you use the Service for your business, or that you act on behalf of a business and are authorized to do so. We do not contract with consumers within the meaning of Article 221 of the Polish Civil Code (the "Civil Code").
If you are a natural person who concludes the agreement in direct connection with your business, and the agreement shows that it is not of a professional nature for you, as follows in particular from the subject of your business disclosed in the Polish Central Register and Information on Economic Activity (CEIDG), you enjoy the protection provided for consumers to the extent set out in Article 3855 of the Civil Code and Article 7aa of the Polish Act of 30 May 2014 on consumer rights (the "Consumer Rights Act"). To that extent:
- you are not bound by provisions of these Terms that would be unfair to you within the meaning of Articles 3851 to 3853 of the Civil Code, in particular the exclusions and limits of liability in sections 24 and 25 and the choice of court in section 31, to the extent they would be unfair;
- you may withdraw from the distance agreement without giving a reason within 14 days of its conclusion by sending a statement to [email protected]. If you expressly asked for a paid plan to start before that period ended, you pay for what was provided until the withdrawal (Article 35 of the Consumer Rights Act). Refunds are made by Dodo Payments;
- your rights if the digital service does not conform to the agreement follow from Chapter 5b of the Consumer Rights Act and these Terms do not limit them.
5. Accounts, sign-in and technical requirements
You may create an Account if you can enter into a binding contract and provide accurate details. We may require e-mail verification and use anti-abuse checks (such as Cloudflare Turnstile). You sign in with a password, a passkey or a Google or GitHub account. When you sign in with Google or GitHub, their terms apply as well. An Account is personal: do not share it with other people, add them to your Organization as Members instead. You are responsible for all activity under your Account and for keeping your credentials secure. Notify us immediately at [email protected] of any unauthorized use of your Account.
To use the Service you need a device with Internet access, an up-to-date browser (such as Chrome, Firefox, Safari or Edge) with JavaScript and strictly necessary cookies enabled, and a working e-mail address. For a Container to work you need a domain whose DNS records you can change and a Google Tag Manager web container, and to start a tagging server also a Google Tag Manager server container config. Some features require a Cloudflare account (section 8).
6. Organizations, roles and agencies
At registration we create an Organization for you in which you are the Organization Admin. You may create further Organizations, up to 20 created by your Account (we may change that limit for an Account). Containers, their plans, invoice details, discount codes and Cloudflare connections belong to the Organization, not to the Account. Every Member can reach and configure the Organization's Containers. Only an Organization Admin may buy, change and cancel plans, switch overage and auto-upgrade on or off, change invoice details, enter discount codes, delete Containers, and invite and remove Members and change their roles.
An Organization Admin declares that they are authorized to act on behalf of the business for which they run the Organization (named in the Organization's invoice details or, without them, the business that created the Organization). That business is the Customer for the Organization's matters: it is bound by these Terms and is responsible for the actions of the Members and for the fees for the Organization's Containers.
A Member may leave an Organization at any time, and an Organization Admin may remove a Member. Containers and data stay with the Organization. The last Organization Admin cannot leave until they give the admin role to another Member. An Organization cannot be deleted in the dashboard. Section 28 describes how it is closed.
Agencies. You may run Containers for your clients: in your own Organization (then you are the Customer towards us and you pay for those Containers) or in your client's Organization, to which you have been added (then your client is the Customer). In both cases you are responsible for your client having agreed to this, having a lawful basis and any consent required from Visitors, and having concluded with you the processing agreement the GDPR requires. You may charge for your work and pass on the cost of the Service. This is the only exception to the resale ban in section 18: without our written consent you may not resell access to the Service under your own brand or share an Account with third parties.
7. The Service
SGTM.space provides hosting and management of server-side Google Tag Manager containers. Each Container's tagging server runs on Google Cloud Run, in the region you choose from those offered. Traffic to a Container passes through a Cloudflare Worker we operate, which among other things counts Requests, applies limits and runs the Add-ons. A Container can start without a tagging server ("web only"): it then serves the Custom domain, DNS and Better Loader at the edge, and we start the tagging server once you paste a Google Tag Manager container config.
Add-ons are optional features, such as loading Google's scripts from your own domain, extending cookie lifetimes, bot filtering, disguising requests, enriching requests with location and device data, or a preview mode. We list the current Add-ons, their descriptions and the plans that include them in the Service and on the pricing page. You switch Add-ons on and configure them yourself.
The Service also includes the website audit (a Container's Audit tab and the read of your site when a Container is created, also in a real browser), the public scanner (section 9), the Academy with learning materials, and support chat and tickets. We may add, change, deprecate or discontinue features. Reducing the features of a running paid plan to your disadvantage is governed by section 15. The Service relies on third-party platforms (including Google, Cloudflare, Dodo Payments and CookieTip) and is provided subject to their terms to the extent they concern your use. With your optional consent we measure use of SGTM.space through first-party web and direct server-to-server events as described in the Privacy Policy and Cookie Notice.
8. Cloudflare connection, Same Origin Transport and Live debug
We make the features in this section available gradually. The provisions about a feature apply where it is available to your Organization or Container.
Cloudflare connection. An Organization may connect its Cloudflare accounts to the Service over OAuth. An authorized person from the Organization approves the connection on Cloudflare's consent screen, which shows the permissions requested (such as reading zones and DNS, writing DNS records, Workers and their routes, and Google tag gateway settings). The connection belongs to the Organization. You authorize us to make changes in your Cloudflare account only within those permissions and only after a preview and your confirmation in the Service. We record every change in a change log, and we only remove what we created. Some settings apply to a whole zone (for example, Google tag gateway covers every site in the zone), which we show before you confirm. You can disconnect at any time in the Service or in Cloudflare. Changes already made then stay in your account. You are responsible for your Cloudflare account, its plan and its other settings.
Same Origin Transport. This Add-on works through a Worker in your Cloudflare account, on a path of your website. You deploy it yourself following the instructions in the Service or, through the Cloudflare connection, we deploy it after you confirm a preview. The Worker runs in your account and under your Cloudflare plan: Cloudflare's limits (such as the daily request limit of the Workers Free plan) and fees are yours, and once a limit is reached traffic on that path may not reach the Container.
Live debug. A Live debug session shows in the dashboard, for 15 to 60 minutes, what one tester's browser sends to the Container, what the page puts in its dataLayer and which web and server tags fired. Before you start a session you will inform the testers that, during it, their requests to the website's tagging servers, Google and Meta are shown in the dashboard with their headers and payloads, and you will confirm that in the form. We record that confirmation. You start a session only on a page of the Container's website. We process the session's data on your behalf under the DPA.
9. Public scanner
The public scanner at https://sgtm.space/nl/audit checks any publicly available website without an Account. By starting a scan you accept this section and sections 18, 24 and 25 as far as the scanner is concerned. Scan websites lawfully, do not circumvent the scan limits (the number of scans an hour and a day per visitor or Account and the scanner's daily limit) or its protections (such as Cloudflare Turnstile), and do not use the scanner to overload websites. The scanner reads a page as any visitor could see it, also in a real browser: it does not sign in or submit forms. Results are automated and indicative. They may be incomplete or wrong, and a named provider or a score is the output of heuristics, not our opinion of that provider's services. A report is open to anyone who has its address, and we delete it after 30 days. Do not present a report in a misleading way.
10. Plans, fees and billing
A plan covers one Container: each paid Container has its own plan, billing period and payment. We list the current plans, prices, limits and Add-ons on the pricing page and in the Service. The terms shown at purchase apply to you. Paid plans are currently billed monthly. The plan fee is charged in advance for the billing period, and overage in arrears (section 14). Paid plans renew automatically for successive periods until cancelled.
Plans are sold by Dodo Payments as merchant of record: it takes the payments, charges taxes and issues the invoices, and its terms apply to the payment as well. Prices are in US dollars (USD), net of taxes. Where Dodo Payments lets you pay in your local currency, Dodo Payments sets the exchange rate and the conversion fee (usually 2 to 4%) is borne by the Customer.
Changing plans. A move to a higher plan applies at once: Dodo Payments charges the difference for the higher plan straight away, and a new billing period with the higher plan's full monthly allowance starts on the day of the change. A move to a lower plan applies from the next billing period, and the current plan stays until then. You can cancel a scheduled change. A plan that does not include an Add-on you have on switches that Add-on off and keeps its settings.
Payment portal. Through the Dodo Payments portal, reached from a Container's plan page, you can change your payment method and address, download invoices, cancel a plan and, where Dodo Payments offers it, pause a plan. A Container whose plan is paused is blocked until the plan resumes. While a payment is overdue we do not serve overage and we may suspend the Service (section 28).
11. Taxes and VAT
Unless stated otherwise, prices are exclusive of taxes. Indirect taxes (such as VAT) are charged by Dodo Payments as merchant of record based on the Organization's billing details. You are responsible for entering a correct business name, address and tax identification number in the Organization's billing settings, and for any taxes for which you are liable. For EU business customers, the reverse-charge mechanism may apply where relevant.
12. Free plan
The Organization created at registration may have one active Container on the Free plan. Organizations created later have no Free plan slot unless we grant one. Any further Container that would run on the Free plan is inactive: we do not start it, and if it already has infrastructure, that stays blocked until you buy a paid plan for it or free up the slot. The Free plan has a monthly Request limit and a limited set of Add-ons. Its daily limit is for information only and does not block traffic. The Free plan costs nothing and needs no card. You may not create several Accounts or Organizations to get around the Free plan limit.
13. Requests and limits
A Request is every HTTP request from your website that our Cloudflare Worker answers for a Container's hosts: tracking events and loads of the Better Loader scripts, also while the Container has no tagging server yet. We do not count requests that do not come from your domain or requests turned away by bot filtering. Bot requests that are only flagged and reach the tagging server are counted.
Each plan has a monthly Request limit per Container, counted over the billing period. Once the limit is passed, or with overage on once the maximum overage is passed, the Worker answers HTTP 429 to every request for the Container, the Better Loader script included, which can stop Google Tag Manager from loading on your site. The block lasts until the next billing period, a plan change or an auto-upgrade. The counters in the dashboard come from our measurement and update with a short delay. Overage is billed on that basis. We may restrict or pause traffic that threatens the stability of the Platform, abuses the Free plan or breaches these Terms.
14. Overage and auto-upgrade
Overage. A Container on a paid plan with usage billing can keep serving Requests after its monthly limit. Each Request above the limit is charged at the plan's rate, up to the plan's maximum overage (some plans have no maximum). We list the rates and maximum overage on the pricing page and on the Container's plan page. Overage switches on by itself with the first payment for a Container that has never had a paid plan. An Organization Admin can switch it off, and on again, at any time on the Container's plan page. Neither a renewal nor a new purchase switches it back on. Switching it off applies at once: a Container past its limit is blocked or, with auto-upgrade on, moved to a higher plan. We serve overage only while the plan's payment is confirmed.
Billed in arrears. We count overage from our measurement of Requests and report it to Dodo Payments during the period. Dodo Payments charges it after the end of the billing period in which it arose, usually together with the payment for the next period, also when the plan has been cancelled.
Auto-upgrade. Auto-upgrade works only if an Organization Admin switches it on. When a Container reaches the point at which it would be blocked (the plan limit or, with overage on, the limit plus the maximum overage), we move it to the next higher paid plan, at most once per billing period. As with a manual move to a higher plan, Dodo Payments charges the difference straight away and a new billing period starts on the day of the change. If there is no higher plan, the Container is blocked.
15. Changes to plans, prices and features
We may change the offer for new purchases at any time. We announce a change to a running paid plan to your disadvantage (its price, overage rate or maximum overage, monthly Request limit, or the Add-ons included) by an in-app banner and by e-mail at least 14 days before it takes effect. A price change applies from the first billing period that starts after that date. Until then you may change or cancel the plan. We may move your plan to its new equivalent at Dodo Payments: at once on the same or better terms, and under this section on less favourable ones. Changes in your favour and changes required by law may take effect at once. We announce changes to the Free plan with the same notice.
16. Promotions and discount codes
We show percentage promotions on the pricing page and the plan page. Unless stated otherwise, they cover the first billing period only, and later payments are at the list price. A general promotion applies once per Container: a Container that has already had a paid plan does not get it again. A plan change ends a discount covering several periods and does not carry it over to the new plan. Personal codes are given to selected Customers. An Organization Admin enters them in the billing settings, and on the plans they cover they take precedence over a general promotion. A personal code works once per Container and may have an overall redemption limit. It may not be published or sold. Discounts do not add up, have no cash value, and no other codes can be entered at checkout. We may end a promotion for new purchases at any time.
17. Cancellation, refunds and Container deletion
An Organization Admin can cancel a plan on the Container's plan page or in the Dodo Payments portal. Cancelling stops renewal, and the plan runs until the end of the paid period. The Container then moves to the Free plan if the Organization has a free slot for it, and otherwise becomes inactive and blocked. Its infrastructure stays, and Add-ons the Free plan does not include are switched off with their settings kept. We delete a Container only at your request: when cancelling in the app, an Organization Admin can schedule the Container's deletion for the end of the period, or delete a Container that has no active paid plan. Cancelling in the Dodo Payments portal does not schedule a deletion. Deletion is irreversible and covers the tagging server and the records and hostnames we created.
Except where required by law (including section 4) or in the case of a billing error by us, fees already paid, including for an unused part of a period and for overage, are non-refundable. The Free plan is not eligible for refunds. Refunds, where due, are made by Dodo Payments. A chargeback without contacting us first may result in suspension of your Account.
18. Acceptable use
You must use the Service lawfully. In particular, you agree not to:
- provide unlawful content;
- process Visitor data without a valid legal basis and any consent required under applicable law;
- breach the Google Tag Manager / Google API terms, Cloudflare's terms or other applicable third-party terms;
- upload or transmit malware, or use the Service, the scanner included, for denial-of-service, intrusion, scraping abuse or fraud;
- attempt to gain unauthorized access to the Service, other Customers or underlying infrastructure;
- circumvent Request limits, scanner limits, security controls or usage restrictions, including by creating several Accounts or Organizations for that purpose;
- use Add-ons to evade consent obligations or unlawfully track individuals;
- resell or provide the Service to third parties without our written consent, except as described in section 6.
19. Your responsibilities as data controller
For personal data of your Visitors that flows through your Containers, and of the testers in Live debug sessions, you are the data controller and we act as your processor. You are responsible for publishing your own privacy and cookie notices, establishing a lawful basis, and obtaining any required consent before deploying tags or Add-ons. Where the data from your tagging server goes depends on your Google Tag Manager configuration. Our processing of that data is governed by the Data Processing Agreement.
20. Custom domains and DNS
You authorize us to create the DNS records and Cloudflare custom hostnames needed to operate your Containers and, through the Cloudflare connection where available, records in your own zone (section 8). You warrant that you own or are authorized to use each domain you connect, and you remain responsible for your DNS configuration and domain verification. We may disconnect a domain used in breach of the law or these Terms.
21. Availability, support and complaints
We use reasonable efforts to keep the Service available, but do not guarantee uninterrupted or error-free operation. We do not offer a guaranteed service level (SLA) unless we agree one in a separate agreement. We may carry out maintenance, where possible outside peak hours. We are not responsible for outages or changes in third-party services (such as Google, Cloudflare or Dodo Payments) outside our control.
Support is provided through chat and in-app tickets, the same way on every plan. Authorized Implementation Partners get priority (section 27). You can file a complaint about the Service through an in-app ticket or by e-mail to [email protected], giving your Account's e-mail address, the Container concerned and a description of the problem. We answer within 14 days of receiving the complaint.
22. Intellectual property and licences
We and our licensors own all rights in the Platform, including the dashboards, the Cloudflare Worker, loader scripts, templates and related software and trademarks. We grant you a limited, non-exclusive, non-transferable right to use the Service for the term of the agreement.
Code you install outside the Service, namely Better Loader snippets, the Same Origin Transport Worker script, Google Tag Manager templates (such as the Live debug templates) and other files downloaded from the Service, is provided under a non-exclusive, non-transferable licence, free of charge within your plan, for the term of the agreement and worldwide. The licence covers these fields of use: recording and copying it in your websites, Google Tag Manager accounts and Cloudflare accounts, loading it into device memory and running it, only in connection with the Service. You may let your subcontractors use it and, as an agency, your clients for their websites. When the agreement ends, remove this code from your websites and accounts.
You retain ownership of your Container configuration and your data and grant us the right to use them as far as needed to provide the Service. If you provide feedback, you grant us a perpetual licence to use it. Google and Cloudflare marks remain the property of their respective owners.
23. Confidentiality
Each party must keep the other party's non-public information confidential and use it only to perform under these Terms, except where disclosure is required by law. This obligation survives termination.
24. Disclaimer of warranties
To the maximum extent permitted by law, and subject to section 4, the Service is provided "as is" and "as available" without warranties of any kind, whether express or implied, including fitness for a particular purpose, accuracy, or non-interruption. Statutory warranty (rękojmia) is excluded to the extent the law allows. Results of the website audit and the scanner and the Academy materials are for information only. You are responsible for testing your tags and configurations.
25. Liability
To the maximum extent permitted by law, we exclude our liability for damage related to the use of, or inability to use, the Service, in particular for lost profits, indirect damage, loss or incompleteness of data (including analytics and conversion data), the effects of Requests being blocked, outages and changes at third-party providers, and the effects of configuration made by the Customer.
The exclusion does not cover damage caused intentionally (Article 473(2) of the Civil Code) or liability that cannot be excluded or limited under mandatory law, including towards the persons described in section 4.
If the exclusion proves ineffective to any extent, our total liability to the Customer on all grounds is limited to the fees paid for the Service (including through Dodo Payments) by the Organization the claim concerns, for all its Containers, in the 12 months before the event that caused the damage. Liability relating to the processing of Visitor personal data is governed by the DPA.
26. Indemnification
You will defend and indemnify the Operator against third-party claims arising from your unlawful or non-consented tracking, your breach of the acceptable-use rules or the Partner Programme rules, your infringement of third-party rights, or your decisions as data controller, to the extent permitted by law.
27. Partner Programme
Joining. The Partner Programme covers the affiliate programme and the Authorized Implementation Partner status. You join the affiliate programme on the Affiliate program page of the dashboard, with the join button. This section binds you from that moment. You take part as a business, in your own name and for your own account. You are not our agent or representative and may not make statements on our behalf. We run the programme on the Affonso platform. Joining takes effect at once, without approval. We may still reject or suspend your participation for abuse or a breach of this section.
Commission. For each referred Customer you receive 50% of each of their payments for plans in their first 3 months, then 30% of every later payment for as long as they pay, renewals and moves to a higher plan included. Commission is calculated on the amount actually paid, after discounts. For a Partner who joined the programme through your link you also receive 30% of their commission, without reducing theirs. Commission is forfeited, and if already paid is deducted from later payouts, when the payment is refunded or charged back.
Attribution. The cookie from your link is valid for 30 days from the click. An Account created within that time, with advertising cookies consent, is assigned to you for good: no cookie overwrites it, and only our team can correct it. If the referral was not stored at registration, it is stored at the first purchase from that browser while the cookie is still valid and consent is given, unless our team removed that Account's referral before. Payments for an Organization's Containers are credited to the Partner who referred the Organization's creator, whichever Member pays, and, if the creator has no referral, to the paying Member's Partner. At your request, for example for client Accounts set up by your agency, we may assign an Account to you by hand. We may also correct or remove a referral, for example when a Customer objects, after an error, or in case of abuse. A removal applies to future purchases, and plans bought earlier keep their attribution.
Self-referrals and banned methods. Affonso flags payments made from your own partner Account, and we may reject the commission when a purchase is made mainly to earn it. An agency's purchases for its clients from its partner Account are not abuse in themselves, and payments your clients make from their own Accounts are not self-referrals. The following are banned: spam and unsolicited commercial communication, bidding on the SGTM.space brand (misspellings included) in search ads, impersonating us or suggesting that you are us, cookie stuffing and forced clicks, and misleading statements about the Service or its prices. Label your links as affiliate links where the law requires it. For a breach we may reject or reverse commission and remove you from the programme.
Payouts and settlement. Payouts and settlement with Partners are run by Affonso (ZASolution, Fellbach, Germany) as merchant of record: monthly, via PayPal, Wise or bank transfer, once your balance reaches at least USD 50 (a lower balance carries over to the next month), and commission becomes payable 30 days after the Customer's payment. Invoices for commission are either issued on your behalf by Affonso as self-billing invoices (Article 106d of the Polish VAT Act of 11 March 2004), under the agreement you give Affonso in the partner portal, or uploaded by you to Affonso. By joining you undertake to choose one of these ways and to give Affonso the data needed for payouts and tax reporting (such as W-8 or W-9 forms). You are responsible for the taxes and contributions on your commission.
Partner portal. The partner.sgtm.space portal and the partner dashboard in the Service are run by Affonso under its own terms, https://affonso.io/terms, and privacy policy, https://affonso.io/privacy.
Authorized Implementation Partner. We grant this status on an application sent to [email protected] or through an in-app ticket, after our review. It requires membership of the affiliate programme, your own Account with a running Container, and at least 10 active Containers on paid plans on Accounts created through your link. A Partner with this status gets a personal discount code (section 16), priority support and referrals of Customers who want the implementation done for them. You agree the scope, price and invoice for an implementation directly with the client. We are not a party to that agreement and are not liable for its performance. We may withdraw the status, with 14 days' notice, when the requirements are no longer met or the quality of implementations gives cause for concern.
Changes and ending. We may change the programme's rates and rules with 14 days' notice by e-mail. A change applies to commission on payments made after it takes effect. You may leave the programme at any time by writing to [email protected]. We may end the programme or your participation with 14 days' notice, or with immediate effect for a breach of this section. Commission due before the end, other than commission from a breach, is paid out under this section.
28. Suspension, termination and account closure
We may suspend or restrict the Service for non-payment, a breach of these Terms, abuse, legal risk or security reasons, telling you when we can. For a serious or repeated breach we may terminate the agreement with immediate effect. For other important reasons, such as discontinuing the Service, we may terminate the agreement with 30 days' notice.
Account closure. You may terminate the agreement at any time by asking for your Account to be closed, by e-mail from the Account's address to [email protected]. We close the Account within 30 days. Cancel your paid plans first, or ask us to cancel them. If you are the last Organization Admin of an Organization with other Members, first give the admin role to another Member or ask for the whole Organization to be closed. On closure we delete the Account with its sign-in data and, when an Organization is closed, also its Containers with their infrastructure and configuration and its Cloudflare connections. We keep billing records and invoices for 5 years, as tax law requires, proof of document acceptance for 3 years after the Account is closed, and support conversations for 3 years after they are closed. Log data expires as set out in the Privacy Policy. Affonso keeps a Partner's data at Affonso under its own rules.
Export. At your request before closure we provide an export of the Account's and Organization's data (such as the Account details and the list of Containers and their settings) in a commonly used electronic format. Your Google Tag Manager configuration stays in your Google account. When the agreement ends, the Containers stop working, and you should remove the code described in section 22 from your websites and accounts.
29. Changes to these Terms
We may change these Terms for important reasons: changes in the law, changes in the scope or way of providing the Service, new or withdrawn features, changes of providers, security, preventing abuse, or price changes (within section 15). We announce a material change by an in-app banner and by e-mail to the Account's address. For existing Customers a change binds 14 days after the notice, and for new Customers from publication. Changes required by law or solely in your favour may take effect at once. Continuing to use the Service after the date a change takes effect means you accept it, with no separate confirmation needed. If you do not accept a change, you may cancel your plans and ask for your Account to be closed before that date (section 28), and until the agreement ends the previous version applies to you. The current version and its effective date are shown at the top of this page.
30. Force majeure
We are not liable for failure or delay caused by events beyond our reasonable control, including outages of providers such as Cloudflare, Google or Dodo Payments, network failures, or acts of authorities.
31. Governing law and disputes
These Terms and the agreement are governed by Polish law. The parties will first try to resolve disputes amicably. Disputes that cannot be resolved will be submitted to the court competent for the Operator's registered seat in Łódź, Poland, subject to section 4.
32. Miscellaneous
We may transfer our rights and obligations under the agreement in connection with a reorganization, merger or sale of the business. You may not do so without our consent. If any provision is held invalid or unenforceable, the remainder stays in effect. Not exercising a right does not waive it. Notices to you may be sent to your Account's e-mail address and shown in the app. Legal notices to us should be sent to [email protected].
33. Contact
Questions about these Terms can be sent to BEO Technology sp. z o.o. at [email protected], Prezydenta Gabriela Narutowicza 40 / 1, 90-135 Łódź, Poland.