Terms of service · in force

The terms this site and this work are offered on.

In Polish law this document has a name: regulamin świadczenia usług drogą elektroniczną, the terms of service for services provided by electronic means. That is the last of the Polish in it. The rest is English, because the work and the correspondence are in English, and because a document nobody reads protects nobody.

uśude art. 8 · Kodeks cywilny art. 71, 384, 385 · in force from 08.09.2026

The service provider — the statutory details

Firma
WIL TRADE Spółka z ograniczoną odpowiedzialnością (WIL TRADE sp. z o.o.)
Seat and address
ul. Szosa Ełcka 13, 15-690 Białystok, Poland
Registration court
Sąd Rejonowy w Białymstoku, XII Wydział Gospodarczy Krajowego Rejestru Sądowego
KRS
0000970413
NIP
5423448874
Share capital
100 000,00 PLN

Contact: vitali@quantika.org. Kodeks spółek handlowych art. 206 § 1 covers company websites in terms — "a także informacje na stronach internetowych spółki, powinny zawierać" — and lists the firma, the seat and address, the registration court and the number in the register, the NIP and the share capital (isap.sejm.gov.pl, KSH). Prawo przedsiębiorców art. 20 ust. 3 asks for at least the firma, the NIP and the seat or address on a distance offer (isap.sejm.gov.pl, Prawo przedsiębiorców). The e-services act of 18 July 2002 (uśude) art. 5 ust. 1 requires these details "w sposób wyraźny, jednoznaczny i bezpośrednio dostępny", and art. 5 ust. 2 the electronic addresses with the name, seat and address (isap.sejm.gov.pl, uśude).

Quantika Commerce is the trading name on this site. The party to every contract is WIL TRADE sp. z o.o.

When this takes effect

Approved by the owner of WIL TRADE sp. z o.o. on 8 September 2026, and in force from that date. What is published at this address is the version in force.

If we change these terms while you are working with us, we write and tell you. Not a notice buried on the page and left for you to find: an email to the address in your engagement, and the version published at this address is the one in force from then. What we agreed with you in writing for work already under way stands on the terms it was agreed on.

Where personal data is concerned, the data processing agreement on this site prevails over this document. It comes into force with the engagement itself, the same way these terms do, and you sign nothing separately for it. Everything else — the price, the delivery, the ceiling on money, the governing law and the courts — is settled here.

Kodeks cywilny art. 221 · ustawa o prawach konsumenta — who these terms are for

Business customers only. We do not serve consumers, and that is a term, not a preference.

We contract with businesses: companies, and sole traders acting in the course of their trade. The work we sell — reducing a shop's channels, stores and campaigns to one profit-and-loss, and building software on the strength of it — is bought for a business, by a business, and we take on no other kind of customer.

We do not take on consumers as clients. A consumer, in Polish law, is a natural person doing a legal act with a business that is not directly connected with their own business or professional activity. If that is you, none of the paid work described here is offered to you, and we will decline the engagement rather than take your money and argue about it afterwards. Reading these pages and using the panel demonstration is the one free service described below, it is open to anyone who opens the page, and nothing in this section takes away a right that anyone has in respect of that free service.

The consequence is deliberate and it runs both ways, so here it is in the open. Because you are not a consumer, the consumer rules do not apply to what we agree — the fourteen-day right to withdraw from a distance contract without giving a reason, first of all, which the consumer rights act gives to consumers and not to business buyers. You do not get that right from us, and you should read every other term in this document knowing it.

One Polish rule deserves naming rather than hiding, because it touches sole traders. Where a natural person concludes a contract directly connected with their business but the contract has no professional character for them — judged in particular against the business they are registered as carrying on — the consumer provisions on withdrawal, and the Civil Code's rules on unfair terms in a standard form, are extended to them. That is why we say "acting in the course of their trade": we contract with a sole trader for work on that trader's own shop and advertising accounts, which is as directly professional as a purchase gets. If what you want falls outside your trade, say so before we agree anything, because it changes which rules apply to us both.

This is also what makes the VAT treatment further down work as described. The reverse charge there rests on your being a taxable person buying a service for your business; a consumer sale would be taxed differently and that section would be wrong. One answer, two consequences.

