OrbitStudio ← Back to site

Privacy Policy

Last updated: 29 October 2026 · Agreement version 2026-10-29c

This policy explains what personal data OrbitStudio collects, why we collect it, how long we keep it, and what rights you have under the GDPR. We keep this short and specific, because vague privacy policies help nobody.

01 Who is responsible for your data

The controller of your personal data is SimplySolid3D, a sole proprietorship (eenmanszaak) registered in the Netherlands, which runs OrbitStudio.

We are not required to appoint a Data Protection Officer, so you can reach us directly at the contact address above for any privacy question.

02 What we collect and why

DataWhyLegal basis
Email address, password (stored only as a salted hash — we never see your password), validation code, account tier and credit balance To create and secure your account, let you sign in, and give you the access you bought Performance of our contract with you
Your generations: selected coordinates, model settings, any text you engrave, the resulting model files, and a small preview image of the finished model To produce your models, let you download them, show them in your library, and support you if something fails Performance of our contract with you
Models you build on OrbitStudio Atlas: the country, province or continent you chose, the settings you built it with (such as puzzle or solid, size, relief height, plate and colour bands), the files we build from them (the download, its 3D preview and its fit report) and a small preview image of the finished model To build your model, let you download it, keep it in your library, and support you if a build fails Performance of our contract with you
A model code in the files. Model files you download carry a random model code and the text “Made with OrbitStudio” (in an STL’s header and in a 3MF’s description), together with a title: the model’s world and the coordinates of its centre, or the name you gave it, and for a star chart its place and date. A star chart’s files carry the code once the chart is saved to your library. The code is linked to your account in our records only So we can trace copies that are shared or resold against our terms (section 8 of the terms: nobody may share or resell the digital files) Our legitimate interest in enforcing our terms. Weighed against you: the code is random and taken from the model’s own record, not from anything about you; the file carries no name, email address or account number; and only we can look a code up
A shared page, only if you choose to share a model. Pressing Share publishes a page at orbitstudio3d.com/m/ followed by a random code, showing a picture your browser makes of the model on screen, the model’s world, place, shape, size and settings, and the name you type to be shown with it, if you type one (anonymous otherwise). Anyone with the link can see the page, and search engines may find it; we do not list it anywhere on our site. The page never shows your email address, your account or the text on your model’s frame or lid, and the model files are never shared To show the model you chose to share to the people you send the link to, and to let you stop sharing it at any time Your consent, given by pressing Share for that model. You withdraw it with Stop sharing (in the app or in My Models), which takes the page and its picture down
Star charts you save or unlock on OrbitStudio Sky. A chart is built in your browser; apart from a place search (below), nothing about it reaches us unless you save it or, signed in, press one of its 3MF buttons. Saving it to your library stores the place name and coordinates, the date, time and time zone, every piece of text you chose to engrave, the plate, font and display settings, the model files and a small preview image. A 3MF button sends the chart's settings to our server, which checks whether your account has already unlocked that chart. Unlocking it keeps a record that your account unlocked that chart: a fingerprint of the chart, not its settings To keep the charts you save, and so that downloading a chart you have already unlocked never costs you a second credit Performance of our contract with you
A generation made without an account: the same coordinates, settings, engraved text and model files as above, together with the random identifier your browser makes up for itself (orbit_guest) and your IP address To let you see that the generator works before you decide whether to back the campaign or create an account, to hand back the model you just asked for, and to keep automated traffic from running up the cost of producing them Our legitimate interest in letting you try the product before you pay for it, and in not paying for abuse. Weighed against you: the identifier is a random number that says nothing about who you are, we never join it to anything else, and it disappears together with the model after 48 hours. Create an account inside that window and the model moves onto it, after which the row about your generations applies instead
A preview on OrbitStudio Atlas, with or without an account: the country, province or continent and the settings you chose, your IP address, and either the random identifier described in section 3 (orbit_guest) or, if you are signed in, your account To draw the preview you asked for, and to limit how often one visitor can ask, so that previews stay available to everyone Our legitimate interest in letting you see a model before you build it, and in not paying for abuse. Weighed against you: the identifier is a random number that says nothing about who you are; it or your account is used only to count your previews, and is held in memory for the minute that count covers; and apart from our request logs (section 6) we keep no record of a preview
A place search on OrbitStudio Sky: the text you type into the search box, your IP address, and either the random identifier described in section 3 (orbit_guest) or, if you are signed in, your account To turn a place name into coordinates for your chart, and to limit how often one visitor can search, so that place search stays available to everyone and within OpenStreetMap's usage policy Our legitimate interest in offering place search and keeping it working. Weighed against you: the box asks only for a place; our server forwards the text to OpenStreetMap without your IP address or any identifier of yours (section 4); the identifier or account is used only to count your searches, and is held in memory for the minute that count covers; and apart from our request logs (section 6) we keep no record of your searches
If you use the OrbitStudio connector in an AI assistant or another MCP client, such as Claude by Anthropic or ChatGPT by OpenAI: what the assistant asks our server on your behalf, which is only the text of that one request, such as a place name, a world, coordinates, or a place, date and time for a star map (a place on Earth given by name rather than coordinates is looked up with OpenStreetMap, section 4), and the IP address the request comes from. When the assistant calls us from its provider's servers, as Claude and ChatGPT do, that address is the provider's and not yours; when an app on your own device or a page in your browser calls us directly, it is yours To answer that request, and to limit how many requests one address can make in a minute, so the connector stays available to everyone Our legitimate interest in offering the connector and keeping it working. Weighed against you: the connector needs no account, has no login and sets no cookies, so we do not know who you are; it receives only the request, never the rest of your conversation (section 4); we do not store what it asked, except that the answer to a place name looked up for a star map stays in our server's memory for up to a day, under the name alone (section 4); the address is held in memory only for the minute that count covers; and apart from our request logs (section 6), which record that a request was made but not what it asked, we keep no record of it
If you buy a Plus or Merchant plan: which plan, monthly or yearly, its status (running, cancelled, past due or ended), when it started and when its current period ends, whether it renews, when we sent a renewal reminder, and Stripe's reference numbers for you as a customer, for the subscription, for the checkout and for the payment. Your card or other payment details are never part of it: they stay with Stripe To give your account the rights of the plan for as long as it runs, to let you cancel or withdraw from it and refund you when the terms say so, and to send you the purchase confirmation and the yearly renewal reminder (terms section 05A) Performance of our contract with you
If you buy one model or one star chart's 3MF on its own: which model, or a fingerprint of the chart (the same one a spent credit records), when you paid, the amount and currency, and Stripe's reference number for the checkout. Your card or other payment details are never part of it: they stay with Stripe To unlock that model or chart for you, to refund you when the terms say so, and to send you the purchase confirmation (terms section 05B) Performance of our contract with you
The record of what you agreed to when you bought a plan or a model: the version of the terms and the moment you ticked the box asking for access to start now To be able to show which terms applied to your purchase and that you asked for access to begin at once, which is what ends the right of withdrawal once you use the plan or download the model (terms section 07). The version travels with the checkout, so Stripe keeps it with the purchase, and we repeat both in the confirmation email we send you Performance of our contract with you, and our legal obligation to confirm that consent to you
On the Lifetime Commercial tier, or a running Merchant plan: your license number, when it was issued, and the shop name and shop links you choose to add to your certificate To let anyone check that a shop selling prints made with OrbitStudio holds the commercial license. The page at orbitstudio3d.com/license shows the number's status and, while the license is valid, the shop name and links you added — never your email address. Adding a shop name or links is optional Performance of our contract with you (the commercial license in section 08 of the terms)
Whether you asked to hear from us, when you asked, and which wording you agreed to To email you occasionally about OrbitStudio — new places to print, new features. Only if you ticked the optional box; it is never part of accepting the terms, and an account works exactly the same without it Your consent, which you can withdraw at any time from your account bar or the link in any such email. Withdrawing does not affect emails we must send about your account, such as a password reset or notice that these terms are changing
Technical data: IP address, browser type, timestamps, request and error logs To keep the service secure and available — rate limiting, abuse and fraud prevention, and debugging Our legitimate interest in a secure, working service
Where your first visit came from: the name of the site that linked to us (for example reddit.com, never the address of the page or post itself), the page you first opened, the label on a link we posted ourselves (such as utm_source=discord) and the date, kept in your browser as described in section 3 To learn which places bring people to OrbitStudio, so that we know where to share it. It is stored with your account when you create one, with a model you generate without an account, and with a star map you download Our legitimate interest in knowing which of our efforts work. Weighed against you: it is four facts about one visit, not about you; it says nothing about who you are or what else you do online, follows you nowhere, is never shared or used for advertising, and you can clear it from your browser at any time
Messages you send us — by email, or through the report form in the app: what you write, the address you give us if you choose to give one, and the technical details of what you were doing at the time (the model you were working on, the settings you had chosen, the error the service returned, and your browser type). Through the request form on our business page: your name, your email address, your organisation if you give it, what your request is about, the rough volume you choose, what you write, and your browser type. That form's request reaches us only as an email and is not stored on our website To answer your question, fix the fault you report, and weigh up your suggestion; for a business request, to reply and to prepare an offer if you ask for one Our legitimate interest in helping our users and in a service that works; for a business request, also taking the steps you ask for before a possible contract
When one of our own scripts fails in your browser while you use the generator, OrbitStudio Sky, your library or the homepage, your browser sends us the error by itself: the error's text, where in our code it happened, the page it happened on (without anything after ? in its address) and your browser type. Nothing that identifies you: not your account, not the orbit_guest identifier, not anything you typed into a form To notice and fix faults on our pages, including the ones nobody writes in about Our legitimate interest in a service that works. Weighed against you: it is a description of our own code failing, kept for a short time, not tied to you and never shared
When our download wall stops you, and what you do next. When our server itself refuses a download you have no credit or plan for, or a star chart's 3MF you cannot pay for, or opens a payment page for you, it notes that step with your account: which step, when, the model or star chart it was for (its world and kind), your tier and the plan you chose. A step only your browser sees — the account wall a visitor without an account meets, or a click on the links to our plans or our campaign — is sent with nothing that identifies you: not your account, not the orbit_guest identifier To count how many people our prices stop, and whether a different offer would serve them better. Used only for counts: never to email you, to show you a different price, or to decide anything about you Our legitimate interest in prices that work for the people who use OrbitStudio. Weighed against you: it is a few facts about a moment you met our own payment wall, kept for a short time, never shared, and deleted with your account
If you back our campaign on MakerWorld: your MakerWorld username, your pledge number, the reward you chose and the date, as MakerWorld shows them to us as the campaign's creator; the code we send you; and when we sent it. Nothing else — MakerWorld shows us no email address and no payment details To send you your code by MakerWorld message, keep track of who has had theirs, and replace a lost code or withdraw the code of a pledge that was cancelled Performance of our contract with you (delivering the pass you backed)

