SAIKER is provided by Awaire Technologies LLC (“SAIKER”, “we”, “us”). This policy covers this website and the SAIKER service.

SAIKER is used by aviation operators. For information an operator puts into SAIKER, the operator decides what is collected and why, and we process it on the operator's behalf. If you are a crew member or employee of an operator, contact your operator first about your information; we will help them answer you. For account and website information, and for our own business records, we decide how it is used.

This website sets no cookies and uses no analytics, advertising or tracking tools. Our host, Cloudflare, processes technical information such as IP addresses to deliver the pages and protect them from attack.

The contact form does not send anything to us. It opens your own email app with your message filled in. If you send it, we receive your email and the details you chose to include, and use them to reply.

Depending on the features your operator uses, SAIKER holds:

• Account information: name, work email, organization, role, the authenticator-app factor, and sign-in and session records, including IP addresses used to limit repeated attempts.
• Trips and aircraft: trip numbers, the customer name on a trip, legs, airports, times, aircraft registrations and type, equipment and deferred items, and the number of passengers. SAIKER does not import passenger names by default.
• Crew information: names, roles, bases, ratings, duty and rest times, and email address and phone number where your operator provides them.
• Pilot risk assessments: when a pilot opens a risk assessment link, we record the pilot's name and seat, their answers and notes, their sign-off, and the time, IP address and browser of the sign-off. We also record when the link was sent and opened.
• Safety and audit records: findings, acknowledgements, risk scores and approvals, checklist runs, safety management system records and exports, and a log of who did what and when.
• Documents: manuals, procedures and forms your operator uploads, stored privately for that organization.
• AI requests: questions to Ask SAIKER and the trip information needed to answer them; drafts and setup proposals are kept with your organization's records.
• Notifications: if you turn on browser notifications, the address your browser gives us for delivering them and a short description of the browser.
• Scheduling-system credentials: stored encrypted, never shown in full, and never passed to an AI model.

SAIKER does not ask for passport numbers, dates of birth, medical certificate details, payment card data or home addresses, and is not designed to hold them.

SAIKER receives FAA flight data through the FAA's System Wide Information Management service. It keeps only flights for the aircraft and flight numbers its customers operate, and shows each flight only to the operator that flies it.

Flights that the FAA marks as privacy protected, including aircraft in the Limiting Aircraft Data Displayed and Privacy ICAO Address programs, are not recorded in our aviation data history and are not shown to anyone but their operator.

• to run SAIKER for your organization: watch trips, show findings, send the notifications and emails your organization sets up, and answer questions;
• to keep SAIKER secure, prevent misuse and investigate problems;
• to provide support when your organization asks for it;
• to bill and manage our customer relationship; and
• to meet legal obligations.

We do not sell personal information or share it for advertising. We do not use customer information to train AI models, and our AI provider does not use it to train its models. Our staff access an organization's data only to provide support or keep the service secure.

We keep a history of public aviation data, such as weather observations and forecasts, FAA programs, NOTAMs and the timing of watched flights, to improve how SAIKER predicts conditions. This history contains no crew, passenger, customer, organization or trip information.

We may create statistics about how SAIKER is used, in a form that does not identify any organization, aircraft or person, and use them to run and improve SAIKER. We do not combine one operator's records with another's in any form that identifies either of them.

These providers process information for us under contract:

• Amazon Web Services (United States, us-east-1). Hosting, storage, scheduled jobs, the FAA data receiver, and email through Amazon SES.
• Amazon Bedrock (Amazon Web Services). Runs the AI models (Amazon Nova) for Ask SAIKER, summaries, drafts and setup from documents.
• Supabase. The database and sign-in service, including authenticator-app second factors.
• Cloudflare. Hosts this website and its domain name records.
• FlightAware. Only where your organization turns it on: receives the identifiers of the flights it tracks.

SAIKER also exchanges information with these services as part of how it works:

• Your scheduling system (FL3XX, Avianis, or a file you upload). SAIKER reads trips, aircraft and crew from it, using credentials your administrator provides. These providers work for you, not for us.
• CARTO and RainViewer. Your browser loads map tiles and radar images directly from them, so they receive your IP address as any website would.
• Browser push services. If you turn on notifications, your browser's push service (such as Apple, Google or Mozilla) delivers them.
• adsbdb. When someone adds a real flight by hand, SAIKER may look up the aircraft registration there.

We tell customer administrators by email at least 30 days before we add a provider that processes Customer Data. We may also disclose information when the law requires it, or to a successor if our business is reorganized or sold, under this policy.

SAIKER stores information in the United States. If you use SAIKER from another country, your information is transferred to the United States.

We keep Customer Data for as long as the operator's subscription lasts, or for a shorter period the operator sets. When a subscription ends, the operator can export its data for 30 days. We then delete it within a further 30 days, and from backups as they expire, unless the law requires us to keep it.

Pilot risk assessment links expire a set time after the flight departs. The record of the assessment stays with the operator's safety records. Server logs are kept for up to three months. Emails you send us are kept as long as needed to deal with them and for our business records.

Every account uses an authenticator app as a second factor. Each operator's data is kept separate by database rules that are tested automatically, and SAIKER only reads from scheduling systems. Information is encrypted in transit, stored documents are encrypted at rest, and scheduling-system credentials are sealed with their own encryption. No system is perfectly secure. If a security incident affects your information, we will tell the affected operators without undue delay.

Depending on where you live, you may have rights to see, correct, delete or receive a copy of your personal information, or to object to how it is used. Crew and staff of an operator should ask their operator, which controls that information; we will help it respond. For anything else, write to [email protected]. We will not treat you differently for exercising these rights.

You can turn browser notifications off at any time in SAIKER or in your browser.

SAIKER is a business service and is not meant for anyone under 18. We do not knowingly collect information from children.

We will post any update here with a new effective date, and tell customer administrators by email about a material change. Questions or requests: Awaire Technologies LLC, [email protected].