Nexus Aero
Follow us
Stay updated

Policy, transparency, and accountability

One clear reference for rights, boundaries, and responsibilities.

This center includes the adopted membership/privacy terms and general Nexus Aero, AeroChain and AeroPassport operating notices. Check your membership, invoice or transaction record for its exact version and acceptance status; general explanations do not amend an earlier agreement.

Version and standing of this text

public-notices-2026-10-16 · Content reviewed:

Standing: public explanation, not a contractual effective date or compliance certificate. Legal drafts are not adopted terms without appropriate review and explicit owner adoption. Updating this page does not rewrite an earlier consent or agreement.

Account and membership records · Workspace agreement and version

Membership terms and verification privacy

Persian controls; English is a translation. Shahbaz Peyvand Paya adopted this version, effective on its live release for new actions presenting it. Earlier records are not rewritten.

NEXUS_MEMBERSHIP_PRIVACY_20261018_V2

Read the complete membership terms

Operator and notices

Nexus Aero is the aviation brand operated by Shahbaz Peyvand Paya, registration 97642, Mashhad, Iran. Shahbaz Peyvand Paya is responsible for review. Membership, privacy and legal requests may be sent to `info@nexusaerosupply.com` or through an authenticated Support case. Do not send identity images, passwords, payment-card data or confidential evidence through ordinary email or public forms.

Service and responsibility

AeroChain supports inventory records, offer discovery/publication and related Workspaces. Counterparties remain responsible for their goods, services, ownership, competence, authorized technical data, acceptance, shipping and direct payment. Membership, account review, a clean scan, order status or Intelligence data is not aviation authority, installation approval, airworthiness or a maintenance release. Nexus does not hold funds for direct participant transactions. Pool stock, prices, access and benefits are not guaranteed; each use requires actual availability and its applicable agreement.

Account and access

The holder must provide accurate information, establish company representation, assign appropriate roles and report relevant changes or security incidents. Contact verification, document review, contract acceptance, payment and operational access are separate. Nexus Admin controls Trial, Active and Suspended access with a recorded decision and reason. Payment alone grants neither access nor technical authority. Technical work and independent approvals still require the appropriate qualified person and authorized scope. Corrections and challenges can be raised through Support.

Written offer, support and renewal

Each order form and invoice must identify the fee, IRR/toman denomination, applicable tax, term, users, document allowance and scope before acceptance/payment; one toman equals ten IRR. The approved eligible first-year fees are 4,500,000 toman Individual and 27,000,000 toman Company. That offer covers twelve months, one named Individual user or up to five named Company users, 1 GB private documents during the pilot and one guided onboarding session. Tax must follow the approved legal basis and be disclosed in the actual document; this text establishes no rate or exemption. Email/Support cases have no guaranteed hours or response time and are not an emergency AOG service. An optional trial of up to seven days requires an explicit Admin grant and expiry. Renewal, future discounts and credits are not automatic; renewal requires a new express decision and offer.

Changes, cancellation, refunds and fiscal records

Authenticated acceptance binds the exact order-form version/content and server-recorded time. Later amendments require their own record and applicable acceptance; earlier agreements/consents are not rewritten. Cancellation, charge disputes and refund requests are reviewed through Support against the accepted offer, delivered service and applicable legal rights. There is no universal no-refund rule or waiver of non-waivable rights. Each correction/refund needs an approved amount/reason linked to the original payment; a request or receipt image alone is not settlement. Platform invoices are commercial records. Shahbaz Peyvand Paya handles statutory invoices, corrections, tax and refund documentation through the company's existing fiscal system and links its reference to the commercial record. Actual collection/refund is recorded only from a reliable bank/provider result or independent confirmation; repeated outcomes cannot duplicate payment or access.

Disputes and mandatory rights

Domestic membership is subject to applicable Iranian law and its valid written terms. The issue and record reference should first be raised through Support to the company's responsible owner; this does not prevent access to a legally competent authority or mandatory rights. This text introduces no compulsory arbitration, invented exclusive forum, liability cap or blanket liability exemption. Nexus remains responsible for its own service, and counterparties for their transactions/technical decisions, under applicable law and valid agreements. Membership cannot waive aviation authority boundaries or non-waivable duties.