We do not sell your data, we do not share it for advertising, and we do not use it to build profiles or make automated decisions with legal effects for you.

03 Cookies and local storage

OrbitStudio sets no cookies of its own, runs no advertising pixels and does no cross-site tracking. That is why you do not see a cookie banner — there is nothing to consent to.

We use only strictly functional browser storage:

  • a login token stored in your browser's local storage, so you stay signed in;
  • a few interface preferences (such as your last map position and settings), stored locally so the app opens where you left off;
  • if you use OrbitStudio without an account, a random identifier (orbit_guest) that your browser makes up for itself, shared by the tools on this site. Unlike the two above this one is sent to our server, with the requests you make while signed out: generating, previewing and fetching a Moon or Mars model, sending a report through the form in the app, sending a request through the form on our business page, signing in or creating an account from the generator, searching for a place on OrbitStudio Sky, and asking for a preview on OrbitStudio Atlas. It ties those requests to this browser — it is what connects the model you just made to the browser that asked for it and, if you then sign in or create an account, what lets that model move onto it — and it lets our rate limits count per visitor instead of lumping everyone together. It says nothing about who you are and we never join it to anything else.
  • a note of where your first visit came from (orbit_first_touch), written once, the first time you open a page here, and never changed afterwards: the name of the site that linked to us (never the address of the page or post), the page you arrived on, the label on a link we posted ourselves (such as utm_source=discord) and the date. It is sent to our server only when you create an account, generate a model without an account, or download a star map, so that we can count which places bring people here (section 2). It says nothing about who you are and follows you nowhere else.

