Skip to content
Search icon

    Purposes for Processing Personal Data

    Last Updated: November 1, 2026

    Below is a description of the ways we may use your data and the legal basis we rely on to do so. We have also identified what our legitimate interests are, where appropriate, and we have identified when the purpose is limited to a specific product or Service.

    We may process your personal data for more than one legal basis depending on the specific purpose for which we are using your data. Please contact us at privacy@jetnet.com if you need details about the specific legal basis we are relying on to process your personal data, where more than one basis has been set out in the table below.

    Purpose/Activity Type of data Lawful basis for processing
    including basis of legitimate interest

    To register you as a new customer:
    (a) Create an account for you
    (b) Provide our products
    (c) Manage our systems
    (d) Prevent fraud
    (e) Send you marketing communications
    (f) Share this information with third parties if you have provided your consent to this

    (a) Identity
    (b) Contact

    (a) Performance of a contract with you
    (b) Necessary to comply with a legal obligation
    (c) Necessary for our legitimate interests
    (d) Consent

    To understand the way you use our products:
    (a) Identify products/services that may be of interest to you
    (b) Monitor usage of website and app
    (c) Provide location-based functions
    (d) Upload your photos and videos
    (e) Send notifications
    (f) Personalise our service
    (g) Statistical analysis and research
    (h) Improve our services
    (i) Develop new products and services
    (j) Record, transcribe, and summarize calls and meetings

    (a) Identity
    (b) Contact
    (c) Technical
    (d) Marketing and Communications
    (e) Audio and Video Recordings

    (a) Necessary for our legitimate interests (to keep our records updated and to study how customers use our products/services)
    (b) Performance of a contract with you
    (c) Consent

    To process and deliver your order including:
    (a) Manage payments, fees and charges
    (b) Collect and recover money owed to us
    (c) Foreign money exchange
    (d) Deliver purchased products.

    (a) Identity
    (b) Contact
    (c) Financial
    (d) Payment
    (e) Marketing and Communications

    (a) Performance of a contract with you
    (b) Necessary to comply with a legal obligation
    (c) Necessary for our legitimate interests (to recover debts due to us)

    Information when you communicate with us whether in person, through our website or app, via email, over the phone, through social media or via any other medium. We use this to:
    (a) Answer any of your issues or concerns
    (b) Monitor customer communications for quality and training purposes
    (c) Develop new services
    (d) Improve our services based on the feedback you provide
    (e) Record, transcribe, and summarize calls and meetings

    (a) Identity
    (b) Contact
    (c) Payment
    (d) Marketing and Communications
    (e) Community Interactions
    (f) Audio and Video Recordings

    (a) Performance of a contract with you
    (b) Necessary for our legitimate interests (to provide a better service)
    (c) Consent

    To manage our relationship with you which will include:
    (a) Notifying you about changes to our terms or privacy notice
    (b) Resolving technical issues
    (c) Asking you to provide feedback on our service

    (a) Identity
    (b) Contact
    (c) Technical
    (d) Marketing and Communications
    (e) Community Interactions

    (a) Performance of a contract with you
    (b) Necessary to comply with a legal obligation
    (c) Necessary for our legitimate interests (to keep our records updated and to study how customers use our products/services)

    To administer and protect our business, our websites and Services (including troubleshooting, data analysis, testing, system maintenance, support, reporting, hosting of data, and anti-money laundering checks).

    (a) Identity
    (b) Contact
    (c) Technical
    (d) Community Interactions

    (a) Necessary for our legitimate interests (for running our business, provision of administration and IT services, network security, to prevent fraud and in the context of a business reorganisation or group restructuring exercise)
    (b) Necessary to comply with a legal obligation

    To deliver relevant website content

    (a) Identity
    (b) Contact
    (c) Usage
    (d) Marketing and Communications
    (e) Technical

    (a) Necessary for our legitimate interests (to study how customers use our products/services, to develop them, to grow our business and to inform our marketing strategy)

    To transmit professional contact information for internal data matching and accuracy improvements to enhance Services

    (a) Identity
    (b) Contact

    (a) Performance of a contract with you
    (b) Necessary for our legitimate interests (to develop our products/services)

    To use data analytics to improve our website, products/services, marketing, customer relationships and experiences

    (a) Technical
    (b) Usage
    (c) Identity

    (a) Necessary for our legitimate interests (to define types of customers for our products and services, to keep our website updated and relevant, to develop our business and to inform our marketing strategy)

    To make suggestions and recommendations to you about services that may be of interest to you, including through the use of your personal data and marketing communications, where permitted by law or based on your consent.

    (a) Identity
    (b) Contact
    (c) Technical
    (d) Usage
    (e) Marketing and Communications

    (a) Necessary for our legitimate interests (to develop our products/services)
    (b) Consent, where required by law (e.g., for direct electronic marketing)

    Information that we collect incidentally from other sources or public sources, including information presented on our social media or wider social media platforms including Facebook, Twitter and Instagram. We use this information, including to:
    (a) Maintain market awareness
    (b) Build and maintain social media branding

    (a) Technical
    (b) Usage
    (c) Marketing and Communications

    (a) Necessary for our legitimate interests (to develop our products/services and grow our business)

    JETNET Mobile Applications

    The following purposes and legal bases apply specifically to JETNET’s Mobile Applications, in addition to the purposes described above. These entries reflect processing that occurs only within the mobile application(s), including device location, push notifications, augmented reality features, and mobile session management.

    Purpose/Activity Type of data Lawful basis for processing
    including basis of legitimate interest

    To deliver proximity alerts for mobile app users:
    (a) Identify nearby aircraft based on the user’s current location
    (b) Deliver push notifications when a tracked aircraft is within the user’s selected proximity threshold

    (a) Precise Geolocation
    (b) Push Notification

    (a) Consent

    Retention: Location data retained for 7 days after last activity; push notification tokens retained for 90 days after inactivity; alert cooldown markers deleted after 24 hours.

    To retrieve live aircraft position data for mobile app users:
    (a) Use the user’s current location to query JETNET and ADS-B Exchange aircraft position feeds
    (b) Display nearby aircraft on the in-app map

    (a) Precise Geolocation
    (b) Technical

    (a) Performance of a contract with you

    Retention: Location data retained for 7 days after last activity.

    To provide augmented reality aircraft identification features in the mobile app:
    (a) Access device camera and motion sensors to overlay aircraft data on a live camera view

    (a) Device Sensor

    (a) Performance of a contract with you

    Retention: Processed on device, never stored or transmitted.

    To store and manage user preferences and activity in the mobile app:
    (a) Maintain tracked aircraft lists
    (b) Store alert preferences and proximity threshold settings
    (c) Record lifetime sighting statistics

    (a) User-Generated Content

    (a) Performance of a contract with you

    Retention: User preferences and activity data retained until account deletion.

    To manage authentication and session security for mobile app users:
    (a) Issue and validate session tokens
    (b) Store encrypted refresh tokens server-side
    (c) Maintain short-lived session tokens on the user’s device via secure storage (iOS Keychain / Android Keystore)
    (d) Delete all session data on logout or account deletion

    (a) Session
    (b) Identity
    (c) Technical

    (a) Performance of a contract with you
    (b) Necessary for our legitimate interests (to protect user accounts and prevent unauthorised access)

    Retention: Sessions deleted after 30 days; device-side tokens cleared on logout.

    To apply rate limiting to unauthorized mobile app requests:
    (a) Monitor request frequency by IP address to detect and prevent abuse
    (b) Temporarily block or throttle excessive requests from a single source

    (a) Technical

    (a) Necessary for our legitimate interests (to protect the availability and security of our services and prevent abuse)

    To manage consent audit records for authenticated mobile users:
    (a) Issue consent record details
    (b) Store consent record details
    (c) Validate user and consent records

    (a) Consent Records
    (b) Identity
    (c) Technical

    (a) Necessary for our legitimate interests (to protect user accounts, maintain a verifiable record that consent was given, and prevent unauthorised access)

    To manage consent for anonymous mobile users:
    (a) Issue anonymous Universally Unique Identifier (UUID) stored on device
    (b) UUID provided with consent record details for storage and processing
    (c) Validate UUID and consent records

    (a) Consent Records
    (b) Technical

    (a) Necessary for our legitimate interests (to maintain a verifiable record that consent was given and to prevent duplication or tampering with the consent record)

    ADS-B Exchange Feeder Applications

    The following purposes and legal bases apply specifically to the ADS-B Exchange feeder applications, in addition to the purposes described above. These entries reflect processing of data sent by the feeder applications, including receiver location for multilateration (MLAT), feeder statistics, and public feeder pages.

    Purpose/Activity Type of data Lawful basis for processing
    including basis of legitimate interest

    To operate the ADS-B Exchange feed and multilateration (MLAT) for feeder application users:
    (a) Receive aircraft data sent by the feeder application
    (b) Use the receiver’s precise location and antenna altitude to calculate MLAT aircraft positions

    (a) Precise Geolocation
    (b) Feeder ID
    (c) Technical

    (a) Necessary for our legitimate interests (to operate ADS-B Exchange flight tracking and MLAT)

    Retention: Snapshots that include the precise receiver location and IP address are deleted after 60 days. Feeders inactive for 90 days are removed from the feeder registry. Daily presence records are retained as part of ADS-B Exchange’s historical network records.

    To provide feeder statistics and public feeder pages:
    (a) Display feeder statistics, the leaderboard, and the Feeder Hub
    (b) List feeders by feeder name on public MLAT pages
    (c) Show an approximate receiver location for feeders who have not turned on MLAT privacy

    (a) Feeder ID
    (b) Feeder Name
    (c) Receiver Statistics
    (d) Approximate Geolocation

    (a) Necessary for our legitimate interests (to provide feeder statistics and recognize feeder contributions)

    Retention: Statistics caches expire within 30 days of the last upload. Daily leaderboard history is retained as part of ADS-B Exchange’s historical network records.

    To distinguish feeders and measure feeder application use:
    (a) Tell feeders apart
    (b) Count feeders by application

    (a) Feeder ID
    (b) Technical

    (a) Necessary for our legitimate interests (to manage the ADS-B Exchange feeder network and measure application use)

    Retention: Feeders inactive for 90 days are removed from the feeder registry.

    To link a feeder to your ADS-B Exchange account:
    (a) Link a feeder to your account
    (b) Send feeder status notifications by email or phone, if you turn them on

    (a) Identity
    (b) Contact
    (c) Feeder ID

    (a) Performance of a contract with you
    (b) Consent (for notifications)

    Retention: Retained while the feeder is linked to your account, or until you request deletion.