Privacy, publication and permitted use

Account data and evidence are used for service delivery/protection, verified contacts and representation, identity review, agreements/financial records, Support and applicable obligations. Public profiles, offers and selected fields require the relevant publication choice/authority; registration or identity approval does not automatically publish private evidence or stock. Marketing, publication and job-matching choices are separate. Supplying evidence grants no permission to sell it, publish it freely or train AI models on private content. The detailed notice below is available before evidence is supplied and its accepted version is bound to the action record.

Read the complete verification privacy notice

Purpose and minimum data

Identity evidence of the account administrator and, for companies, registration/representation evidence support review of the person and their authority. Records include contacts, applicant type, declared company details, supplied files, scan outcomes, review decisions and related security/consent events. Do not supply unnecessary medical or technical records.

Access and recipients

Files use private, account-scoped storage, quarantine and scanning. Access is limited to the holder and authorized reviewers according to role and need. Admin/Support access is not publication permission. Arvan hosting/network, self-hosted private storage and encrypted backups support Nexus operations. Resend handles transactional email, Farapayamak/MeliPayamak contact-verification SMS and PayPing enabled payments; these connections are not channels for identity-image attachments. Email processing may occur outside Iran. A payment reference does not mean Nexus stores payment-card details.

Retention and closure

Retention is based on the identified identity/representation need, active account, agreement/invoice, security incident, open dispute or applicable legal obligation. When the purpose ends or closure is requested, the responsible owner reviews each category, records the outcome and any deletion restriction, removes unnecessary data from active use and arranges authorized deletion/anonymization. This is a reviewed process, not a promise of immediate automatic erasure. Backups are separate from public access; closure does not immediately erase every archive, and restoration must honor recorded restrictions. A seven-day local-archive policy is not an identity-document or universal backup retention period.

Requests and correction

Access, correction, restriction, publication withdrawal and deletion-review requests use the stated email or authenticated Support. Identity and authority are checked before disclosure or access changes. Corrections preserve necessary history; withdrawing publication does not automatically cancel agreements or legal obligations. Do not resend evidence through public messages.

Separate choices and security limits

Identity review is separate from marketing, optional public-page measurement, publication and job matching. Newsletter delivery is currently disabled. A clean scan does not establish document authenticity or personal competence. No end-to-end encryption, unrestricted erasure or absolute security is promised. Adverse decisions and correction requests can be raised through Support.

Adopted document reference

SHA-256 of the retained adoption document:

cf1e7eb15d2302848540f80a8989d5fff61612251e3664f08c3b637969ecaad7

01

Privacy and data rights

Defines processing purposes, data minimization, access controls, applicant rights, and the path for data-related requests.

Public operating notice

public-notices-2026-10-16 · Public explanation

Read the notice and responsibilities

Use the minimum information needed for your enquiry, account or permitted workflow. Do not place government identifiers, passwords, medical details or confidential technical records in a public enquiry or general support message; use an approved protected channel when evidence is requested.

Identity, contact, access and activity information supports account administration, security, requested communication and authorized service delivery. Public Sourcing and business profiles use consent-controlled fields; private stock, documents and agreements remain separately restricted. AeroPassport public sharing and private job matching have separate consent and withdrawal controls. A numbered profile does not authorize disclosure of its underlying private evidence.

Request clarification, access or correction through Help and identify the affected account or record without sending its secret values. Deletion and retention requests require identity and scope checks; audit, security, contractual or applicable legal obligations may limit immediate removal. The applicable service notice or agreement must identify its retention and recipient arrangements before sensitive data is supplied.

Ask a question about this notice
02

Website use and authority boundaries

Separates public use, membership, organization authority, technical eligibility, direct transactions, and each party’s responsibility.

Contractual version requires separate acceptance

public-notices-2026-10-16 · Public explanation

Read the notice and responsibilities

Public information helps you evaluate Nexus; it is not a binding offer, inventory reservation, employment offer or guarantee of availability. Demonstrations and roadmap items are not operational commitments. Confirm current scope, eligibility and commercial terms before relying on a service.