Apart from that guest identifier and the note of your first visit, these never leave your browser except to authenticate you with our own server, and you can clear them all at any time through your browser settings. Signing out removes the login token.

Cloudflare, which sits in front of this site, sets one cookie of its own (cf_clearance) to tell real visitors apart from automated abuse. It is required for the site to work and carries no advertising or tracking function.

Signing in with Google

You can sign in with a Google account instead of a password, on the Moon and Mars generator and on OrbitStudio Sky alike. Google's code is deliberately kept behind your own choice: nothing is loaded from Google, and Google sets no cookies, until you press the “Continue with Google” button. Press it and Google's sign-in script loads, Google sets its own cookies and learns that you are signing in here, on their terms rather than ours. We receive only your email address and Google's internal account identifier — enough to recognise you next time, and nothing else. Never press the button and Google is not involved at all; the email-and-password route stays available and always will.

Using your location

OrbitStudio Sky's “Use my location” button asks your browser for your position through its own built-in location feature. The permission prompt you see is your browser's or your device's, not ours, and we never learn that you were asked or how you answered. If you allow it, the page rounds the position to four decimal places (about 11 metres) and fills in the latitude and longitude fields exactly as if you had typed them. Pressing the button sends nothing to us; how your browser or device works out the position is between you and them. We deliberately do not turn the position into a place name for you, because that would mean sending your coordinates to OpenStreetMap, so the place-name field is left for you to fill in.

