LEGAL AIRBRIDGE
Terms of Service
Version 1.1 · Effective 22 November 2026 · Last updated 22 November 2026
These Terms of Service (“Terms”) are the agreement between you and the AirBridge project for the AirBridge applications, the browser interface, the command-line tools and relay, and the website at airbridge.fyi. AirBridge is an independent, source-available project maintained by Diganta Dey and the AirBridge contributors.
AirBridge is built to keep your information on your own devices. There is no AirBridge account, no AirBridge cloud drive holding your files, and no advertising or analytics software in the Android app. In exchange, the software is provided as-is, its Licence permits personal non-commercial use without payment, and we cannot promise that any software — including this one — is free of defects or completely safe from attack.
1. Introduction
AirBridge is a source-available, privacy-focused device connectivity application. It connects an Android phone with a macOS, Windows or Linux computer so that you can transfer files, synchronise the clipboard, view the phone screen, search contacts, handle calls, and pair and reconnect devices — without creating an AirBridge account and without an AirBridge cloud service storing your content.
These Terms explain what you may expect from AirBridge, what we expect from you, and the limits of what the software can promise. They are written to be read by ordinary users rather than lawyers, and they are structured so that each topic has its own section. Words with a specific meaning are defined in Section 2.
2. Definitions
- “AirBridge”, “we”, “us”, “our” — the AirBridge project, maintained by Diganta Dey and the AirBridge contributors. AirBridge is an independent project and is not affiliated with or endorsed by Apple, Google or any other platform vendor.
- “Software” — the AirBridge Android application, the macOS, Windows and Linux desktop companions, the browser-based client, the command-line interface, the background daemon, the relay component, installers and release artefacts.
- “Service” — the Software together with the features it provides, including device pairing, file transfer, clipboard synchronisation, screen sharing, contacts, call controls and connectivity fallbacks.
- “Website” — the public static site at airbridge.fyi, including this page and the Privacy Policy.
- “Device” — an Android phone or tablet, or a computer, on which the Software runs.
- “Paired Device” — another Device that has completed AirBridge’s pairing process with yours and is therefore trusted by your installation.
- “Relay” — an optional AirBridge relay component that forwards encrypted traffic between Devices when no direct network path exists. A Relay may be run by you, or by whoever operates the relay you configure.
- “User Content” — files, folders, clipboard text or images, contacts, screen content, call audio and any other material you choose to send, receive or share through the Software.
- “Diagnostics” — local, scrubbed diagnostic logs and crash reports that the Software keeps on your own Devices and shares only when you explicitly choose to copy or send them.
- “Licence” — the AirBridge Fair-Use & Non-Commercial License that applies to the Software’s source code and binaries.
- “Privacy Policy” — the AirBridge privacy policy published at airbridge.fyi/privacy.
3. Acceptance of Terms
By downloading, installing, running, pairing or otherwise using the Software or the Website, you agree to be bound by these Terms. If you do not agree, do not install or use AirBridge, and uninstall it if you already have.
If you use AirBridge on behalf of an organisation, you confirm that you have authority to accept these Terms for that organisation — but note that organisational, corporate and commercial use also requires the prior written consent described in Section 15. If you do not have that authority or consent, do not use AirBridge for the organisation.
These Terms apply together with the Licence and the Privacy Policy. Where they differ, the Licence governs your rights in the source code and binaries, the Privacy Policy governs how information is handled, and these Terms govern your use of the Service.
4. Eligibility
You may use AirBridge only if you can form a binding agreement with us under the law that applies to you. If you are below the age of legal majority where you live, you may use AirBridge only with the involvement and consent of a parent or legal guardian, and only under their supervision.
You must be at least 13 years old, or older if your country sets a higher minimum age for consenting to online services. You may not use AirBridge if you are barred from doing so by applicable law, or if you are located in, or ordinarily resident in, a country or region subject to comprehensive trade sanctions that prohibit your use of the Software.
5. Description of the Service
AirBridge connects an Android phone to a computer over a network. When the Devices can reach each other directly — typically on the same local network — the connection is established directly between them. Supported capabilities include:
- File transfer — sending files and folders in either direction, with direct-to-disk streaming, resumable transfers inside a running session, and SHA-256 verification before a received file is published to the destination folder.
- Clipboard synchronisation — text in both directions, and images where the platform allows it, driven by an explicit AirBridge action or by the optional automatic setting where the operating system permits it.
- Screen sharing — viewing the phone screen on a computer through a consent-based, end-to-end encrypted H.264 stream, and sharing a computer screen or window with another computer through the browser picker.
- Device pairing and connectivity — QR-code or six-character pairing, verification codes, trust pinning, phone-hotspot handoff, and relay fallback when no direct path exists.
- Optional phone features — contacts search, call controls and optional two-way call audio, each disabled until you enable it and grant the matching permission.
- Desktop, browser and command-line clients — native desktop companions, a browser interface, and a CLI with a background daemon and a self-hostable relay.
The Service has real limits, and we would rather state them than let you discover them at the wrong moment:
- A desktop companion is required for the full feature set. The browser interface offers file transfer and clipboard sharing, subject to browser permissions, and does not promise native integrations.
- There is no native iOS app. iPhone and iPad use the browser interface only.
- Remote control of a phone from the desktop is not supported.
- AirBridge does not bypass platform protections. It does not use Android Accessibility Services or a notification listener, does not read call logs, and does not capture DRM-protected or otherwise protected content.
- AirBridge is not a backup service, a cloud storage provider, a remote device management platform, or a replacement for a virtual private network.
- The Website is informational and static. It does not host your content and does not require a sign-in.
6. Distribution Channels and Pricing
AirBridge is one product distributed through more than one channel, and the price of a copy depends on the channel you obtained it from. The Licence described in Section 15 sets out what you may do with the Software; it does not set prices and does not require a payment for any channel. This section explains the channels; it does not quote a price for any of them.
- Official GitHub releases — free. Every official release published in the AirBridge GitHub repository at github.com/DigantaDey/AirBridge/releases is distributed free of charge. That includes the macOS app, the Windows executable, the Linux binaries, the Android APK and the command-line tools. Downloading from GitHub needs no payment, no account and no store transaction, and the project does not intend to introduce a payment requirement for its official GitHub releases.
- Google Play — paid distribution. The Android application is intended for distribution through Google Play as a paid app. The project may charge for that platform-specific distribution to recover Google Play and developer-account fees, review and distribution overhead, and related platform costs. No Google Play listing is published at the date of these Terms, so the free Android APK in the official GitHub releases remains available for sideloading in the meantime. When a listing is published, the price is set and displayed by Google Play at the point of purchase in your local currency, and the listing — not this page — is the authoritative statement of that price.
- Mac App Store — possibly paid in future. AirBridge is not currently distributed through the Mac App Store, and these Terms do not announce such a release. If a Mac App Store edition is released in future, it may also be paid, for the same platform-fee and distribution-cost reasons. The direct macOS build in the official GitHub releases stays free of charge either way.
- Direct desktop downloads — free. The macOS, Windows and Linux builds in the official GitHub releases are free, whether you install them with the project’s one-line installer or download the archive yourself.
- Store transactions are handled by the store. If you obtain a copy through Google Play or, in future, the Mac App Store, the transaction is processed by that store operator, not by AirBridge. AirBridge does not process payments, does not receive or store your payment card details, and cannot issue refunds on the store’s behalf; the store’s own terms, refund policy and privacy policy apply to that purchase. Obtaining a free GitHub release creates no payment relationship at all.
Paying for a store copy does not widen the permissions you receive under the Licence, and using a free GitHub release does not reduce your obligations under it. Where these Terms describe a copy as “free”, they mean free of charge for that distribution channel. Our Privacy Policy explains how distribution and payment information is handled.
7. Account and Registration
AirBridge does not require a personal account, email address, phone number or password for normal use, and there is nothing to register. There is therefore no account we can look up, reset, recover or delete on your behalf.
The Software does keep some records locally on your Devices so that it can reconnect safely — for example the paired computer’s address, device identity material, pairing state and the pinned TLS trust information. These records stay on your Devices, and Android backup is disabled for the app. You can remove a pairing with Forget in the Android app, or by uninstalling the Software and deleting its local data. Because there is no account, protecting access to your Devices with a screen lock and disk encryption is your responsibility.
8. Device Pairing and Authorization
Pairing authorises another Device to interact with yours, so treat it as a security decision rather than a formality. AirBridge pairs with a QR code or a six-character code. The code is proven with SPAKE2 (RFC 9382) and is never transmitted, not even hashed, and repeated guesses are rate-limited. A six-digit verification code (SAS) is derived from the session keys so you can compare it on both screens; comparing it the first time you pair is the most reliable way to rule out a man-in-the-middle.
You agree that:
- you will pair only Devices that you own, or that you are clearly authorised to connect — never someone else’s phone or computer without their informed permission;
- you are responsible for the capabilities you enable for a Paired Device, since a trusted Device can use the features you have switched on, subject to per-session approvals such as screen sharing;
- you will keep pairing codes and QR codes away from people who should not pair with your Devices;
- if a Device is lost, sold, repaired or otherwise outside your control, you will remove the pairing on the other Device (for example with Forget) and change any credentials that were exposed;
- you understand that first-use TLS pinning is not out-of-band authentication: an attacker present at the very first contact could establish their own pin, which is why comparing the verification code matters.
Unpairing or forgetting a Device removes the saved trust on that side. AirBridge will not silently fall back to an unencrypted connection when an identity changes; it fails closed and requires a new pairing.
9. User Responsibilities
You are responsible for how you use AirBridge and for the Devices and networks you use it on. In particular, you agree to:
- Use it lawfully. Comply with the laws that apply to you, including privacy, data protection, confidentiality, export control and computer-misuse laws.
- Only share what you may share. Make sure you have the rights and permissions needed to transfer files, sync clipboard content, share screens, or expose contacts and call controls.
- Secure your Devices. Keep operating systems and AirBridge up to date, use screen locks, and remove pairings you no longer need.
- Respect other people. Do not capture or share another person’s screen, clipboard, conversations or personal data without the consent required by law, and follow any workplace or client confidentiality obligations you are subject to.
- Follow network rules. Some networks, employers and hosting providers restrict device-to-device traffic, relays or peer-to-peer connections. It is your responsibility to comply with those rules.
- Keep your own backups. AirBridge verifies transfers as documented, but it is not a backup system and cannot recover content that was never sent, was interrupted, or was deleted.
- Supervise minors. If a minor uses AirBridge on a Device you manage, you are responsible for their use and for the pairings and permissions on that Device.
10. File Transfers and User Content
You keep ownership of your User Content. We do not claim any ownership of your files, clipboard items, contacts or screen content. You grant us only the limited, temporary permission needed to operate the feature you have asked for on your own Devices — for example decrypting a file on the receiving Device so it can be written to disk. That permission ends when the operation ends.
Files travel between the sender and the paired receiver you choose. We do not receive, store, index or review your User Content, and we have no ability to access it or to restore it for you. If a relay is used, the relay forwards encrypted traffic and is not given the content encryption keys.
What AirBridge does and does not guarantee about transfers:
- Received files are hashed while they stream, and the declared SHA-256 digest is checked before the file is published to your destination folder.
- Transfers can resume within a running session after an interruption. If the app is force-stopped, the process dies, or a device identity changes, you will need to send the file again.
- Browser-based receives that cannot use the File System Access API are memory-limited; use the native app or a disk-backed receive folder for very large files.
- File names, sizes and timing are visible to the Devices involved and, on some networks, to the network operator.
You are responsible for the content you send and for the content you accept. Treat files from other people with the same caution you would apply to any download: scan them, and do not run anything you do not trust. You are also responsible for deleting content you no longer need from your own Devices.
11. Clipboard and Screen Sharing
Clipboard. Clipboard synchronisation sends text, and images where the platform supports it, to your Paired Devices. It is triggered by an explicit AirBridge action (share, process text, the Quick Settings tile, or paste in AirBridge), or by the optional automatic setting where your operating system permits it. Android 10 and later restrict background clipboard reads, and AirBridge does not use Accessibility Services to bypass that restriction. Clipboard content can include passwords, one-time codes, private messages and other sensitive material; a Paired Device may receive what you copy, so treat clipboard sync as a feature you enable deliberately and switch off when it is not appropriate.
Screen sharing. A Paired Device can request a view of your phone’s screen only after you approve it in AirBridge and then approve Android’s own screen-capture prompt. Each session must be approved on the Device being shared and can be stopped from either side. Permitted playback audio is optional per session, off by default, and never includes microphone audio; the optional microphone use is limited to the separately enabled call-audio feature. Protected content, including DRM-protected video and app windows that opt out of capture, may be blank by design — AirBridge does not bypass those flags. Computers can also share a screen or window with each other through the browser picker.
Only share a screen or clipboard with people who are entitled to see it. Anything visible on screen — notifications, messages, documents, account details — becomes visible to the viewer, and their own recording or confidentiality obligations are between you and them.
12. Privacy and Data Handling
Our Privacy Policy describes what AirBridge handles and is the authoritative statement on data handling. In summary:
- AirBridge does not require an account, does not sell personal data, and contains no advertising SDK, analytics SDK, Accessibility Service or notification-listener service in the Android app.
- Content moves between the Devices you pair. AirBridge does not upload your selected content to an AirBridge cloud service.
- Pairing records, device identity material, trust pins, transfer and clipboard history, and scrubbed local Diagnostics stay on your own Devices, subject to the product’s retention limits and your ability to delete them.
- Diagnostics are shared only when you explicitly choose to copy them, report on GitHub, or send a report after reviewing the contents.
- If a Relay is used, it carries encrypted traffic and can observe ordinary connection metadata such as addresses and timing; it is not given the content encryption keys.
- The Website is static, requires no sign-in and sets no advertising cookies.
This section is a summary, not a substitute for the Privacy Policy. If these Terms and the Privacy Policy appear to conflict on how information is handled, the Privacy Policy controls.
13. Security
AirBridge is designed so that a shared network is not automatically a trusted network. Its security features include SPAKE2 pairing with a code that is never transmitted, ephemeral ECDH P-256 key agreement with HKDF derivation, AES-256-GCM for file chunks, clipboard items, call frames and screen frames, six-digit verification codes you can compare out of band, TLS identity pinning on first use, and a host boundary that limits clipboard writes, saving into the received-files folder and opening folders to loopback requests. Unpaired devices can see device names and public keys before pairing, which is why pairing and verification are explicit.
These measures are designed to protect your communications, but no software can guarantee absolute security. AirBridge has not undergone an independent third-party security audit, and we do not claim that it is certified, penetration-tested by a third party, immune to attacks, or free of vulnerabilities. We also cannot guarantee that data will never leave a local network: a relay route, a hotspot, a misconfigured network, a compromised Device or an operating-system feature you enable can each carry traffic beyond the local link.
The project documents its known residual risks — including first-contact man-in-the-middle risk, unpaired devices being able to offer transfers, the loopback trust boundary, and the plain-HTTP local certificate bootstrap — in SECURITY.md. Please read it if you rely on AirBridge in a sensitive environment. Your responsibilities include installing updates, comparing verification codes when it matters, disabling features you do not need, and using networks and Devices you trust.
If you believe you have found a security vulnerability, please report it privately as described in SECURITY.md rather than opening a public issue. We will do our best to investigate and respond, but we do not promise a particular response time or a fix for every report.
14. Third-Party Software and Services
AirBridge depends on, and is distributed through, services and components that we do not control. These include GitHub (source hosting, releases, checksums and issue tracking), Google Play, where the Android app is planned to be distributed as a paid app, the operating-system services of Android, macOS, Windows and Linux, and platform clipboard or media components such as the macOS pasteboard, Windows clipboard cmdlets, and wl-clipboard, xclip or xsel on Linux. The CLI, daemon and relay run on Node.js. The Website is served as static files and its domain name uses third-party DNS.
Your use of a third-party service is governed by that service’s own terms and privacy policy, and we are not responsible for it. A third-party service may change, rate-limit, suspend or discontinue access in ways that affect downloads, updates or the Website. Third-party open-source libraries included in AirBridge remain under their own licences; nothing in these Terms or in the Licence overrides those licences.
Product names and marks such as AirDrop, Continuity and iPhone Mirroring (Apple), and Android, Quick Share and Google Play (Google), as well as macOS, Windows and Linux, belong to their respective owners. AirBridge is an independent project and is not affiliated with, sponsored by or endorsed by any of them.
15. Source-Available Software and Licence
AirBridge is source-available. The source code is public and readable, but AirBridge is not “open source” in the OSI sense, because the Licence restricts commercial and organisational use. The Licence is the AirBridge Fair-Use & Non-Commercial License; the full text is in LICENSE in the source repository.
- Permitted without charge. Personal, individual, non-commercial use by a single user on their own personal Devices, including obtaining, copying, modifying, merging and running the Software for that purpose, and including the copyright and permission notice in copies and substantial portions.
- Requires prior written consent. Any commercial, corporate, organisational, enterprise or monetised use; any distribution, bundling, sublicensing or re-sublicensing; any hosted service deployment; and any resale of the Software or derivative works. Consent must come from the primary author, Diganta Dey, before that use begins. To ask, email hello@airbridge.fyi.
- Derivative works are subject to the same restrictions as the Software.
- No warranty in the Licence. The Software is licensed “as is”, without warranty of any kind, and the Licence’s liability exclusion applies in addition to Sections 19 and 20 below.
If the Licence and these Terms conflict about your rights in the Software, the Licence controls. If you are unsure whether your intended use is permitted, ask before you rely on it.
16. Acceptable Use
You must not use AirBridge, or any relay or instance you operate, to:
- break any law, regulation or court order, or infringe anyone’s intellectual-property, privacy, personality or confidentiality rights;
- access a Device, account, network or data without the owner’s permission, or help anyone else do so;
- send or store malware, ransomware or other harmful code, or content that is illegal, abusive, harassing, or sexually exploitative of minors;
- intercept, decrypt, monitor or exfiltrate another person’s communications or content;
- bypass, defeat or circumvent DRM,
FLAG_SECURE, capture prompts, permission dialogs or other platform protections; - covertly capture another person’s screen or clipboard, or use the Software for stalking, domestic surveillance or coercive monitoring;
- use the Software commercially or organisationally without the written consent required by Section 15, or resell, rebrand, white-label or bundle it without permission;
- remove or obscure copyright, licence or attribution notices;
- attack, overload, probe or disrupt a relay, a host or another user’s Devices, including with denial-of-service traffic or automated abuse;
- misrepresent an affiliation with, or endorsement by, AirBridge, Diganta Dey or any platform vendor;
- operate the Software in safety-critical environments where a failure or delay could lead to death, personal injury, or severe environmental or property damage, such as medical devices, life-support systems, aviation, or nuclear facilities.
We may investigate suspected breaches and may stop providing services we operate, such as a relay or the Website, to anyone we reasonably believe is abusing them. We are not a law-enforcement body and cannot police your Devices.
17. Intellectual Property
The AirBridge name, wordmark, icon and logo, the design and content of the Website, the documentation, and the Software’s original code and assets are owned by Diganta Dey and the AirBridge contributors, and are protected by copyright and other laws. Your rights to use the Software come from the Licence, and your rights to use the name and marks extend only to factual, nominative references to AirBridge — for example, stating that your device or project works with AirBridge. You may not use the marks in a way that suggests sponsorship, endorsement or official status without written permission.
Your User Content remains yours, as described in Section 10. If you send us feedback, suggestions or bug reports, you grant us a non-exclusive, perpetual, royalty-free licence to use and act on them without obligation, compensation or confidentiality, except that we will handle personal data as described in the Privacy Policy.
18. Availability and Changes to the Service
AirBridge is developed in the open, and its official GitHub releases are provided free of charge; store distributions may be paid as described in Section 6. We do not promise any level of uptime, availability, support or response time, and there is no service-level agreement. The Website, downloads, releases, relays and features may change, be interrupted, or be withdrawn at any time, including because a third-party platform, store or dependency changes.
We may add, modify, deprecate or remove features, change system requirements, or stop distributing builds for a platform. Updates may be staged gradually. A relay is available only if you or someone else configures and runs one; we do not promise a relay will exist or remain reachable. Because there is no account, we cannot notify you individually about changes — check this page and the repository’s release notes. Nothing in these Terms obliges us to provide maintenance, updates or support, and nothing prevents you from continuing to run a version you already have, subject to the Licence.
19. Disclaimers
To the maximum extent permitted by applicable law, the Software, the Service and the Website are provided “as is” and “as available”, with all faults and without warranties of any kind, whether express, implied or statutory. We disclaim implied warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy, quiet enjoyment, and any warranty arising from a course of dealing or usage of trade.
We do not warrant that the Software will be uninterrupted, timely, error-free or free of harmful components; that every feature will work on every device, Android vendor build, operating-system version, network or browser; that a transfer, pairing or relay will always succeed; or that any defect will be corrected. Security features are designed to protect communications, but no software or network can guarantee absolute security, and this Software has not been independently audited.
Where data integrity checks are documented — for example SHA-256 verification before a received file is published — we aim to make them reliable, but they verify integrity, not the trustworthiness or safety of the content itself. Nothing in these Terms excludes or limits any warranty, guarantee or statutory right that cannot lawfully be excluded or limited where you live.
20. Limitation of Liability
To the maximum extent permitted by applicable law, we will not be liable for any indirect, incidental, special, exemplary, punitive or consequential damages, or for any loss of data, files, profits, revenue, business, goodwill, anticipated savings or device functionality, arising out of or relating to your use of, or inability to use, the Software, the Service or the Website — whether the claim is based on contract, tort (including negligence), strict liability or otherwise, and whether or not we were advised of the possibility of such loss.
To the same extent, our total aggregate liability for all claims relating to the Software, the Service or the Website will not exceed the greater of (a) the amount you have paid us for the Software in the twelve months before the event giving rise to the claim — which, for a copy obtained from the official GitHub releases, is zero, and for a paid store copy is the amount you paid for that copy — or (b) the minimum amount required by applicable law.
Nothing in these Terms limits or excludes liability for fraud or fraudulent misrepresentation, for wilful misconduct, for death or personal injury caused by negligence, or for any other liability that cannot lawfully be limited or excluded. Some jurisdictions do not allow the exclusion or limitation of certain damages, so parts of this section may not apply to you, and nothing here affects mandatory consumer rights you have where you live.
21. Indemnification
To the extent permitted by applicable law, you agree to indemnify and hold harmless Diganta Dey, the AirBridge contributors and the project’s licensors from and against third-party claims, actions, damages, losses, liabilities, costs and reasonable legal fees arising from: your breach of these Terms or the Licence; your User Content; your misuse of the Software or the Service; or your violation of any law or third-party right.
We will notify you of such a claim within a reasonable time, and you may participate in or, where appropriate, conduct the defence with counsel we reasonably accept, provided you do not settle in a way that admits fault by us without our written consent. We may also participate in the defence at our own cost. This obligation does not apply to the extent a claim results from our own wilful misconduct, or to the extent applicable consumer law says otherwise.
22. Termination
You may stop using AirBridge at any time by unpairing your Devices, uninstalling the Software and deleting any data it stored locally. Because there is no account, there is no account to close.
Your rights under these Terms and the Licence end automatically if you breach them — for example by using AirBridge commercially without consent, or by infringing the Licence’s restrictions. We may also stop operating anything we run ourselves, such as the Website or a relay, or stop distributing the Software, at any time.
Sections that by their nature should survive termination will continue to apply, including those on intellectual property, disclaimers, limitation of liability, indemnification, governing law and general provisions. Termination does not by itself entitle you to a refund: the official GitHub releases are free of charge, and a refund for a paid store copy is handled by the store you bought it from under that store’s policy.
23. Governing Law and Disputes
AirBridge does not designate a single governing law or an exclusive court for these Terms. The project is maintained by an individual, is distributed globally, and has not established a jurisdiction that it could fairly impose on every user, so it does not pretend to have one. Rather than name a forum it cannot support, this section records the following:
- Nothing in these Terms removes or limits any mandatory right or protection available to you under the law that applies where you live, including consumer-protection rights.
- Nothing in these Terms requires you to bring a claim in a particular court, or prevents you from bringing one before a court that has jurisdiction over the matter under applicable law.
- If you have a concern or a dispute, write to hello@airbridge.fyi first, so that we have a reasonable opportunity to resolve it informally.
- Where a court or other authority decides which law applies to a question, it will apply the rules that bind it; these Terms do not ask it to do otherwise.
This section is a decision not to impose a forum or a governing law through these Terms. It is not a waiver of any right you have, and it does not prevent the maintainer from agreeing a specific jurisdiction with you in writing if a dispute ever arises.
24. Changes to These Terms
We may update these Terms as AirBridge changes. When we do, we will publish the revised Terms on this page with a new version number and effective date, and we will describe material changes in plain language here or in the repository’s release notes. We cannot email you, because AirBridge has no account or mailing list.
Changes take effect on the date stated at the top of the page. If you continue to use AirBridge after that date, you accept the revised Terms. If you do not agree to a change, stop using AirBridge and uninstall it. Terms that applied when you used an earlier version continue to govern that earlier use.
25. Contact Information
AirBridge is maintained by Diganta Dey. For questions about these Terms, the Licence, permission for commercial or organisational use, or legal notices, email hello@airbridge.fyi.
- Source code, releases and licence: github.com/DigantaDey/AirBridge
- Bugs and feature requests: the repository’s issue tracker
- Security reports: the private process in SECURITY.md — please do not open a public issue
- Privacy questions: see the Privacy Policy
AirBridge does not publish a postal address, and none has been established for the project. Email is the established channel for formal legal notices and all other correspondence: hello@airbridge.fyi. Please allow a reasonable time for a reply.
26. General
- Entire agreement. These Terms, the Licence and the Privacy Policy are the entire agreement between you and us about AirBridge and replace any prior statements about it.
- Severability. If any provision is found unenforceable, it will be limited or removed to the minimum extent necessary, and the remaining provisions will stay in effect.
- No waiver. If we do not enforce a provision, that is not a waiver of our right to enforce it later.
- Assignment. You may not assign or transfer your rights under these Terms without our written consent. We may transfer our rights and obligations to a successor maintaining the project.
- No third-party beneficiaries. Except for the indemnified parties in Section 21, no one other than you and us has rights under these Terms.
- Events beyond our control. We are not responsible for delay or failure caused by events beyond our reasonable control, including network or platform outages.
- Headings and language. Headings are for navigation only. These Terms are written in English, and the English version governs if they are translated.
These Terms were last reviewed on 22 November 2026. If anything here is unclear, ask before you rely on it: hello@airbridge.fyi.