Use an account only within your assigned authority. Keep credentials private, provide accurate information and obtain permission before submitting another person’s or organization’s material. Impersonation, fabricated evidence, unauthorized extraction, access-control bypass and malicious files are prohibited. Suspected misuse may require restricted access and review under the applicable account process.

Account creation, membership purchase, identity verification and permission to perform an operation are separate. Admin controls AeroChain Trial, Active and Suspended access; payment alone does not activate it. Job Apply in AeroPassport uses verified sign-in, not AeroChain membership. Each commercial service or transaction requires its applicable versioned agreement and authorized decisions. This notice does not introduce a liability waiver, override a signed agreement or remove rights that cannot lawfully be excluded. Changes to public descriptions do not silently amend an accepted contract.

Ask a question about this notice
03

Cookies and optional measurement

Separates essential operation from optional measurement; privacy choices remain reopenable from every public footer.

Active website control

public-notices-2026-10-16 · Public explanation

Read the notice and responsibilities

Essential storage supports functions such as authentication, security, language choice and privacy preferences. Optional measurement is distinct from these functions and is controlled through the website’s privacy choices. Refusing optional measurement does not grant or remove operational authority.

Reopen Privacy choices in the footer to review or change your selection. A change applies to subsequent optional collection; it is not a promise that previously collected information or third-party records are instantly erased. External employer, payment or other websites have their own notices and controls.

Never include contact details, personal evidence, confidential documents or operational record contents in campaign links or analytics event labels. Report a suspected disclosure through Help rather than reproducing the sensitive information in a public channel.

Ask a question about this notice
04

Accessibility and language

Commits to keyboard navigation, semantic structure, native Persian RTL, English, and continuous accessibility improvement.

Product standard under continuous review

public-notices-2026-10-16 · Public explanation

Read the notice and responsibilities

Nexus aims for clear headings, keyboard-operable controls, visible focus, readable contrast and responsive layouts in English and Persian. Persian layouts should preserve correct reading order while keeping technical references and identifiers legible. This is an improvement commitment, not a claim of independent accessibility certification.

Respect reduced-motion preferences and use available motion controls where provided. Essential information must not depend solely on animation, colour or a diagram. If a chart or interaction prevents understanding, request a textual explanation or an accessible alternative through Help.

To report a barrier, include the page address, language, device, browser and the action you could not complete. Do not include passwords or confidential account contents. Language differences or unclear technical wording should be reported before a consequential decision; the applicable controlled document remains the reference for that decision.

Ask a question about this notice
05

Operational data and document governance

Separates public data from governed provenance, version, access, disclosure, correction, retention, and audit history.

Controlled in member workspaces

public-notices-2026-10-16 · Public explanation

Read the notice and responsibilities

A record should be interpreted with its source, observation date, version, scope and unresolved limitations. Dataset presence is not evidence of current availability, operating authority, certification or technical condition. Public aggregates must not be used to infer restricted individual records.

Submit only material you are entitled to provide, preserve its provenance and identify corrections. A correction may require a superseding record rather than deletion of history. Access to one record does not grant rights to redistribute related documents or use them for another purpose.

Document sharing requires the relevant permission and available protected workflow. The proposed nexus-safe vault is not active on this public page. Do not send archives or sensitive evidence through unapproved channels. A reference code alone is neither encryption nor permission to open a document.

Ask a question about this notice
06

Civil-aviation scope

The platform serves civil-aviation maintenance, repair, supply, inventory, and support and does not support military or prohibited use.

Core admission boundary

public-notices-2026-10-16 · Public explanation

Read the notice and responsibilities

Nexus AeroChain serves civil-aviation maintenance, supply, resource coordination and related professional services. Military or defence use, prohibited trade, misrepresentation of end use and attempts to bypass applicable restrictions are outside the platform scope.

Nexus does not issue aviation licences, airworthiness determinations, installation approvals, maintenance releases or customs and dangerous-goods acceptance. Responsible participants must check the applicable authority, approved data, competence, records and transaction conditions independently of a platform status.

For urgent or safety-relevant matters, use your organization’s approved operational and emergency channels. A public support request, automated suggestion or marketplace listing is not an emergency response, technical instruction or permission to dispatch or install a component.

Ask a question about this notice

Need clarification?

Route a public-policy question to an accountable path.

Open help center