Organization Verification Terms

SpaltX lets an account claim that it belongs to an organization in one of five sectors, and reviews that claim. These terms govern the claim, the review, and what an approval means afterwards. They apply from the moment you open a request at Verification or on any sector portal.

They are part of the Terms of Service. What we do with the documents you send is in the Privacy Policy, and knowingly submitting a false claim breaches the Acceptable Use Policy.

A verification is a decision on a request: who decided it, on what date, and for what reason.

• An account holds one verification at a time. A request in one sector replaces an outstanding request in another.
• Every request carries a code. The prefix names the sector, and quoting one to support identifies your request. A code authorizes nothing, so treat it as a reference rather than a secret.
• It attaches to the account, not to a person. Whoever signs in to a verified account is treated as that organization. Section 9 is about keeping that true.
• It is not permanent. A verification can be revoked, and Section 10 covers when.

Some sectors sit on a domain that is issued against an eligibility check, so holding a mailbox on one is itself evidence. Where no such domain exists, a person reads the request instead.

The mailbox track. We send a one-time link to the address you gave. Open it within 24 hours and the request is approved with no human in the loop. The link is a capability: anyone who reaches that mailbox can settle the request, so use an address only the right people can read.

The documentation track. Send evidence that ties you to the organization and a person there. A staff member reads it and decides. This is the only track for a sector with no reserved domain, and it is open to everyone else too.

Give an address at the organization itself. A personal address gives us nothing to check against, whichever track you are on.

By opening a request you represent all of the following:

• The organization named is real, and you are acting for it with the authority to make this claim.
• The mailbox you gave belongs to that organization and you are entitled to read it.
• Every document you attach is genuine, unaltered, and yours to send us. Do not send classified or otherwise controlled material, and redact what a reviewer does not need.
• Nothing in the request is a personnel record, a patient record, or anything else about a person who is not part of the claim.

• Documents are read by staff handling the verification queue and by nobody else. They are not shared with sales, and they are not shared outside SpaltX.
• A decision records a reason. That reason is visible to you and to staff, and it is what an appeal is argued against.
• Retention follows the schedule in the Privacy Policy. Ask us to delete a document you should not have sent and we will, unless a live decision rests on it.
• Access, export and deletion under Account, Privacy cover verification records like everything else.

A mailbox request settles the moment the link is opened. A documentation request is normally decided within 5 business days, and we write to the account either way.

A denial is about the evidence rather than about you, and resubmitting with a better document is the ordinary next step. Write to support@spaltx.com with the request code if you think a decision was wrong.

Today, an approved verification does one thing:

• The account can mark the aircraft it registers with its sector, so a hangar entry says what kind of operator holds it.

Verification does not create a procurement relationship or a reseller agreement, and it does not change what you are allowed to fly. It also gives no discount by right, no priority in a queue by right, and no claim on stock.

A badge on an account says we checked a mailbox or read a document. It says nothing about any of the following, and neither we nor you should present it as if it did.

A verification is a statement about the present. Tell us at support@spaltx.com when any of it stops being true:

• You leave the organization, or your authority to act for it ends.
• The organization is dissolved, merged, renamed, or absorbed into another.
• The mailbox that settled the request is closed or reassigned.
• Anyone who should not have it gains access to the account.

Where an account passes between people, the safer move is a new account with its own request rather than handing over a login. Both are your call, and the responsibility for what a verified account does is the organization’s either way.

We revoke a verification where:

• The claim turns out to be false, or the evidence behind it was altered.
• The link between the account and the organization has ended.
• The organization asks us to.
• The account has been used in a way that breaches the Acceptable Use Policy and the verification is part of the harm.

A revocation is written to the account with a reason. The sector marking on existing aircraft is withdrawn, and the account keeps its orders, its hangar and its data.

A revoked account cannot come back through the mailbox track. That track approves with nobody in the loop, so it would undo the decision within minutes. You can still ask again, through documentation, where a person reads it.

We may change which sectors exist, which domains prove themselves, and what an approval opens. A change that narrows what a live verification does is written to affected accounts before it takes effect.