Privacy Policy

Who we are, and what this covers

This policy explains what [operator: registered name] ("we", "us"), registered in the Hashemite Kingdom of Jordan at [registered address & commercial registration no.], 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.

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. Your sign-in session is held in your browser's local storage, not in a cookie sent to us.
• No analytics, no telemetry, no tracking pixels, no session recording, no fingerprinting. There is no third-party analytics code in the application.
• 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 send no marketing e-mail. Messages from us are about your account, your plan, security, or changes to these policies.

Why we process it, and on what basis

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.

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 also fetches charting, 3D and orbit-propagation libraries from public content delivery networks when the page loads. As with any resource a browser requests, that discloses your IP address to the network serving it. Those requests carry no account data.

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, 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

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

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;
• Receive a copy of your data in a portable form, or have it transferred.

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.

Contact

For anything in this policy, whether access requests, deletions, the current list of our providers, or a question you would just like answered:

[operator: registered name]
[registered address, Jordan]
E-mail: [email protected]