From then on the coordinates are part of your chart, like typed ones: they stay in your browser unless you save the chart to your library or, signed in, press one of its 3MF buttons (section 2). The chart's settings are also written into the part of the page address after the “#”, so that Copy link can hand the chart to someone; browsers do not send that part of an address to any server.

How we count visits

We do want to know roughly how many people visit and which pages they read, so we use Cloudflare Web Analytics. It was chosen because of what it does not do: it sets no cookie, it does not fingerprint your device, it does not follow you to other websites, and it builds no profile of you. It records a page view — the page, the referring site, and a country and device type derived from your request — and nothing that identifies you. There is therefore still nothing to ask your consent for.

04 Who processes data on our behalf

We are a small operation and rely on a few well-established providers. They act as our processors, may only use the data to deliver their service to us, and each is bound by a signed data processing agreement that sets out what they may do with it and obliges them to help us meet our duties to you. One row is deliberately not like the others: MakerWorld is not our processor and we have no agreement with it. It is listed because it is where you pay, and you are entitled to see that the party taking your money is not us and is bound to us by nothing. Stripe is not our processor either when you buy a plan: it sells the plan to you as merchant of record (terms section 05A) and handles the payment as a controller in its own right, under its own privacy policy.

ProviderRoleWhere
Google Cloud (Cloud Run) Runs our application and the background worker that generates models Region europe-west1 (Belgium, EU)
Supabase Pte. Ltd. Hosts our database: your account, credits and tier, your plan records, your job records, and the record of the terms you accepted Stored in AWS eu-west-1 (Ireland, EU). Supabase is a Singapore company and its US affiliate provides support, so staff outside the EEA can access it
Cloudflare (Pages, R2 storage, CDN, Web Analytics) Serves the website, stores generated model files, holds our database backups, and counts visits Global network; may process outside the EEA
MakerWorld (Bambu Lab) Not a processor for us: it is where you back the campaign and pay, under its own privacy policy. As the campaign's creator we can see your MakerWorld username and your pledge, and we copy those into our own list to send you your code (section 02); we receive no email address or payment details from it. The only link to an account here is the code, once you choose to redeem it. See MakerWorld's privacy policy
Stripe (Managed Payments, through its Link service) Not a processor for us: when you buy a Plus or Merchant plan, or one model or star chart on its own, Stripe is the seller (merchant of record). Buying takes you to Stripe's own checkout page, where you give your payment details to Stripe and never to us. We give Stripe your email address, your account number and the plan or model you chose, so the payment can be matched to your account; Stripe tells us whether the subscription or the purchase is paid, renewed, cancelled or refunded. Stripe's privacy policy applies to the payment. See Stripe's privacy policy; Stripe may process data outside the EEA
Resend, Inc. Sends account emails such as password resets and, if you buy a plan, the purchase confirmation and the reminder before a yearly renewal. If you ticked the box to hear from us, it also sends our occasional emails about OrbitStudio. It receives your email address and the email at the moment each one is sent; the list of who asked for these emails is kept in our own database, not at Resend United States (EU-US Data Privacy Framework certified)
Google (Gmail) Hosts our support mailbox, so any email you send us is stored there EU and global Google infrastructure