Sources: Kodeks cywilny art. 221, which defines the consumer as a natural person performing a legal act with an entrepreneur "niezwiązanej bezpośrednio z jej działalnością gospodarczą lub zawodową", and art. 3855 § 1, which extends art. 3851–3853 to a natural person whose contract, though connected with their business, has no professional character for them (isap.sejm.gov.pl, Kodeks cywilny). ustawa z 30.05.2014 o prawach konsumenta art. 27 ust. 1 — a consumer who concluded a distance or off-premises contract may withdraw within fourteen days without giving a reason — and art. 7aa, which extends the withdrawal chapter to the non-professional contract of a natural person in business; consolidated text Dz.U. 2024 poz. 1796 (api.sejm.gov.pl, Dz.U. 2024 poz. 1796).

Kodeks cywilny art. 71 — what the website is

These pages invite you to talk. They are not an offer we are bound by.

The prices, packages and descriptions on this site are an invitation to contract, not an offer. Nobody becomes our client by reading a page or by writing "yes" to it: a contract exists only once we have agreed a scope and a price in writing between us, and that is set out under "starting and ending a contract" below.

This is not a disclaimer we invented. Polish law reads adverts, price lists and the like as an invitation to conclude a contract unless something says otherwise, and there is no such thing in Polish law as a "public offer" that a website makes to the world.

Source: Kodeks cywilny art. 71 — an advertisement, price list or other information addressed to the public counts "nie za ofertę, lecz za zaproszenie do zawarcia umowy" (isap.sejm.gov.pl, Kodeks cywilny).

uśude art. 8 · Kodeks cywilny art. 384–385 — what this document is

It is a standard form of contract, and it binds you only if you got it before you signed.

Legally this document is a wzorzec umowy — a standard form of contract. The Civil Code names the regulamin as one expressly, and requires that an electronic one be made available in a way that lets you store it and reproduce it. This page can be saved or printed to a file from any browser, which is one way of meeting that.

We will not claim more than that. This document is in force and published on this site, and we undertake to send it as an attachment with the scope and price, before any contract is concluded, so you have it in a form you can keep. Whether that has actually been done in a given case is a question of fact in that case, not something a web page can settle in advance.

The e-services act requires us to make this document available free of charge before the contract for a service is concluded, and states the consequence if we do not: a clause you were not given does not bind you. We would rather you read it than be bound by it, which is why it is short.

The same law requires it to be written unambiguously and intelligibly. That is why this is English prose and not a wall of definitions.

Sources: Kodeks cywilny art. 384 § 1 (a wzorzec includes a "regulamin"), art. 384 § 4 (an electronic wzorzec must be made available so it can be stored and reproduced) and art. 385 § 2 (it must be "sformułowany jednoznacznie i w sposób zrozumiały") (isap.sejm.gov.pl, Kodeks cywilny); uśude art. 8 ust. 1 pkt 1 and pkt 2, and art. 8 ust. 2 (isap.sejm.gov.pl, uśude).

uśude art. 8 ust. 3 pkt 1 — the services and their scope

Two free services, and two you pay for.

Free, and provided by electronic means: the website itself. Reading these pages, and using the seller panel demonstration published on this site. The demonstration runs on synthetic data, as the home page states — it is a working example of what we build, not anybody's real figures. No account, no registration and no payment is required to use it.

Free, and agreed by email: the store check. You send us the address of your shop and we look at the public storefront only — mobile speed against the score Shopify asks of its own themes, the product page and the checkout, the app scripts and tracking the page loads. What comes back is a written note with up to three findings and a number beside each one we could count. No store access is asked for, nothing is installed, no payment is taken, and the note is yours to keep whether or not anything follows. We say two working days because that is how long it usually takes us; on a service nobody pays for it is what we aim at rather than a date we owe you, and we tell you if it will be longer.

Paid, and agreed case by case:

  • Projects — from €1,000, fixed scope and fixed price, quoted after the check. The site lists what these have been: a profit panel; landed cost with duty by batch; an accounting or warehouse integration; a server-side tracking repair; an AI solution to a named task — each from €1,000.
  • Ongoing work, only after something has been built. Watch — €450 a month: monitoring, a monthly health report, fixes under fifteen minutes. Partner — €2,800 a month: priorities agreed on Monday, what shipped reported on Friday, with no counting of hours.

What is outside the scope, in the site's own words: ad spend and platform subscriptions; photography and video; copywriting beyond product cards; theme redesign; anything on a platform other than Shopify or BigCommerce. Each of those is quoted separately, in writing, before it starts. We do not promise a result figure — we promise the analysis and the build.

