x.1 Foundation × FAA

IT Preparation

Enter the access code for the IT preparation session.

← Back to portal

This is our shared working document. Together we map the technical landscape — the answers here shape every infrastructure and access decision we make jointly. Wherever something needs a follow-up, it lands in our shared action list at the bottom automatically.
  Completion
0% 0 action items
Current Infrastructure 1 / 6  
Includes physical servers at your office, rented cloud VMs, or any hosting services for your website.
Select all that apply. This shapes our infrastructure decision together: Azure VM if you're already in the Microsoft ecosystem, or Linux VPS for a lighter, more flexible setup.
"Comfortable" means someone on your team can install software, manage files, and restart services. The workshop system runs on either Windows Server or Linux.
This is the person x.1 Foundation works alongside throughout — from setup to the final handover. A clearly named partner makes everything run smoothly.
Microsoft 365 & Graph API — Our Integration Foundation 2 / 6  
Microsoft 365 confirmed — email and Forms data accessible via MS Graph API. This is the integration layer we build on together.
This determines how many years of email history we can mine. The further back, the richer the data — but we need to know where the coverage starts.
This determines how we scope the mailbox extraction. Individual accounts mean we need access to multiple mailboxes; shared inboxes require different permissions.
Roughly how many email accounts receive or send prospect enquiries. Each mailbox counts as one data source.
The M365 Global Admin grants the API permissions for the Graph integration. We only need them for a focused 30-minute session — you run the configuration, x.1 guides remotely and you keep full control of all credentials.
Registering an app in Azure AD (Entra ID), setting API permissions, generating a Client Secret. Since you're familiar with Graph API, this is a quick configuration step — we'll do it together via screen-share and you stay in full control of the credentials.
Data Landscape — What We'll Work With Together 3 / 6  
Select all that apply — this is the data landscape we'll work through together. More sources means richer analysis, but we scope to what's realistic for the workshop timeline.
Rough estimates help us size the server correctly and estimate processing time. No precision needed.
Workspace Setup — Where We'll Run the Workshop 4 / 6  
The workshop makes AI API calls and screen-share sessions. A stable broadband connection (10 Mbps+) is more than enough — we've designed it to work within normal office conditions.
Helps us plan machine requirements and prepare the right number of workspaces.
Ideally each person has their own laptop or desktop for the duration of the workshop. Sharing machines slows down hands-on exercises.
Desktops with large monitors are ideal for intensive data work — bigger screens make a real difference for side-by-side comparisons.
Workshop sessions involve multiple open windows simultaneously. Larger or dual screens significantly improve the experience.
The IT station is used for setup, monitoring, and troubleshooting during the workshop. Two screens make this significantly easier.
Blocked ports, content filtering, VPN requirements, or managed devices. Most office setups have none — but strict environments may need port whitelisting.
Our Shared Team 5 / 6  
The IT lead is our primary collaborator throughout — actively involved in setup, validation, and the final handover. Reachable by phone during the workshop week.
Helps us tailor the workshop content and pace to each group — so everyone gets value from the sessions, not just the technical participants.
Data Privacy & Compliance 6 / 6  
FAA's privacy page lists faadataprivacy@firstaviationacademy.com as the privacy contact. Under RA 10173, the DPO should be identified by name. Can you confirm who manages this inbox?
If a data subject (prospect, parent, applicant) emails faadataprivacy@firstaviationacademy.com with a request to access or delete their data — who receives it, and is there a process for responding?
FAA's privacy page shows an NPC Certificate of Registration seal dated November 2024. Can you confirm this registration is current and provide the registration number?
Our privacy review found tracking IDs G-XRKCMPCDY1, G-XD00KKP0LZ, G-82SDLRBSQ9, and UA-154625202-1 loading on every page. Under RA 10173, this requires user consent. Do you know who manages these?
FAA has a Data Sharing Agreement template from 2020 — but a DACA is different: it covers supervised server access, not data sharing between controllers. Since x.1 never stores data locally, we use a lighter Data Access & Confidentiality Agreement instead of a full DOA.
The DACA must be signed before x.1 Foundation receives server access. Typically signed by the CEO, General Manager, or DPO. Draft PDF available. Digital signature accepted.
Our Shared Action List

Built live as we work through each topic together. These are the things we jointly commit to before the call ends.

  Leadership Commitments
Fill in the form to generate action items…
  IT Lead Actions
Fill in the form to generate action items…
  HR Coordination
Fill in the form to generate action items…

Data Privacy Requirement — RA 10173

A Data Access & Confidentiality Agreement (DACA) between FAA and x.1 Foundation must be signed before server access is granted. x.1 accesses FAA's server but never stores personal data locally — this lightweight agreement covers access restrictions, confidentiality, and breach notification under RA 10173. Download DACA Draft (PDF). Digital signature accepted.

Full Data Privacy & Compliance overview
← Back to portal  ·  x.1 Foundation × First Aviation Academy — Data Mining Workshop 2026