Terms of Service

1. These terms, and who they apply to

These terms cover your use of Pirca, sealed cloud cells, one for each client of a software agency, where a coding model we run works on that client's code for the agency's engineers. They are a contract between Pirca sp. z o.o., of ul. Legnicka 48/6, 54-202 Wrocław, Poland (“Pirca”, “we”) and the company that signs up (“Customer”, “you”).

The service is for businesses only, not consumers. By signing up you confirm that you are acting for your business and that you have the authority to commit your company.

The person who accepts these terms accepts them for the company, not for themselves. If you don’t have that authority, please don’t go ahead.

If documents disagree. This order applies: (1) a signed order form or agreement between us, (2) the data processing agreement, (3) these terms, (4) our Privacy Policy, (5) anything else on our website.

2. What the service is

Pirca gives your agency one sealed cell for each client you choose, on cloud infrastructure in N. Virginia. A cell holds that client's repositories, reached through a GitHub App your client creates in its own GitHub organization; the test-mode keys you supply; the client's application running in Docker Compose with seed data the model writes; and a log. In the cell, the Pirca model, a coding model we fine-tune and serve on the cell's own GPU, starts the application and then does the tickets an engineer of the cell assigns: it runs the client's tests before and after its change and a browser check, and a second model grades whether the change does what the ticket asks. The model never pushes or merges. When an engineer of the cell says yes, the cell opens a pull request in your client's repository that names the model and the engineer, with the test results, screenshots and a link to the log. The log records every input the model reads and every output it writes, cannot be edited, and can be opened by the client's reviewers you invite. Each month the model drafts, from each cell's log, a disclosure of the AI used on that client's work, for your head of delivery to complete, sign and send. Nothing in a cell can reach another cell, and nothing from a cell trains any model outside that cell.

3. What the service is not

These limits are deliberate, and they are part of what you are buying. They are not defects.

Not a choice of agents. Each cell runs the Pirca model and no other. Claude Code, Codex, Cursor and models on your own keys cannot run in a cell, and a ticket beyond our model goes back to your engineer with a note.

Not an agent that ships on its own. The model never pushes to a branch of your client's repository, merges, answers a review comment or fixes a failing check by itself. Every pull request waits for an engineer of the cell to say yes.

Not a copy of production. We do not copy your client's staging or production data into a cell, and a bug that appears only with real records cannot be reproduced there.

Not a view of anything outside the cell. A cell sees nothing on your engineers' laptops or in your other tools. The log and the disclosure cover what ran in the cell, not AI used on the client's work anywhere else.

Not other code hosts. Cells connect to repositories on GitHub only.

4. What you need to do, and why it matters

What you get from the service depends a lot on things only you control. Please read this section carefully, because sections 9 and 10 build on it.

Connect each client through the client. Ask each client's GitHub administrator to create the cell's GitHub App in the client's own organization from the manifest we send, and to pick the repositories it may reach. Until that is done, the cell cannot start, and the client can revoke the App there at any time.

Name each cell's engineers. Add to a cell only the engineers who work for that client, each with their own account, and remove them the day they leave that client's work. The yes that sends a pull request to your client is theirs.

Check the start-up once, and the fence. Read each cell's start-up report, supply the test-mode keys it asks for, never a production key, and confirm or change the areas the model must not touch.

Keep other AI off the client's code. The log and the disclosure cover the cell. Keeping undisclosed tools, laptops and personal keys away from the client's code everywhere else is your rule to set and to enforce.

Review before the yes, and send the disclosure yourself. An engineer's yes is a review: the change, its tests and its log are yours to read before your client sees them. The monthly disclosure is a draft until your head of delivery completes and signs it, and we never send it to your client.

5. Getting started, and what is free

Your first cell runs free for 30 days from the day its GitHub App is installed, with the same model, log and disclosure draft as a paid cell. No card is asked for.

If you do not go on, the cell closes at the end of the 30 days, its log is exported to you and to the client's reviewers, and the cell is deleted within 30 days after that.

6. Fees

Per cell. Each open cell costs $900 a month, whatever the number of engineers, reviewers, tickets or hours the model works. A cell runs up to three tickets at a time, and more wait in its queue. Cells are billed monthly in advance; a cell opened during a month is billed from its first day, pro rata.

What is not charged. Starting a cell, accounts for engineers and reviewers, the log with its storage and exports, the monthly disclosure draft, closing a cell and handing over its log, and your first cell's 30 days. A cell the model cannot start is not billed until it runs.

Currency and tax. Prices are in US dollars. A software house in Poland is invoiced in US dollars or, if it asks, in złoty at the National Bank of Poland's average rate for the last working day before the invoice, plus 23% VAT. A business registered for VAT elsewhere in the EU gets an invoice in US dollars with no VAT on it, and declares the tax in its own country under the reverse charge. Outside the EU, no Polish VAT is added.

Closing a cell, and price changes. Close a cell at any time; it is billed to the end of the month in which it closes and never after. A price change is announced in writing 60 days ahead and applies from the following month.