Source: uśude art. 8 ust. 3 pkt 1, which requires the regulamin to state the types and scope of the services provided by electronic means (isap.sejm.gov.pl, uśude). The services and prices above are those published on this site.

uśude art. 8 ust. 3 pkt 2 — conditions, technical requirements, unlawful content

What you need to use the site, and the one thing you must not do.

Technical requirements

A device with an internet connection and a current web browser that renders HTML and CSS. The text of every page is readable with JavaScript switched off; the seller panel demonstration needs JavaScript enabled and a browser that will display a framed page, and it is served over HTTPS. To reach us you need an email address, because email is the only contact channel this site offers. No account, no registration and no software of ours is required, and the pages set no cookies and use no browser storage.

One thing follows from that, and you should have it before you use the channel rather than after. Email is not a private path and we cannot make it one: everything sent to quantika.org — headers, body and attachments alike — passes through Cloudflare Email Routing and comes to rest in a Google mailbox. So if you attach a shop export, a customer list or an advertising report, those two companies hold that data too, for as long as we hold the message. If you would rather your store and advertising data did not travel that way, grant us access to the accounts instead of emailing an export — that is the path we ask for, and on it the bulk of your data, the store and advertising records themselves, is read where it sits and never goes by mail.

That is worth having, and it is not the whole of it, so here is the rest. What we deliver — the store check, and any document we make of your own figures — goes out by email, and so does anything we return to you at the end of an engagement. Both are written on our own machine and sent from that Google mailbox, so Google holds them from the moment we send them, and from there they go into your mailbox and onward wherever your own mail goes. Cloudflare is not on the way out: its Email Routing receives our domain's mail and forwards it, gives us no mailbox and sends nothing, so it stands on the way in only. It stays the registrar and DNS operator for the domain, which is not the same as carrying what a message contains. Granting access keeps your data off the email path on the way in; it does not keep the work off it on the way out. Email is the only route we have built: there is no server of ours and no shared drive, and this site offers no other channel. We offer no standing alternative to it and none is planned — that is a decision, not a question we have left open. If that matters to you, say so before the work starts and we will agree a route with you rather than assume email; it would be arranged for that one engagement, around something you already run, because we have nothing of the kind standing. The data processing agreement on this site sets out both paths side by side, and the privacy notice sets out the email path in full.

One thing about the way out we would rather you had from us, because the domain looks busier than our arrangements are. quantika.org also carries sender records we inherited with the domain for three other mail providers — Amazon SES, Resend and Zoho. Sender records are what let a company send as a domain, so a reader who looked them up would reasonably wonder. We send from the Google mailbox and from nothing else: none of those three is used by us. That is our statement about our own arrangements, and it is what we are answerable for here. It is not a statement that those records have been taken out of the domain's DNS — they have not been, and what is published in DNS is a different fact from what we use.

The condition on you

You must not supply unlawful content. That is the wording of the act and we adopt it as written: nothing you send us — by email, in an attachment, or through any access you grant us — may be unlawful, and that includes content you have no right to pass on. You must not attempt to disrupt this site, to overload it or to reach parts of it that are not published.

If unlawful content reaches us, we stop working with it and tell you why. What the law obliges us to do on receiving a notice that content is unlawful — the notice-and-takedown regime and who it binds — has not been checked, so this document states no procedure for it and makes no promise about one. It is listed in the block below.

Source: uśude art. 8 ust. 3 pkt 2, which requires the conditions of providing the services by electronic means, including the technical requirements and the prohibition on the recipient supplying content of an unlawful character (isap.sejm.gov.pl, uśude). Who stands on each direction of the mail is our own statement about our own arrangements, made on our own responsibility and not resting on anybody else's document: we have mail addressed to the domain received and forwarded by Cloudflare Email Routing, it comes to rest in a Google mailbox, and that mailbox is what the store check and anything we return to you are sent from. Cloudflare gives us no mailbox and nothing can be sent from Email Routing, so it is not on the way out; Cloudflare's own documentation describes the product the same way, and it is a document you can open: "Route incoming emails to custom addresses, Workers, or external destinations" (developers.cloudflare.com/email-routing), with outbound sending listed there as a separate product, checked 07.09.2026. That we send from the Google mailbox and from no other provider, the inherited Amazon SES, Resend and Zoho sender records included, is a statement of the same kind and made on 08.09.2026: it is about what we use, and it is not a claim that those records are gone from the domain's DNS.

