This page is for customers of GroundRoster, which Microsoft Marketplace lists as "AVIONIQX Ground Operations". It says how you take your data out of the service and in which form, what is not part of it, how a switch to another provider or to your own systems works, where the service runs, and what we do about requests for data from authorities outside the European Union. Annex 3 of the GroundRoster Subscription Agreement refers to this page, and we keep it up to date. Where this page and the Agreement differ, the Agreement applies.
1. Taking a complete copy
An administrator of your organisation takes the copy in GroundRoster itself: Settings, then "Plan & data", then "Export all data" and "Download the copy". The copy is one ZIP archive, named groundroster-export- followed by your organisation's code, the date and the time. It shows your data as it was at the moment the copy was started: every file in it shows the same moment.
During the subscription: at any time, also while the subscription is suspended.
After the subscription has ended: for the 30 days in which we keep your data (section 6). The product is closed then. An administrator who signs in gets one page, which says until when the data is kept and offers the copy. Nobody else of your organisation can sign in.
A copy is complete when the archive opens and holds the file manifest.json, which is written last. The download button checks that the archive is complete before it saves it. A copy that was cut off on the way cannot be opened.
Each copy is recorded in your organisation's audit trail, with the number of records it held.
The copy is free of charge.
If you cannot take the copy yourself, write to contact@technobyte.ai. We then give it to you as Annex 3 of the Agreement says.
2. What the copy contains
The files
| File | What it is |
|---|---|
| README.txt | What the archive holds and how to read it. |
| manifest.json | The list of what is in the archive: every data file with its table, its columns and its number of records; how the files link to each other; and what is not in the archive, with the reason. |
| data/ | One JSON file per table: 48 at the date of this page, listed below. |
| photos/ | The pictures taken on tasks, one image file each (JPEG, PNG or WebP), named after its record. |
| photos/index.json | One entry per picture: its record, its file, its type and size, and the task and the employee it belongs to. |
The formats
The archive is a ZIP file. All text is UTF-8.
Each data file is a JSON array (RFC 8259). Each element is one record: an object whose keys are the table's columns.
A number is a JSON number, yes or no is true or false, and an empty value is null.
A moment in time is written in UTC, in the ISO 8601 form 2026-06-11T07:30:00Z. A calendar day is written as 2026-06-11 and a time of day as 06:30; both are in the time of their station, whose time zone is in station.json.
A column whose name ends in _json holds a JSON document as text.
Every record has an id, which is unique within its table. A column whose name ends in _id holds the id of a record in another table. The manifest lists every such link.
The data structures
The register of the data structures is at https://legal.technobyte.ai/groundroster/data-export/register.json. It names every data file with its columns, the links between the files, and what is left out with the reason. It is the manifest of a copy without the figures of one organisation, and every copy carries the same list in its own manifest.json. The data files are:
| File in data/ | What it holds |
|---|---|
| organization.json | Your organisation: name, code and type. |
| station.json | Your stations: IATA and ICAO codes, name and time zone. |
| app_user.json | User accounts: e-mail address, name, role, station, the employee an account belongs to and the Microsoft account it is linked to. No passwords. |
| entra_tenant.json | The Microsoft Entra tenants linked to your organisation for sign-in. |
| employee.json | Employees: number, name, contact details, team, contract type, weekly hours, hire date and agency. |
| qualification.json | The qualifications you defined. |
| employee_qualification.json | Which employee holds which qualification, and from when until when. |
| employee_preference.json | Employees' preferences, with their weight. |
| agency.json | Staffing agencies and their certification. |
| leave_request.json | Leave requests: dates, type, status and decision. |
| leave_policy.json | Each station's leave policy: how days are counted, notice and automatic approval. |
| leave_entitlement.json | Leave entitlement per employee and year. |
| leave_allowance_rule.json | How many people of a team may be on leave at the same time. |
| shift_template.json | Shift templates: code, times, break and category. |
| roster_period.json | Roster periods with their status and score. |
| shift_demand.json | How many people each shift needs, per day and qualification. |
| shift_assignment.json | The rosters: who works which shift on which day. |
| coverage_requirement.json | The required coverage per day and qualification. |
| shift_pattern.json | Shift patterns. |
| shift_pattern_step.json | The steps of each shift pattern. |
| pattern_assignment.json | Which employee or team follows which pattern, and from when. |
| swap_request.json | Shift swap requests and their outcome. |
| rule_setting.json | The rostering rules as you set them: on or off, hard or soft, weight and parameters. |
| aircraft_visit.json | Flights and aircraft visits: airline, flight numbers, times, passengers and stand. |
| schedule_import.json | The flight schedule files you loaded, with their result. |
| stand.json | Stands and their restrictions. |
| gse_unit.json | Ground support equipment units. |
| task_type.json | The kinds of tasks and what each needs. |
| ground_task.json | Tasks: time window, status, the employee and the equipment assigned, actual start and end. |
| task_photo.json | The records of the pictures taken on tasks: which task and which employee each belongs to. |
| ops_event.json | Events of the day of operations, with their details. |
| station_location.json | Locations at a station, such as a checkpoint, with their terminal. |
| station_demand_settings.json | Each station's settings for the demand forecast. |
| service_parameter_set.json | Service parameters per location: lanes, throughput, service level and staffing. |
| show_up_profile.json | Passenger show-up profiles. |
| forecast_run.json | Forecast runs with their parameters and result. |
| passenger_forecast.json | Forecast and actual passengers per interval. |
| interval_demand.json | Staff demand per interval, location and qualification, with its explanation. |
| fixed_post_rule.json | Fixed posts: positions staffed at set times. |
| demand_upload.json | The demand files you loaded, with their result. |
| actual_attendance.json | Actual attendance per shift: start, end and absence. |
| actual_demand_interval.json | Actual demand figures per interval. |
| actuals_import.json | The files of actual figures you loaded, with their result. |
| notification.json | Notifications sent to your users. |
| subscription.json | Your subscription in Microsoft Marketplace: offer, plan, state and dates, and the buyer's Microsoft identifiers and e-mail address. |
| audit_event.json | The audit trail: who did what and when, sign-ins included. |
| aircraft_type.json | From the catalogue all customers share: the aircraft types your flights refer to. |
| gse_type.json | From the catalogue all customers share: the equipment kinds your equipment and task types refer to. |
3. What the copy does not contain
Left out is what belongs to the way the service works inside and whose disclosure would put its security at risk (Annex 3, section 5, of the Agreement):
passwords, which GroundRoster keeps only as hashes, and the counter that ends a user's sessions;
sign-in sessions, password-reset and invitation links, the links that connect a Microsoft account, calendar feed addresses, and browser registrations for notifications;
the accounts of TECHNOBYTE support, which are not your users; what such an account changed is in your audit trail;
the place where the service keeps a picture's file; the picture itself is in the copy;
the service's own bookkeeping and technical logs, and the software with the solver's built-in calculation rules.
Of the two catalogues that all customers share, aircraft types and equipment kinds, the copy holds the entries your own records refer to, and no others. Reports are made from your records when they are asked for and are not kept, so there are none in the copy.
4. Other ways to get data out and in
Reports. Every report in the product can be downloaded as a CSV file or as a PDF, for a period of up to 366 days at a time.
Loading data. GroundRoster loads data from CSV files: employees, their qualifications, shift templates, an earlier roster, the flight schedule, demand figures, leave entitlements and attendance. Each kind has a template to download, and a file is checked in a trial run before anything is stored.
A copy cannot be loaded back as a whole. The complete copy of section 1 is for use outside GroundRoster.
5. Interfaces for other providers
GroundRoster has no separate programming interface for other providers. The complete copy is one file in an open, documented format, which you can hand to your new provider or load into your own systems. Taking it is one HTTPS request made with the sign-in of one of your administrators. If your new provider is to take part in the switch, tell us in your notice (section 6), and we assist as Annex 3 of the Agreement says.
6. Switching to another provider or to your own systems
The rules are in Annex 3 of the Agreement. In short:
Notice. You write to contact@technobyte.ai that you want to switch to another provider (with its details), to move to your own infrastructure, or to have your data erased. The notice period is two months.
Transition. After the notice period you have up to 30 calendar days to move. You can extend this period once. If a switch cannot technically be completed in that time, we tell you within 14 working days of your notice and name another period of not more than seven months.
While it lasts. The service keeps running, its security measures stay in place, and the fees remain due. You can take the complete copy at any time, also before you give notice.
Retrieval. For 30 calendar days after the transition period, or after a subscription has ended in any other way, we keep your data and you can still get the complete copy.
Erasure. After the retrieval period we erase your data from the service. Copies in backups are overwritten within a further 35 days. A record that the subscription existed and that its data was erased remains. On request we confirm the erasure in writing.
Charges. We charge nothing for switching or for the copy. Work beyond that, such as converting the data to another provider's format, is charged at a price agreed with you in advance.
7. Known restrictions and technical limits
Only an administrator of your organisation can take the copy, and only of its own organisation.
One copy of an organisation is made at a time. A second request while one is running is refused, and so is a request while copies of two other organisations are running; try again a few minutes later.
The copy is one download. The hosting platform limits a request to 240 seconds, so a copy that takes longer than that may be cut off. The largest copy we have made so far held about 10,000 records and two pictures. We have not yet measured a copy of the size a large organisation reaches after years of use, or one with many pictures. If your copy does not finish, write to us: we then produce it for you another way, in the time Annex 3 of the Agreement gives.
The download button keeps the archive in the browser's memory until it is saved, so a very large copy needs a computer with enough memory.
The copy is in the formats of section 2. We do not convert it to another provider's format as part of the service.
GroundRoster holds only data: you bring no software, virtual machines or other digital assets of your own into it, so there are none to move.
8. Where the service runs
| What | Where |
|---|---|
| Database and its backups | Microsoft Azure, region France Central (France) |
| Application, technical logs and secrets | Microsoft Azure, region Germany West Central (Germany) |
| Provider of the infrastructure | Microsoft Ireland Operations Limited (Ireland), whose parent company is established in the United States |
| Operated by | TECHNOBYTE SOFTWARE SRL, from Romania |
The infrastructure is subject to the law of the European Union, of France, of Germany and of Romania.
9. Requests from authorities outside the European Union
What we have in place against access to your data by authorities of countries outside the European Union, where such access would conflict with the law of the Union or of a Member State:
Technical. Your data is stored in the two regions of section 8 only. A policy on our Azure subscription allows resources in these two regions and nowhere else, and the backups stay in the region of the database. Data is encrypted in transit between browsers and the service and between the application and the database, and at rest.
Organisational. TECHNOBYTE is a Romanian company and operates the service from Romania. Nobody at TECHNOBYTE has standing access to the production database.
Contractual. We store your data in the European Union and transfer it outside the European Economic Area only as Annex 1, section 7, of the Agreement says. We process personal data other than on your instructions only where the law of the European Union or of a Member State requires it, and we tell you beforehand unless that law forbids it (Annex 1, section 3). Your other confidential information we disclose only where the law, a court or an authority requires it, after telling you where the law allows (section 9.2). Microsoft sets out its own commitments on customer data in its Product Terms and its Data Protection Addendum. Microsoft states that it shares customer data only when the customer authorises it or the applicable law requires it, and that it gives no government direct or unfettered access to customer data.
10. Changes
We post changes to this page here, with the date.