Who you are dealing with.

Data controller: InOrbit d.o.o., Benčani 15A, Saršoni, 51216 Viškovo, Croatia, OIB 38846238650, MBS 081116183 (Commercial Court in Rijeka). Privacy requests: legal@inorbit.hr.

This site sets no tracking cookie and loads nothing from a third party on its own. The one exception you choose: 'Book a call' opens Calendly, our scheduling service, and only when you click it does Calendly load, set its own cookies and receive what you enter to book. Visits are counted only if you allow it; the Analytics section below says exactly what that means. It sits behind Cloudflare, which is how a request reaches it. Every request is written to an access log, as web servers do: the time, the path, the status, the sizes, how long it took, your network address and your browser's user-agent string, with a request id. Those logs are kept for 30 days and then deleted, and nothing in them is joined to anything else about you.

The site reads in English or Croatian. The first time, it asks which country the request came from (Cloudflare tells the server) and looks at your browser's language, and keeps neither. What your browser keeps for this site: the language you pick with the switch, and the theme and its colour, if you change them, which site you chose at the first-visit screen (Nevio's or the company's), and the currency you pick on the pricing page, each as one cookie for inorbit.hr so that the sign-in, the console and the docs follow the same choice, the language and the theme with a copy in local storage; that you closed the notice bar; and on the metronome its practice log, which that page says. All of it is functional and first-party, nobody reads it but the page, and clearing the site's data in your browser removes it.

You can sign in with a Google or GitHub account. That is optional: the public pages need it for nothing. Signing in creates an account on this platform's identity service with the email address and the name the provider gives, and sets session cookies for inorbit.hr while you are signed in; signing out ends the session. An account is what the InOrbit platform runs on: the console, API keys, monitors, connections to your tools, Trails uploads, the phone app and billing, and it lets a playground keep your work under it. To have it deleted, write to the address below, or use Your data in the console.

What a platform account holds, and why: your name, email address and user id; the API keys and tokens you create (the secrets are never shown again); the monitors you set up and the connections to your tools, whose credentials are stored sealed; the audit lines that say who did what and how it ended, never the content of a call; and, if you pay, your billing identity with Stripe. Stripe hosts the payment page, so your card details go to Stripe and not to us; we send it your account id and email address and keep the plan and the invoices. All of it is there to provide the account you asked for.

The InOrbit phone app signs in to the same account. It sends our API your sign-in token, and, so that a page can reach you, registers the phone to /v1/paging/devices: the push token Apple gives it, the app's version and build, the system (iOS or iPadOS) and its major version, whether it is a phone or a tablet, the language, and whether notifications are allowed. Never a model, a serial number, an advertising id, an address or a location. The text of a page (severity, the monitor's name, the incident's short id), with the incident's and the account's ids so the app can open it, passes through Apple's push service to reach the phone. The app has no tracking and no analytics or advertising SDK; the App Store privacy label (name, email address, user id, device id and other user content, all linked to you, none for tracking) says the same. Settings has a Privacy policy link to this section.

If you email us, we keep your message and our reply for as long as the conversation is useful, and we pass them on only to the service providers that run our email. To have them deleted, write to legal@inorbit.hr.

A playground may need to process what you type into it to answer you. Where one does, it says so on its own page, and the rule is the same: nothing is kept that does not have to be. The terms cover what you can expect from them.

On the Radar you can run the example programs, signed in or not. Pressing Run sends that program to this platform's own sandbox, where it is compiled and run once, with no network, and what it printed comes back to you. The program is not kept. So that everyone gets a fair share, runs are counted per visitor for the day: by your account when you are signed in, otherwise by a salted hash of your network address. The run's audit record carries that account id or hash, the language, the size of the program, how it ended and how long it took, never the program or its output, and it is kept with the other logs for 30 days. The request itself is in the access log above, like any other.

In the EVM lab's playground you can submit a Solidity contract to an assignment, signed in. Pressing Run sends the contract to the same sandbox with the assignment's hidden tests, where it is compiled and run once, with no network. Unlike a Radar run, the contract and its report are kept under your account, so the playground can show your progress; they stay until you erase them, which one button on the playground does, at once and for good. The audit record of a run names your account, the assignment, the sizes and the outcome, never the contract. Asking a public network a question from the playground goes through this platform to that network's public endpoint; the record names your account, the network, the method and the status, not the parameters or the answer, and the calls are counted per account for the day.