uśude art. 8 ust. 3 pkt 3 — starting and ending a contract

The free service starts when you open a page. A paid one starts when both of us have written it down.

The website

The contract for the free service is concluded when you open a page of this site and ends when you close it. There is nothing to sign up to and no account to delete afterwards.

Paid work

You write to us. We agree the scope and the price in writing, by email. The contract comes into being when both sides have confirmed that scope and price in that exchange — not when you read a price on this site, which as item "Kodeks cywilny art. 71" above explains is an invitation, not an offer. Money follows the site: half up front on projects and half on delivery; subscriptions billed monthly in advance.

Ending it

Monthly work is monthly. You cancel with a fortnight's notice and we finish the month's work before we stop. The store check is a single delivery: once the note is with you there is nothing to terminate, and if you stop there you keep it. The code, the repositories and every key are yours from the first commit — including if we part company in the middle of a project — and repositories, hosting, API keys and ad accounts are created in your organisation, with us as a collaborator rather than the owner.

If the store check does not deliver what it was sold on

The check is free, so there is no money to hand back and no refund to promise. What we owe you is the note itself, made of the four things named in the list of services above: mobile speed against the score Shopify asks of its own themes, the product page and the checkout, the app scripts and tracking, and up to three findings with a number beside each one we could count. If what arrives is missing one of those, say so and we will either supply it or tell you plainly that we cannot. Paid work is a different matter: there the scope and the price are agreed in writing before anything starts, and what we owe is what that exchange says.

Source: uśude art. 8 ust. 3 pkt 3, which requires the conditions for concluding and terminating contracts for services provided by electronic means (isap.sejm.gov.pl, uśude). The commercial terms above are those published on this site.

uśude art. 8 ust. 3 pkt 4 — complaints

How to complain, and what happens then.

Write to vitali@quantika.org with the word "complaint" in the subject line. Tell us what you ordered, what happened instead, and what you want us to do about it. There is no form, no portal and no reference number to quote; a plain email is a valid complaint and we will not reject one for its shape.

We confirm receipt at the address you wrote from, within one working day, which is the answer time this site states for all mail. In that confirmation we tell you what we intend to do and by when. If we need something from you to look into it, we ask for it once and in full rather than in instalments.

The answer we send says what we found and what we will do, or says plainly that we disagree and why. Nothing in this procedure takes away any right you have to go to court instead, and you do not have to complain to us first.

We answer a complaint on the merits within one week of receiving it. That is our own undertaking, counted from the day your complaint reaches us, or from the day you send us the last thing we asked for if we had to ask. Where the answer is that we need longer to put something right, the answer still comes within the week and says by when. We have not checked whether any statute imposes a shorter deadline on a complaint by a business customer; if one does, it applies over this term rather than being displaced by it, and that unchecked point is listed in the block below.

Source: uśude art. 8 ust. 3 pkt 4, which requires the regulamin to state the complaints procedure — the tryb postępowania reklamacyjnego (isap.sejm.gov.pl, uśude).

Prices and VAT

What the figures are, and who accounts for the VAT on them.

The figures are the ones published on this site and repeated under "the services and their scope" above: from €1,000 for a project, €450 a month for Watch and €2,800 a month for Partner. The store check is free. Project prices are quoted after the check, when the shape of the work is known. Nothing else is charged without a written quote first.

Every figure above is the price before tax. A customer in Poland pays it with Polish VAT added at the rate in force. A business customer in the United Kingdom pays it as printed, for the reason set out next. The invoice we send states the same.

We are a Polish company registered for VAT. For a service supplied to a business customer, the Polish VAT act places the supply where the customer has its seat, not where we are. For a customer whose seat is in the United Kingdom that means we do not charge Polish VAT: the supply is treated as taking place in the United Kingdom, so if you are registered for VAT there you account for the tax yourself under the reverse charge, and if you are not registered you do not — the value of what you buy from us counts towards your own registration threshold instead. For the registered customer HMRC's guidance puts the position bluntly — under the reverse charge you "must act as if you are both the supplier and the recipient".

What we need from you, and what we do not

To treat you as a business we have to satisfy ourselves that you are one, and the rule that binds us as a Polish supplier is the EU implementing regulation, not HMRC's guidance — that guidance is written for UK suppliers and is not our rule. For a customer established outside the Community we may rely on a certificate from your tax authorities; failing that, on your VAT number or a similar number your country of establishment uses to identify businesses, or on any other proof that you are a taxable person, verified to a reasonable level by normal commercial security measures.