Our processors in turn use their own suppliers — sub-processors — and our agreements require them to hold those suppliers to the same obligations. That guarantee covers the processors above and not MakerWorld, which we have no agreement with. The one worth naming is the chain under your account data: Supabase does not own data centres, so the database itself sits on Amazon Web Services infrastructure in Ireland. Supabase publishes its full sub-processor list and must give us at least 30 days' notice before adding to it, which gives us time to object.

We may also disclose data where we are legally required to, or where it is necessary to establish, exercise or defend a legal claim.

Parties we do not control

The map of the Moon and Mars in the generator is served by NASA Solar System Treks (trek.nasa.gov), a public service of the United States government. When you pan or zoom the map, your browser requests those map tiles from NASA directly, which means NASA — and not us — receives your IP address and the area you are looking at. NASA is not our processor and we have no agreement with them; we simply cannot show you the Moon or Mars without their imagery.

There is one more third party on the page, and it is there to protect the service rather than to watch you. The app loads Cloudflare Turnstile from challenges.cloudflare.com, and so does the request form on our business page at the moment you send it, a bot check that tells a person apart from a script — without it, automated traffic could generate models endlessly at our expense. Cloudflare therefore receives that request and your IP address. It runs invisibly: there is normally nothing for you to click. Cloudflare already appears in the table above as a processor for this site, and its handling of Turnstile specifically is set out in Cloudflare's own Turnstile Privacy Policy. Turnstile sets no advertising cookie and builds no profile of you.

OrbitStudio Sky's place search works through OpenStreetMap. When you search, our server sends the text you typed to OpenStreetMap's Nominatim service (nominatim.openstreetmap.org) and passes the matching places back to you. Unlike the NASA map above, this request is made by our server, not your browser: Nominatim receives our server's address, the text you searched for, and a line identifying OrbitStudio with our contact address, as its usage policy requires — never your IP address or any identifier of yours. The search box is not checked against a list of real places, so please type only the place itself — a name, an address or coordinates — and nothing else about yourself. The words on your print have their own fields, and those never go to OpenStreetMap. Your browser may keep an answer for an hour, so looking up the same place twice does not ask again. Our server also keeps each answer in its memory for up to a day, filed under the searched text alone and with nothing about who searched, so that a place many people ask for reaches OpenStreetMap once rather than every time; it is gone when the day ends or the server restarts. Nominatim is run by the OpenStreetMap Foundation, a not-for-profit foundation based in the United Kingdom, under its own privacy policy. It is not our processor and we have no agreement with it; we cannot offer place search without it, which puts it on the same footing as NASA's imagery above.

If you add the OrbitStudio connector to an AI assistant or another MCP client, such as Claude by Anthropic or ChatGPT by OpenAI, the assistant calls our server whenever it decides one of your questions needs it, usually from its provider's own systems. The provider decides what it sends us, acts for you and not for us, and handles your conversation under its own privacy policy: Anthropic's privacy policy, OpenAI's privacy policy, or that of whichever client you use. None of them is our processor and we have no agreement with any of them. What reaches us is only the request described in section 2; the rest of your conversation does not. When the assistant asks for a star map of a place on Earth by its name instead of its coordinates, our server looks that name up with OpenStreetMap exactly as it does for OrbitStudio Sky's place search, described above: Nominatim receives the place name from our server, and never the address the request came from. What we send back is information about places and settings, pictures from our own site, and links to our own site. Those links carry a label naming the kind of app they were sent to (for example utm_source=chatgpt), so that we can count visits that came through the connector; the label names the app, never you.

