Privacy Policy
The short version
- We collect your e-mail address, the missions you choose to save, and enough usage counting to run your plan. That is close to all of it.
- No cookies. No advertising. No tracking pixels. Nothing is stored in your browser as a cookie, by us or by anyone else. We checked that in a browser rather than assuming it.
- The network that delivers the site counts visits for us. It adds a small script of its own to our pages, and asks browsers to report network errors back to it. What reaches us is aggregate: how many visits, which pages, how quickly they loaded. Section 3 says exactly what it is and why it is still there.
- We do not sell your data, and we do not train models on your missions.
- Your saved missions are readable only by you, enforced in the database, not just in the interface.
- The infrastructure that runs CMAT sits outside Jordan, so your data is stored abroad. Creating an account is your consent to that.
- We only e-mail you about CMAT itself if you asked us to, in a box at sign-up that starts empty. You can change your mind at any time, and everything else we send is about your account.
- You can see, correct, export or delete your data by e-mailing us.
This summary is written for readability and is not the policy. Where it differs from the numbered sections below, the numbered sections govern.
Who we are, and what this covers
This policy explains what Darb Al Nojoom Software Development ("we", "us"), a sole establishment owned by Firas Jarrar and registered in the Hashemite Kingdom of Jordan under commercial register no. 621874, of Housing Bank Complex, Queen Noor Street, Shmeisani, Amman, Jordan, does with personal data when you use the CubeSat Mission Analysis Tool ("CMAT"). We are the controller of that data.
It covers the CMAT web application, the analysis API behind it, and the account system. It forms part of, and should be read with, our Terms of Service.
Our processing is governed by Jordan's Personal Data Protection Law No. 24 of 2023. Section 12 sets out the additional position for users in the European Economic Area and the United Kingdom.
What we collect
2.1 Your account
- E-mail address: your identifier, and how we send sign-in links, password resets and notices about your account or these policies.
- Password: stored only as a cryptographic hash by our authentication provider. We never see, store or transmit your password in a readable form, and we cannot recover it for you.
- Account metadata: an internal user identifier, when the account was created, when you last signed in, and whether your e-mail has been confirmed.
2.2 Your plan and usage counters
To run the trial and enforce the fair-use limit, we store against your account: which plan you are on, when your trial ends, how many analyses you have run today, and which day that count belongs to. This is a count, not a record: we do not keep a log of which analyses you ran or what was in them.
2.3 Missions you save
If you use Save Mission to Cloud, we store the name you give it, the mission inputs as structured data, the application version that saved it, and the times it was created and last changed. Missions live under your account and nothing else.
2.4 Analyses you run
When you run an analysis, your mission parameters are sent to our analysis API together with your access token, computed, and returned to your browser. The parameters and the results are not written to our database unless you save the mission yourself.
2.5 Technical logs
The platforms that host CMAT keep ordinary server logs covering IP address, timestamp, requested path, response status and browser user-agent, which we use to keep the Service running and to detect abuse. Our own application code does not write your inputs or results to those logs.
2.6 Things you send us
Help → Send Feedback composes a message in your own e-mail client; nothing is transmitted until you press send there. If you do send it, we receive your e-mail address, your message, and the version and build you were running. Support e-mail reaches us the same way.
2.7 Payments
When paid plans go live, checkout and billing will be handled by a specialist payment provider. We will not receive or store your full card details. We expect to hold only what is needed to know that a subscription exists: a customer reference, the plan, and the billing status. Invoicing details you give us for an institutional purchase order are held as business records.
2.8 What you agreed to, and when
When you create an account you tick a box confirming you have read these documents. We record the time you did so and which published versions were on screen, so that both of us can tell later what was actually agreed. The time is taken from our own systems, not from your computer.
The same screen offers a second, separate box asking whether we may e-mail you about CMAT. It starts empty, ticking it is entirely optional, and refusing has no effect on your account or your plan. We record your answer and when it last changed. If you never tick it, what we hold is a record that you did not, which is what lets us be sure we are not writing to you.
What we do not do
Stated plainly, because for an engineering tool these are the questions that actually matter:
- CMAT sets no cookies of its own, and there is no cookie banner because there is nothing to consent to. Checked in a browser on 22 August 2026: this domain sets no cookies at all, ours or anybody else's. Your sign-in session is held in your browser's local storage, not in a cookie sent to us.
- No tracking pixels, no session recording, and nothing that follows you to other sites. We do not build a profile of you, and we do not try to recognise you from one visit to the next.
- Traffic measurement by the network that delivers the site. CMAT is served to you through a content delivery network, and that network adds a small script of its own to our pages which counts page views and measures how quickly they load. It also asks your browser to report network errors back to it. We did not write it and it is not part of the application: it belongs to the delivery network, and that provider switched it on rather than us. We have chosen to keep it, because it is the only measure we have of whether anyone is using CMAT at all. What reaches us is aggregate. It is not advertising, it is not sold, and it does not tell us who you are or what you did in the tool.
- No advertising, and no advertising networks.
- We do not sell, rent or trade personal data, and we do not share it for anyone else's marketing.
- We do not use your mission data to train machine-learning models, our own or anyone else's.
- We do not read your saved missions. Access is restricted at the database to the account that owns the row.
- We do not e-mail you about the product unless you asked us to. The box at sign-up starts empty, and we do not treat creating an account, buying a plan or writing to support as permission. Without that tick, everything we send you is about your account, your plan, security, or a change to these policies. You can withdraw the permission at any time, by the unsubscribe link in any such message or by writing to us, and we act on it either way.
- We do not buy, rent or scrape e-mail addresses, and we do not add you to a list because you appear in a public directory or on a paper.
Why we process it, and on what basis
| What | Why | Basis |
|---|---|---|
| E-mail, password hash, account metadata | To create your account, sign you in, and reach you about it | Performance of our contract with you |
| Plan, trial end, daily counters | To give you the trial, apply your plan, and enforce the fair-use limit | Performance of our contract; our legitimate interest in keeping the Service affordable |
| Saved missions | To store and return work you explicitly asked us to keep | Performance of our contract, at your request |
| Analysis requests | To compute the result you asked for | Performance of our contract |
| Server logs | Security, abuse detection, diagnosing faults | Our legitimate interest in a secure, working Service |
| Feedback and support messages | To answer you and fix what you reported | Your consent in sending it; our legitimate interest in improving CMAT |
| Storage on infrastructure outside Jordan | To operate the Service at all | Your consent, given when you create an account (see section 8) |
| Billing records | To take payment and keep lawful accounts | Performance of our contract; legal obligation |
| Your acceptance of these documents, with its time and version | To know, and to be able to show, what you were asked and what you agreed to | Our legal obligation, and our legitimate interest in a record that protects us both |
| Whether you want product e-mail, and when you last said so | To send you CMAT news if you asked for it, and to be certain we do not if you did not | Your consent, given by ticking the box; and our legal obligation to keep a record of it |
Where we rely on your consent, you may withdraw it at any time; see section 11. Withdrawing consent to storage outside Jordan means we can no longer operate an account for you, so we would treat it as a request to close the account.
Held in your browser only
Some things are stored on your own machine and never transmitted to us. You can clear them at any time through your browser's site-data controls, and doing so signs you out and discards local presets.
| Stored as | What it holds |
|---|---|
cmat-theme | Which of the three colour themes you chose |
cmat_mission_presets_v1 | Presets you saved locally, as distinct from cloud missions |
cmat_session_v1 | Your last set of inputs, so a reload does not lose your work |
cmat_vp_vis_v1 | Which live preview panels you had open |
| Authentication session | The signed token that keeps you logged in, written by the authentication library |
Two features move data at your own initiative and are worth knowing about: Copy Shareable Link encodes the current inputs into a URL, so anyone you give that link to can see those inputs; and Export Presets writes a file to your computer, which is then yours to look after.
Your browser fetches everything CMAT needs — the charting, 3D and orbit-propagation libraries, the typefaces, and the globe imagery — from this site itself. No other company learns that you asked for them, and there is no longer any exception to that. The measurement script described in section 3 is a separate matter: it belongs to the network that delivers this site and is added by that provider, not requested by the application.
Your mission data
Mission inputs and results are yours. Our Terms of Service say so as a matter of ownership; this policy says what we do with them in practice, which is: store them if you asked us to, compute with them when you press Run, and nothing else.
We may generate aggregated, de-identified statistics about how the Service is used (run counts, error rates, which features are exercised) to operate and improve CMAT. These never identify you and never contain your mission parameters or results.
Mission data may contain information about your organisation's spacecraft that you consider sensitive commercially or otherwise. We hold it in confidence, but you should apply your own judgement about what belongs on a hosted service; the export functions exist so that you can keep your own copies and so that nothing has to live here that you would rather keep in-house.
Who else sees it
Your data is not shared with anyone except:
- The providers who run our infrastructure: hosting for the application, the content delivery network that serves the pages and measures traffic, computation for the analysis API, and the managed database and authentication service that hold accounts and saved missions. They process data on our instructions, as sub-processors, and are not permitted to use it for their own purposes.
- The payment provider, once paid plans are live, for checkout, subscriptions and invoicing.
- Professional advisers, meaning accountants and lawyers, where they need it and are bound by confidentiality.
- Authorities, where we are required by law to disclose. We will tell you unless we are prohibited from doing so.
- A successor, if the business operating CMAT is merged, reorganised or acquired, under equivalent protections and with notice to you.
We describe our providers by the role they perform rather than listing them by name, so that this document does not need reissuing whenever a supplier changes. The current list is available on request at the address in section 16, and we will provide it.
Transfer and storage outside Jordan
The infrastructure that runs CMAT is operated outside the Hashemite Kingdom of Jordan. Your account data and any missions you save are therefore stored and processed abroad.
Under Jordan's Personal Data Protection Law, transferring personal data outside the Kingdom requires the data subject's consent and that the destination affords protection no lower than Jordanian law requires. By creating an account and using CMAT you consent to that transfer, and we select providers whose security and data-protection commitments we consider to meet that standard.
The traffic measurement described in section 3 is performed by that same delivery network, outside the Kingdom, on the same basis.
If you would prefer your data not to leave Jordan, we cannot offer you an account, because the Service has no in-Kingdom deployment today.
Security
- Everything travels over encrypted connections (HTTPS/TLS); data at rest is encrypted by our infrastructure providers.
- Passwords are held only as hashes, by the authentication service, and are never visible to us.
- Saved missions are protected by row-level security in the database: the rule that you can read only your own rows is enforced by the data store itself, so a fault in the interface cannot expose someone else's missions.
- The analysis API independently verifies your signed access token on every request; it does not take the browser's word for who you are or what you are entitled to.
- Access to production systems is limited to those who need it.
No service can promise perfect security, and we do not. What we can say is that the design keeps the amount of personal data in the system deliberately small, so there is little here to lose.
How long we keep it
| What | Kept for |
|---|---|
| Account and profile | As long as your account exists |
| Consent record: acceptance, and your product-e-mail choice | As long as your account exists. A withdrawal is kept as a record of the withdrawal, which is the only way we can prove we stopped |
| Saved missions | Until you delete them, or 30 days after the account closes |
| Server logs | A short operational period set by our infrastructure providers |
| Feedback and support e-mail | While useful for support, then deleted |
| Billing and tax records | As long as accounting and tax law requires |
After an account closes we keep your data available for export for 30 days, then delete it in the ordinary course. Copies inside routine backups expire on their own cycle rather than being individually erased.
Your rights
Under Jordanian law you may ask us to:
- Tell you what personal data of yours we hold, and give you access to it;
- Correct or update anything inaccurate or incomplete;
- Delete your data, and close your account;
- Stop processing you consider unnecessary, or object to it;
- Withdraw consent you previously gave;
- Stop product e-mail at any time, which is a specific case of the above and needs no reason;
- Receive a copy of your data in a portable form, or have it transferred.
Withdrawing permission for product e-mail is deliberately as easy as giving it. Every such message carries an unsubscribe link, and writing to the address in section 16 has the same effect. Either route changes the record we hold against your account, so the two cannot disagree. It takes effect immediately and it changes nothing else: your account, your plan and your saved missions are untouched.
Much of this you can do yourself: saved missions can be deleted in the application, and the export functions give you a portable copy of your work at any time. For anything else, write to the address in section 16. We will respond within 30 days, and we will not charge you for a reasonable request. We may need to confirm your identity before acting, which for an e-mail-based account normally means answering from the registered address.
If you are not satisfied with how we have handled a request, you may complain to the competent Jordanian data protection authority.
If you are in the EEA or the United Kingdom
CMAT is offered to researchers and engineers internationally, and we apply the rights in section 11 to everyone regardless of where they are. If the EU or UK General Data Protection Regulation applies to our processing of your data, you additionally have the right to lodge a complaint with your local supervisory authority, and the rights in section 11 map onto the GDPR rights of access, rectification, erasure, restriction, objection and portability.
Our lawful bases are those set out in section 4. Where data is transferred outside the EEA or the UK, we rely on your consent and on the contractual protections we have with our providers.
We have not appointed an EU or UK representative. If you believe our processing requires one, tell us; we would rather hear it than not.
If something goes wrong
If personal data we hold is exposed, altered or lost through a security breach, we will investigate immediately and notify those affected and the regulator within the deadlines Jordanian law sets, currently 24 hours to notify affected individuals and 72 hours to notify the regulatory unit, from the point we become aware. We will tell you what happened, what data was involved, and what you should do.
Children
CMAT is a professional engineering tool and is not directed at children. Accounts require you to be 18 or over, as our Terms of Service set out. We do not knowingly collect data from anyone under that age; if we learn that we have, we will delete the account and its data.
Changes to this policy
The version in force is always the one published at this address, with its version number and effective date at the top. If we make a change that materially affects how we handle your personal data, we will give you at least 30 days' notice by e-mail or a prominent notice in the application before it takes effect. Corrections and clarifications take effect on publication.
Version 1.5, 27 September 2026. Names the controller. Where this policy previously carried a placeholder, it now identifies the controller as Darb Al Nojoom Software Development, a sole establishment registered in Jordan under commercial register no. 621874 and owned by Firas Jarrar, and gives its registered address in Shmeisani, Amman. Section 16 carries the same details. Nothing about what we collect, why, how long we keep it, who it is shared with, or what you can ask us to do with it has changed. The controller has not changed; this version names it on the page instead of leaving a blank. A clarification, effective on publication.
Version 1.4, 4 September 2026. Describes two things the sign-up screen now records: your acceptance of these documents, with the time and the versions you were shown, and a separate optional answer to whether we may e-mail you about CMAT. Section 2.8 sets out both, section 4 gives the basis for each, section 10 says how long they are kept and section 11 says how to withdraw. Section 3 previously said that no marketing e-mail is sent at all; that is replaced by the narrower and now permanent statement that none is sent unless you asked for it. Nothing changes for any account that already exists. Nobody has been added to anything, the box starts empty, and the new permission can only come into being by somebody ticking it after this version is published, at which point this is the version they were shown. On that basis it is not a change to how we handle data we already hold, and no notice period is owed for it. What is new is a purpose we did not have before, and it is described here before it is used rather than afterwards.
Version 1.3, 22 August 2026. Corrects section 5 again, in the same direction and for the same reason: the last exception it named has gone. The globe’s relief and cloud imagery were the final files this site asked your browser to fetch from a third party, and they are now served from here like everything else. Section 5 no longer carries an exception because there is not one. A correction, effective on publication.
Version 1.2, 22 August 2026. Corrects section 5. The previous wording said your browser fetches the charting, 3D and orbit-propagation libraries from public content delivery networks. That had stopped being true: those libraries were moved onto this site earlier the same day, and the typefaces followed, which also ended the requests that were being made to a font provider on every page of this site — including this one. The sentence now describes the single third-party fetch that remains, which happens on the mission tool page only. Again nothing about how we handle your personal data has changed, and this time the change reduced what leaves your browser rather than merely describing it better. A correction, effective on publication.
Version 1.1, 22 August 2026. Corrects the short version and section 3. Version 1.0 said that no third-party analytics ran on CMAT. That was not accurate. The delivery network described in section 3 had been adding its measurement script to our pages, switched on at that provider's end rather than ours, and we had not noticed until we looked. Nothing about how we handle your personal data has changed; what changed is that this document now describes it correctly. Under this section that makes it a correction rather than a material change, so it takes effect on publication.
Contact
For anything in this policy, whether access requests, deletions, the current list of our providers, or a question you would just like answered:
Darb Al Nojoom Software Development
Commercial register no. 621874, Jordan
Housing Bank Complex, Queen Noor Street, Shmeisani, Amman, Jordan
E-mail: contact@cubesatmission.com