So a UK VAT number is not something we require. The UK registration threshold is £90,000 of taxable turnover, so a smaller shop will simply not have one, and we are not going to invent a requirement the law does not impose. A Companies House registration, for instance, is proof of the same kind. We will tell you which evidence we are relying on and keep a record of it.

Sources: ustawa o podatku od towarów i usług art. 28b ust. 1 — the general rule for services supplied to a taxable person places the supply at the customer's seat (isap.sejm.gov.pl, ustawa o VAT). For the UK customer's own position under the reverse charge: HMRC, VAT Notice 741A, sections 5.1–5.2, and for a customer who is not registered there, section 5.7 — a customer in that position adds the value of the general rule services it receives from an overseas supplier to the value of its own taxable supplies when working out whether it has to register (gov.uk, Notice 741A) — its section 6.3 states the same general rule from the UK side, that a supply to a business customer is made where the customer belongs; only the evidence guidance inside that section is written for UK suppliers, and it is that part which is not the rule we work to. For the evidence we must hold: Council Implementing Regulation (EU) No 282/2011, Article 18(3) (eur-lex.europa.eu, CELEX 32011R0282). For the UK registration threshold of £90,000 (gov.uk, VAT registration).

Rome I art. 3(1) · Kodeks postępowania cywilnego art. 1104 · Kodeks cywilny art. 78 — law and forum

Polish law governs. We choose the Polish courts — and say plainly why that second choice may not yet bind you.

These terms, and every contract concluded on them, are governed by the law of Poland. That choice needs no particular form: Rome I lets the parties choose the law, and this document makes the choice expressly, which is what Rome I asks for.

On the court we choose the same way, and here we have to be straighter than a clause of this kind usually is. We submit disputes arising out of these terms or connected with them to the Polish courts, and to the court having jurisdiction over our seat in Białystok. We do not assert that this binds you. The Polish provision it rests on lets the parties agree in writing to submit disputes over property rights to the Polish courts — and writing, in the Civil Code that defines it, means a handwritten signature on the document carrying the declaration, or an electronic declaration bearing a qualified electronic signature. A plain exchange of emails, which is how the section above says a paid engagement is concluded, is neither of those. So unless and until a contract is signed in one of those forms, this clause may not bind a client outside Poland, and which court hears a dispute would be settled by the rules that apply without it. That gap is listed at the end of this document rather than written over.

Two things do not turn on that form. The same Polish provision treats a submission as made where a defendant enters into the merits of a case without raising the objection that national jurisdiction is lacking. And the choice of Polish law in the first paragraph is a different thing from a submission to a court, so nothing here unsettles it.

We are a Polish company and our customers are businesses, often outside Poland, so a choice like this has to be made by somebody: without it, which law applied and which court heard the case would be an argument before the argument. We have made it in the plainest way we can, and it applies to you as much as to us — we cannot sue you somewhere else on the strength of it either.

Two further limits on the choice of law, because a term that overstates itself is worse than none. A choice of law does not switch off provisions that a country applies whatever law governs the contract — the Regulation calls them overriding mandatory provisions, and they keep operating. And where a question is not one of contract at all, or a court elsewhere holds that it has exclusive jurisdiction over it, this clause does not change that.

Sources: Regulation (EC) No 593/2008 (Rome I), Article 3(1) — "A contract shall be governed by the law chosen by the parties" — and Article 9 on overriding mandatory provisions (eur-lex.europa.eu, CELEX 32008R0593). Kodeks postępowania cywilnego art. 1104 § 1, under which the parties to a given legal relationship may agree na piśmie — in writing — to submit disputes over property rights arising from it to the jurisdiction of the Polish courts, and art. 1104 § 2, under which such a submission may also occur by entering into the merits of the case where the defendant does not raise the plea that national jurisdiction is lacking; consolidated text Dz.U. 2026 poz. 468 (api.sejm.gov.pl, Dz.U. 2026 poz. 468). For what that writing means: Kodeks cywilny art. 78 § 1, under which written form is kept by placing a handwritten signature on the document containing the declaration of will, and art. 781 § 1 and § 2, under which electronic form is kept by a declaration in electronic form bearing a qualified electronic signature and is then equivalent to a declaration in written form (isap.sejm.gov.pl, Kodeks cywilny).