Apart from NASA's map tiles and Cloudflare Turnstile, described above, and Google's sign-in script, which loads only if you press “Continue with Google” (section 3), everything on our pages, including all fonts and code libraries, is served from our own domain. The links in our data credits, to OpenStreetMap, the IAU and Creative Commons, are ordinary links: nothing is fetched from those sites unless you click one. OrbitStudio Atlas adds no one to this section: its maps are drawn from elevation and boundary data we store ourselves, so your browser fetches no map tiles or anything else from another site to show you one.

05 Transfers outside the EEA

Your data is stored in the EU: our application runs on Google Cloud in Belgium, and our database sits in Ireland. Storage location and access are two different things, though — several providers can reach that data from outside the European Economic Area:

  • Supabase, which hosts our database, is Supabase Pte. Ltd., a Singapore company. Your data itself stays in their Irish region, but the company is outside the EEA and its US affiliate provides support, so staff in Singapore and the United States can access it. This transfer is covered by the European Commission's Standard Contractual Clauses.
  • Resend is based in the United States. Even where email is dispatched from an EU region, Resend's account data and delivery logs are stored in the US. Resend is certified under the EU-US Data Privacy Framework, which provides the legal basis for this transfer.
  • Cloudflare and Google operate global networks and may process data outside the EEA. These transfers are covered by the European Commission's Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework.
  • Stripe receives your email address, your account number and the plan or model you chose when you buy one, as the seller of that plan or model and under its own privacy policy (section 4). Stripe is a global company and may process that data outside the EEA; its privacy policy says how it protects it.
  • OpenStreetMap's Nominatim service receives the text of an OrbitStudio Sky place search, or a place name the OrbitStudio connector is asked to look up for a star map, from our server, and nothing else about you (section 4). The OpenStreetMap Foundation is based in the United Kingdom and says it stores request details there and in the Netherlands. The United Kingdom is covered by an adequacy decision of the European Commission.

Only the data needed for each service is shared: Resend receives your email address and the contents of the account email being sent. When you send us a report from inside the app, or a request through the form on our business page, Resend also carries it to us, so it passes through Resend in the same way. If you asked to hear from us, Resend receives your email address and the email itself each time we send you one of those emails; it does not keep a mailing list for us (section 6).