The site guide, the chat in the corner of every page, is an AI: a model this platform runs itself, on its own machine, that answers from what this site says and can be wrong. Your question, the earlier turns of the chat and the path of the page you are on go to that model; nothing is sent to anyone else. The question and the answer are not stored. What is recorded is who asked, which model answered, the number of tokens and how it ended, so each visitor has a fair daily share. When you are signed in, that is your account, and the record goes when your account is erased. Otherwise it is a salted hash of your network address that changes every day and cannot be turned back into the address, or tied to you once the day is over. Without a sign-in the guide knows only the public site. The chat itself is kept only in your browser.

The legal basis. The account, the app and what they hold are processed to provide what you asked for (GDPR Article 6(1)(b)). The access logs and the audit records of sandbox runs are processed for our legitimate interest in running the site safely, stopping abuse and giving each visitor a fair share (Article 6(1)(f)); the logs join to nothing else about you, and you may object by writing to us. Analytics rest on your consent, as said above.

International transfers. Some of what is described here reaches suppliers outside the EU: Cloudflare, which ends the connection to this site at its edge, so a request may be handled outside the EU; Calendly in the United States, only when you click 'Book a call'; Google or GitHub when you sign in with them; Stripe for billing; and Apple for push notifications and the app's distribution. We have not yet reviewed and recorded the data processing terms each of them offers, nor confirmed which transfer safeguard each relies on (the EU standard contractual clauses or the EU-US Data Privacy Framework); until that is done we do not name one here. Ask us at the address below and we will tell you where each stands.

How long. Account data is kept while the account exists, and is erased across every service when you delete it: after a seven-day grace period in which you can still keep it. Audit lines about a team are kept while the team exists. Trails recordings are kept 90 days. Access logs and sandbox audit records are kept 30 days. Backups age out after 14 days. Your name and email are yours to correct, and Your data in the console gives you a copy of what is kept.

What is measured, if you allow it: the page you open and the one you came from, your browser, operating system and device type, your screen size, your language, and your country as Cloudflare reports it. Your network address is used for a moment to tell one visit from another and is never stored; the identifier made from it changes every month. No cookie is set, and nothing is linked to your name or your account.

Who processes it: we do, with Umami, open-source software running on our own server in Croatia. No one else receives the data, and nothing is sold or shared. It is kept for 13 months and then deleted automatically.

Why: to see which pages are read and which are not, so the site gets better. The legal basis is your consent (GDPR Article 6(1)(a)). You can withdraw it here at any time, as easily as you gave it; withdrawing stops the measurement at once and does not affect what was counted before.

Your rights: access, erasure, restriction and objection, as the GDPR gives them; write to legal@inorbit.hr. Visit counts carry no name, so we can find yours only if you tell us enough to recognise the visits. You may also complain to the Croatian data protection authority, AZOP (azop.hr).

The extension records your own session only on sites you allow, one at a time: the pages you visit (the path and the names of query parameters, never their values), what you click by the name the site gave it, how far you scroll, page timings and script errors with their text scrubbed. It never records what you type, keystrokes, the clipboard, file contents, cookies, the page's storage, request or response contents, page text, screenshots or the page itself, and nothing on a site you did not allow or while recording is paused.

Recordings stay in your browser. Nothing is sent to us until you sign in to InOrbit and press Upload; you can open a recording first, see every event exactly as it would be sent, and remove any of them. Sign-in tokens are kept in the browser's extension storage, never shown, logged or given to a page.

What you upload goes to your own InOrbit account, to provide the service you asked for (GDPR Article 6(1)(b)). We check every event again and drop anything outside these rules, keep no recording contents in logs, send none to any AI model provider, and sell or share nothing. An uploaded recording is deleted after 90 days, earlier when you delete it in the console, and with your account.

Your rights are the same as above: write to legal@inorbit.hr. The browser stores (Chrome Web Store, Edge Add-ons, Firefox add-ons) that distribute the extension receive only what they receive for any extension you install from them, under their own terms.