Legal

Legal documents.

One place for the documents that govern how TensorPlane handles your data and contracts: who is responsible, how personal data is processed, who our sub-processors are, and how retention works. Every document below is a working draft pending attorney review.

Draft

DRAFT — not legal advice — pending attorney review. These drafts are not execution-ready. They exist to cut attorney time, not to replace review, and must be confirmed by a qualified attorney before anyone relies on them in a signed contract.

Who is responsible

Controller and processor identity.

Blockforo s.r.o. (company ID / IČO 21654093, VAT / DIČ CZ21654093) is the controller and processor behind the TensorPlane suite. It is registered at Rybná 716/24, Staré Město, 110 00 Praha 1, Czech Republic, entered in the Commercial Register kept by the Městský soud v Praze under file C 404625/MSPH, and was incorporated on 2024-05-28. The privacy contact is [email protected].

Legal entity (controller and processor)Blockforo s.r.o.
Company ID (IČO)21654093
VAT number (DIČ)CZ21654093
Registered seatRybná 716/24, Staré Město, 110 00 Praha 1, Czech Republic
Commercial RegisterMěstský soud v Praze, file C 404625/MSPH
Incorporated2024-05-28
Privacy contact[email protected]
Published drafts

The documents, and what each is for.

Each document below is published as a draft — the honest status of the underlying source. Follow a link for the full text.

DocumentStatusSummary
PrivacyDraftWho is responsible for your data, the website's analytics and reCAPTCHA behaviour, and your GDPR rights.
Data retentionDraftWhat is destroyed at teardown and the four content-free classes kept after account deletion, with their periods.
DPADraftThe Article 28 processing terms for both deployment scopes, with sub-processors, breach notice, audit, and deletion.
Governing lawDraftThe Czech-law and Czech-courts clause meant for a future Terms of Service — which does not exist yet.
Sub-processorsDraftThe active sub-processors (OVHcloud, Stripe, GitHub, Cloudflare) by deployment model, and who is not a sub-processor.
Not published yet

What is not published yet.

There is no Terms of Service / Master Services Agreement yet. What exists today is the governing-law and jurisdiction clause intended for that future agreement — a single clause that picks the law and the court, not the agreement itself. Do not read anything on this site as an executed Terms of Service.

The Data Processing Agreement is a starting-point template. For the vendor-hosted self-serve motion — where contracts execute with no human in the loop and the platform processes customer code — it still needs attorney approval before that motion can go live. The sales-assisted, customer-operated motion uses the same template as a reviewed starting point.

If your legal or procurement team needs a point confirmed before you can proceed, contact us and we will route it to the right owner.

Questions about these documents?

These pages are the published rendering of our internal drafts and will change as attorney review completes. If your legal or procurement team needs a specific point clarified, contact us.