Kodeks cywilny art. 473 § 2 — what we are answerable for

Our liability is capped at €10,000 per engagement, the work and the data alike. What the law will not let us cap, we have not capped.

Our liability to you arising out of or connected with these terms and the work done under them is limited to €10,000. Two things about how that is counted, because a cap whose measure is left vague is a cap the drafter gets to read either way later. It is one cap per engagement — the project or the subscription we agreed — and it is the total for that engagement rather than a fresh €10,000 for every claim inside it; it is not, on the other hand, a single ceiling across everything we ever do for you, so a later engagement carries its own. And it covers the work and the data alike: a claim under the data processing agreement published on this site falls inside this cap, not beside it.

The figure is stated so that you can weigh it before you sign rather than discover it in a dispute. Our published engagements run from €450 a month for Watch to €2,800 a month for Partner, with projects quoted from €1,000 and no ceiling set on them in advance. Against those, €10,000 is the outer edge of what we can be made to pay in money — on a small engagement well above what you have paid us, on a large project capable of being well below it.

The cap does not cover everything, and here we will not pretend otherwise. Nothing in it limits liability that the law does not permit to be limited — Polish law makes void, for one, any stipulation that we are not answerable for damage we cause you intentionally, and a clause of ours cannot outrank a rule of that kind. We are not printing a list of exclusions here, because any list we invented would be a guess at what the law does and does not allow; the rule is the one just stated, and it applies whether or not we spell out each case.

What the cap is not is a licence. It limits the money, not the obligation: the work described in these terms is still owed, a complaint still gets the answer described above, and every undertaking in the data processing agreement on this site is still owed in full. That agreement shares this cap on money — it does not sit outside it, and it is not weakened by it. A ceiling on damages is not a discount on what we promised to do.

Source: Kodeks cywilny art. 473 § 2 — "Nieważne jest zastrzeżenie, iż dłużnik nie będzie odpowiedzialny za szkodę, którą może wyrządzić wierzycielowi umyślnie", a stipulation excluding liability for damage caused intentionally is void (isap.sejm.gov.pl, Kodeks cywilny). The cap itself is a term we set, not a figure any statute fixes.

What we have not settled — and are telling you rather than hiding

These terms are in force, and every line below is in them on purpose. Each is a question this document does not answer, and none of them is filled in with a plausible guess. You are entitled to know where the edges of what we have committed to are before you contract on it. Nothing below is a decision we could take and have not: where the answer was ours to give we have given it above rather than list it here. The terms the owner answered on 07.09.2026 and 08.09.2026 — the mail we send from, whether the prices are net of tax, whether any route but email is offered, how a change reaches a client already working with us, and which document governs personal data — are in the sections above, and what is left of any of them is stated narrowly here.

  • Whether any statute imposes its own deadline for answering a complaint by a business customer. The complaints section now commits to an acknowledgement within one working day and an answer on the merits within one week, which is our own undertaking. Whether a shorter statutory deadline applies to a business customer has not been checked; if one does, it governs.
  • Whether the choice of Polish courts binds you at all, and what it would take to make it bind. A submission to Polish jurisdiction under Kodeks postępowania cywilnego art. 1104 § 1 has to be agreed na piśmie, and writing in the sense of Kodeks cywilny art. 78 § 1 means a handwritten signature, while art. 781 § 1 requires a qualified electronic signature for the electronic equivalent. Paid engagements here are concluded by a plain exchange of emails, which is neither. So until a contract is signed in one of those forms the forum clause may not bind a client outside Poland, and the section above says exactly that rather than asserting otherwise. Which instrument would then decide the forum for a client in a given country — and there is more than one candidate, depending where the client is — is a question of law we have not settled and do not assert an answer to.
  • What we must do on a notice that content is unlawful. The condition on you above forbids supplying unlawful content, which is what the e-services act requires this document to state. What that act, or any other, then obliges us to do once such a notice reaches us has not been checked, so no procedure is promised above.
  • Whether the work gives rise to a personal data processing relationship in every case. It does whenever what we are given to work on contains personal data, and on most shops it will; whether an engagement can be run in which none of it does depends on the figures you put in front of us, and we cannot tell you in advance. Which document governs is not the open part of this: where the relationship arises, the data processing agreement on this site applies alongside these terms and prevails over them on personal data, as the block after the company details above states.