06 How long we keep it

  • Account data — for as long as your account exists. If you delete your account, we remove it within 30 days, except where we must keep records by law.
  • Your plan records — for as long as your account exists, like the rest of your account data, and removed with it, except where we must keep records by law. You cannot delete an account while a plan still renews (terms section 05A). What Stripe keeps about the payment, it keeps under its own privacy policy.
  • Your commercial license — for as long as your account exists. Deleting your account deletes the license, its shop name and its links at once, and the number then no longer checks as valid.
  • Generated models and job data — we keep the files for a number of your most recent models so you can find and re-download them in the app: 3 on a free account, 6 on Starter Pass, 12 on Premium Pass, 25 on Lifetime Creator or a running Plus plan, and 50 on Lifetime Commercial or a running Merchant plan. You can delete any of them yourself at any time, and a model's preview image goes with it.

    A model you have downloaded is kept for as long as your account exists. A model you have not downloaded is kept for 12 months, and that period starts again each time you open it, download it, or press Keep in the app; when it runs out we remove the files. Each model shows its own date in the app.

    A star chart you save to your library on OrbitStudio Sky follows the first of those two rules from the moment you press Save, whether or not you have paid for or downloaded anything: its model files and preview image are kept for as long as your account exists, unless you delete the chart. The record that your account unlocked a star chart's 3MF files is kept for as long as your account exists too, so that downloading that chart again stays free.

    A model you build on OrbitStudio Atlas follows the same two rules as a Moon or Mars model, and counts towards the same number of models.

    Beyond those files, a small record of each generation, each Atlas model and each saved star chart (the region, country or place you picked and the settings you used, any text you engraved included) is kept while your account exists, also after you delete the model itself, because it is what enforces the fair-use limits in our terms. Download links are temporary and expire 24 hours after they are issued. The library is a convenience rather than a backup, so keep your own copies of anything you want to be sure of.
  • Shared pages — until you stop sharing, delete the model or delete your account; each of those removes the page and its picture. The page can stay in our edge cache for up to five minutes after that. Services that already showed a preview of the link (a chat app, a social network) may keep their own copy of the picture and title, which we do not control.
  • Models generated without an account — 48 hours, the files and the record of the generation together. Creating an account inside that window moves the model onto it, after which it is kept like any other.
  • Request, security and error logs — normally up to 12 months, then deleted or aggregated. The text of an OrbitStudio Sky place search is part of the address it is sent to, so it appears in these logs together with your IP address and the time of the search. We keep no other record of searches.
  • Your MakerWorld pledge record (username, pledge, the code we sent and when) — up to 24 months after we add it to our list, then deleted. A code you have redeemed stays part of your account's history like any other.
  • Our mailing list (in our own database, as part of your account) — you are on it only while you want to hear from us. If you unsubscribe, from the link in any of those emails or from your account bar, it takes effect immediately and no further such email is sent to you; if you delete your account, you leave the list with it. The record in your account of when you said yes and when you said no is kept like the rest of your account data. We also note which of these emails your account received, without the address or the email's contents; when you delete your account that note is no longer linked to you.
  • Errors your browser sends us by itself (section 2) — up to 90 days, then deleted.
  • Steps at our download wall (section 2) — up to 90 days, then deleted. Those noted with your account are deleted with it.
  • Support emails, reports sent from the app and requests sent from our business page — up to 24 months after your question is resolved. A report you send from the app is stored with it and removed on the same clock; the copy emailed to us lives in our mailbox for the same period. A request from the business page is not stored on our website at all: the email in our mailbox is the only copy, kept for the same period.
  • Backups — we back the database up so an outage or a mistake cannot wipe your account. Our own hourly snapshots are kept in our object storage for 30 days, and our database provider keeps its own daily backups for 7 days.
    This matters for deletion: when you delete your account it disappears from the live service immediately, but a copy remains inside those backups until they expire. We do not open backups to remove individual records — doing so would risk the very data the backups exist to protect — so a deleted account is fully gone once the last backup containing it has aged out. Backups are only ever used to restore the service after a failure, never to bring back an account you asked us to remove.

07 How we protect it

  • All traffic runs over HTTPS.
  • Passwords are stored only as salted hashes (PBKDF2) — they cannot be read back, not even by us.
  • Access to production systems is restricted and authenticated.
  • Rate limiting and abuse protection guard against automated attacks.
  • Download links are time-limited and tied to your account.

No system is perfectly secure. If a data breach ever occurs that is likely to present a risk to you, we will notify the Dutch Data Protection Authority and, where required, you — without undue delay.

08 Your rights

Under the GDPR you have the right to:

  • access the personal data we hold about you;
  • rectify data that is incorrect or incomplete;
  • erase your data ("right to be forgotten") — see the note on backups in section 6 for what this means in practice;
  • restrict or object to our processing, including processing based on legitimate interest;
  • data portability — receive your data in a structured, machine-readable format;
  • withdraw consent at any time, where processing is based on consent.

Email us at [email protected] and we will respond within one month. We may need to verify your identity first, so that nobody else can request your data.

You also have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens, autoriteitpersoonsgegevens.nl) or with the supervisory authority in your own country. We would appreciate the chance to fix it first.

09 Children

OrbitStudio is not directed at children under 16. If you believe a child has given us personal data without the consent of a parent or guardian, contact us and we will delete it.

10 Changes to this policy

If we change how we handle personal data, we will update this page and the date at the top. If a change is significant, we will tell you by email or in the app.

11 Contact

Any privacy question, request or concern: [email protected]. See also our Terms of Service.