7. Delivery, availability and support

A cell's first days. A cell starts once the client's GitHub App is installed. We aim to send the start-up report within two working days, naming what runs, which tests already fail on the untouched code and what the model could not work out.

Tickets. The model starts a ticket when an engineer of the cell assigns it, at any hour. It stops after its second failed test run, when a change touches a fenced area, or when the ticket needs something outside the cell, and hands the ticket back with a note.

Our access to a cell. Pirca's staff cannot open a cell's contents in normal running. On the agency's written request, naming a cell, a reason and a time limit, our security team may open it for that time; every action is written in that cell's log, where the client's reviewers can read it.

Closing, and if Pirca stops. When a cell closes, by your choice or at the end of the contract, we export its log to you and to the client's reviewers and delete the cell within 30 days. If Pirca stops trading, we give 60 days' notice first and do the same for every cell.

Support. Support is by email at [email protected]. We aim to reply within one business day. That is a target, not a guarantee.

8. The cell's log, its exports and corrections

What the log holds. Every model input and output, command, test run, screenshot, network request allowed or blocked, and person's action in the cell, with its time, its author and the version of the model that ran.

How it is kept. Entries are added, never changed. Each carries a hash of the one before it, and the latest hash is printed on every pull request the cell opens and on each month's disclosure draft, so an edited log no longer matches.

Export. The cell's engineers and the client's reviewers can export the log for a ticket, a month or the whole cell as JSON Lines with its hashes, at any time and at no charge.

Corrections. A log entry is never corrected: a wrong one stays, and a note is added after it. A disclosure draft is corrected by your head of delivery before it is signed, and a wrong count in a draft that came from us is fixed and the draft made again.

9. What we promise, and what we don’t

We promise to provide the service with reasonable skill and care, and that we have the right to provide it.

We do not promise that a change the model writes is correct, secure or complete, or that a ticket it takes will be finished. A change has passed the client's tests and a browser check in the cell and an engineer of yours has said yes to it, but tests miss things, and the pull request is yours and your client's to review. We do not promise that the disclosure satisfies any particular contract clause; it reports what the cell's log shows.

Beyond that we give no other warranty. As far as the law allows, we exclude all implied warranties, including merchantability, fitness for a particular purpose and non-infringement.

10. Liability

10.1 Neither of us limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else the law says can’t be limited.

10.2 Losses neither of us covers. Neither of us is liable for lost profit, revenue, expected savings, business, goodwill or reputation, or for any indirect or consequential loss, however it arises.

10.3 Specific exclusions. We are not liable for a change an engineer of yours approved, or for its effects once merged; for anything that happens outside a cell, including AI used on your client's code elsewhere; for a production key supplied as a test-mode key; for a disclosure your head of delivery signed and sent; or for a renewal your client declines.

10.4 Cap. Our total liability to an agency in any 12-month period is limited to the fees that agency paid us in that period. The limit does not reach harm caused with intent, since the Polish Civil Code voids any term excusing it in advance (Article 473 § 2), or anything else Polish law does not let a contract limit.

10.5 You accept that the limits in sections 9 and 10 are a fair way to share risk, given the price and your part under section 4, and that we could not offer the service at this price without them.

11. Confidentiality and data

Everything in a cell, and the fact that a client of yours has one, is confidential. We use it only to run that cell, and our staff are bound to secrecy in their contracts, as Article 28 of the GDPR also requires. Where your client's contract flows its generative AI rules down to your subcontractors, they bind us for the cell as they bind you: no AI tool but the Pirca model runs in it, and every input and output is logged.

How we handle personal data is set out in our Privacy Policy and in the data processing agreement between us, which forms part of these terms. If the DPA and these terms disagree about personal data, the DPA wins.

12. Who owns what

Your client's code, and every change the model writes for it, belong as your contract with your client says. We claim no right in them and keep no copy once the cell is deleted.

A cell's log is yours and your client's to read and export; we hold it only to keep it for you.

The Pirca model, the checker, the corpus they train on, the cell software and the disclosure template are ours, and run only as our service.

You may not use our name or logo in public, and we may not use yours, without written permission first.

13. How long this lasts, and how it ends

13.1 The contract starts when you sign up and runs until one of us ends it.

13.2 You can end it. Cancel at any time. It takes effect at the end of the current billing month, unless section 6 sets a minimum term.

13.3 We can end it. We can end it with 30 days’ notice. We can end it immediately if you seriously break these terms and don’t fix it within 14 days of being told, if you become insolvent, or if your use exposes us to legal risk.

13.4 What happens then. We stop delivering and stop billing. You keep everything already delivered to you, and your right to use it continues. We delete or return our working copies as the DPA says. Sections 9, 10, 11 and 12 continue to apply.

14. Changes to these terms

We may update these terms. A change that matters takes effect 30 days after we email you about it. If you don’t accept it, you can end the contract before then. Using the service after that date means you accept the change.

15. Contact

Pirca sp. z o.o., ul. Legnicka 48/6, 54-202 Wrocław, Poland
[email protected]

← Back