ASTRASDR PRIVACY POLICY MacFly Solutions Ltd Version 2 — Effective date: 1 November 2026 AstraSDR · MacFly Solutions Ltd Privacy Policy Version 2 · Effective date: 1 November 2026 · Development application and website Know what stays on your phone, what a receiver can see and what happens when you contact us. This policy is specific to AstraSDR. It covers local application data, remote receiver connections, optional identifiers and location, decoded material, exports, backups, website services and support. Download a plain-text copy of this policy (privacy-policy.txt) 1. Who is responsible MacFly Solutions Ltd, registered in Scotland under company number SC871379, operates astrasdr.com and develops AstraSDR. Our registered office is 7 Arnage Terrace, Aberdeen, Scotland, AB16 6XB, United Kingdom. In this policy, “we”, “us” and “our” mean MacFly Solutions Ltd. We are the controller for personal information we process for the AstraSDR functions we determine, this website, enquiries and application support. Independent receiver operators, map and data services, and your device or backup provider are responsible for their own processing. This policy explains those connections; it does not replace their privacy information. Privacy contact: support@astrasdr.com (mailto:support@astrasdr.com). You can also write to our registered office, marked “AstraSDR — Privacy”. 2. What this policy covers This policy covers visitors to astrasdr.com, people who contact us and users of the current Android development application. It also explains the handling of callsigns and other information obtained from received signals, receiver directories and DX feeds. AstraSDR is in active development and is not yet available for public download. The application currently has no online AstraSDR account, hosted personal logbook or Google sign-in. A local profile does not create an online account. We will update this policy before introducing materially different data handling. 3. Privacy at a glance Your profile, listening records, favourite receivers, frequency memories and saved images are stored locally by the current application. Remote receivers and external services receive connection information, including your IP address. Local storage does not mean that the application makes no network connections. KiwiSDR receives the generic identifier “AstraSDR” by default. Personal name or callsign sharing is a separate, off-by-default setting restricted to verified encrypted connections. Approximate location is optional. The receiver decoders use incoming receiver audio, not the phone microphone. Reports, log exports and shared images are sent only through destinations you choose. Review them before sharing. This website has no sign-up form, advertising tracker, embedded Facebook feed or analytics script. Ordinary hosting and email processing still apply. 4. Information, purposes and destinations Data handling in the current development version Information | Why it is used | Where it goes | Local profile: name or callsign, preferences | Personalise the interface and remember your settings. | App storage. An identifier goes to a Kiwi operator only if optional sharing is enabled and its connection checks pass. | Receiver choice, tuned frequency, mode and protocol requests | Connect, authenticate where required, tune and receive audio or spectrum data. | The receiver you use. Status checks can also contact other directory entries. | Connection IP, request time, browser or client headers | Deliver website pages, receiver sessions, maps and feeds; operate and protect those services. | Website host, contacted receivers and the relevant external service. | Approximate device location | Provide optional map and station-distance features. | Processed on the device by the current app. Map providers receive requested tile areas separately. | Decoded messages, station callsigns, locators and DX spots | Display received activity, station information and source reports. | Received from radio signals or external feeds; processed in the app. Lookup sites receive a callsign when you open a corresponding link. | SWL entries, frequency memories and favourites | Keep reception notes and return to useful tuning points. | Device storage; supported Android backup or device transfer; destinations you choose for exports. | SSTV images and weather fax charts | Show and save received pictures. | App storage or a chosen export/share destination. Weather fax PNGs can contain reception metadata. | Support email and diagnostic attachments | Respond to enquiries and investigate faults. | Our support mailbox and email service providers, when you send them. | Most data comes from your choices and entries, your device, the receivers you contact or the external information sources you use. A callsign or station record can identify a person even when it is publicly broadcast or listed elsewhere. We do not treat all radio-related information as anonymous. 5. Website, cookies and Facebook The supplied website code does not set cookies, use local storage, run third-party analytics or load advertising or social-media tracking pixels. Fonts, graphics, style files and scripts are served from the website itself. It does not collect beta applications or newsletter subscriptions. Hostinger hosts the website. Delivering a page and protecting the service can involve IP addresses, requested URLs, timestamps, browser information and access, error or security logs. These are technical service records, separate from a marketing analytics profile. Hostinger may also process operational information under its own service terms. Facebook is an ordinary external link. Simply reading this website does not embed a Facebook feed or load a Facebook pixel supplied by us. If you follow the link, Meta/Facebook processes information under its own policy, including any logged-in account or cookies it uses. The same principle applies to other external links. If hosting settings or a later website change introduce additional tracking or optional cookies, the relevant privacy information and any required choices must be provided before that tracking operates. 6. Local storage, received audio and image metadata The application stores profile details, receiver preferences, manual inactive marks, favourites, frequency memories, SWL records, caches and supported saved images on your device. SWL entries can contain station callsigns, frequencies, modes, dates, receiver details and free-text notes. Decoded radio messages and DX spot comments may contain information about other people. Audio received from a remote receiver is processed for playback and, when you start a supported decoder, for FT8, SSTV or Weather Fax decoding. The current decoders do not require microphone or camera access. This is not a claim that the remote receiver's operator keeps no logs or recordings. Weather fax images saved by the application can contain PNG metadata including reception and save times, receiver name and URL, dial and assigned frequency where known, decoder settings, image dimensions, correction settings and complete/partial status. When you share that PNG, its metadata may travel with it. Review the image and its source details before sharing. The current application does not automatically upload a personal logbook or saved-image collection to a MacFly Solutions Ltd backend. This does not prevent exports, Android backups or third-party connection logging described elsewhere in this policy. 7. Receiver connections and personal identifiers AstraSDR contacts independently operated receivers directly. An operator can receive your IP address, session timing, tuning and protocol requests, and any access information required for its service. Receiver discovery and availability checks may contact listed receivers even when they are not your current listening receiver. The default Kiwi identifier is “AstraSDR”. Entering a name or callsign in your local profile does not enable personal identifier sharing. The optional Receiver Identity setting is off by default, including on supported upgrades. Saving an explicit opt-in enables selection of an override, callsign or first name, with a preview of the identifier. The current Kiwi implementation sends a personal identifier only after successful authentication on the actual connection with a verified TLS handshake and final encrypted URL. HTTP, unencrypted WebSocket and unverified connections use the generic identifier even if sharing was enabled. The waterfall connection also uses a generic identifier. Operators may display identifiers to other listeners and retain their own session or access logs. Turning sharing off replaces the identifier on the current eligible session but cannot retrieve information already received, displayed, recorded or copied by another party. Not all receiver or directory traffic is encrypted. Legacy HTTP or WebSocket services can expose traffic to others on the network. A generic identifier does not hide your IP address. Do not assume that every receiver connection is private or anonymous. 8. Optional location and Android permissions If you grant approximate location permission, the current application uses your position for optional map and distance features, such as estimates for received FT8 stations. It does not intentionally send the device coordinates to a MacFly Solutions Ltd server. Map tile requests reveal the tile areas you view, along with your IP address and technical request information, to the map provider. You can refuse or revoke location access in Android Settings → Apps → AstraSDR → Permissions. Listening can be used without it, while location-dependent features may be unavailable. The current manifest does not request background location permission. Internet and network-state access support receivers and feeds. Foreground media playback and notification permissions support audio playback and its controls. File exports use Android's document picker or sharing interface to give access to the destination you select; the app does not need blanket access to all your personal files for these exports. An Android permission is a technical access control. Where processing relies on consent, you can also withdraw your choice as described in this policy. Refusing optional functions does not require you to stop using the unrelated listening functions. 9. External information sources and updates The following services can be contacted when their features run. These are destinations for application requests, not third-party scripts embedded in this website. Receiver directories and independent KiwiSDR/OpenWebRX operators: discovery, status and listening requests. The current Kiwi directory source includes rx.linkfanel.net. OpenStreetMap tile services: map tiles for the viewed area. MapLibre is the mapping software; a tile provider is the network destination. HamQTH: DX spot data. The current DX screen requests updates while visible and resumed; its filters are applied locally. It does not submit spots. HAMQSL, NOAA SWPC and NASA/SDO: solar, propagation and image requests. Cached or stale information is distinguished from a successful refresh. country-files.com: country/prefix information used by the application. QRZ and other source/reference websites: opened when you follow an external reference. A callsign in a lookup URL is disclosed to the lookup destination. Manual application-update tools may open an external browser or Google Drive. A configured version-manifest check contacts its configured endpoint when requested; the current inspected build has no manifest URL configured. The current application does not silently install an APK or require Google OAuth access to your private Drive files. Google or your browser may still process an external page visit under their own policies. Independent services determine their own access rules, privacy practices and retention. They are not all processors acting on our instructions. Source credits do not establish a data-processing agreement or a guarantee about a receiver operator. 10. Support, diagnostic reports and sharing When you email us, we receive your email address, message and attachments, together with normal email routing information. We use them to answer your request, investigate a reported issue and manage the conversation. We do not add support contacts to a marketing list. The Report a Problem and log-sharing functions prepare material for an external email or sharing application. Preparing a report is not sending it. A diagnostic attachment may include the app version, Android version, protocol, receiver address, timestamps and bounded connection or error events. Review both the message and its attachments before sending. Do not send passwords, access tokens or unnecessary personal information. A CSV/ADIF log export or shared image may include information about you, stations or other people. The destination you choose, including a cloud drive or social platform, handles the exported copy under its own rules. Removing an item from AstraSDR does not remove those separate copies. 11. Purposes and lawful bases Where UK data protection law applies to processing for which we are responsible, we use the following bases. The basis depends on the actual purpose, not simply on whether a function is called an application feature. Operating and securing this website; troubleshooting and answering ordinary enquiries: legitimate interests in maintaining a reliable service and responding to people who contact us (Article 6(1)(f)). We limit information to what is reasonably needed for that purpose. User-requested local listening and logbook functions: legitimate interests in providing the expected functionality, with local processing and your controls over entries, receiver choices and exports. This does not establish a lawful basis for an independent operator's separate uses. Optional personal receiver-identity sharing and optional device-location processing: your consent for these optional uses (Article 6(1)(a)), implemented through the relevant application choice and Android permission where needed. Withdrawal affects future processing; it does not make earlier lawful processing unlawful. Responding to applicable data-protection requests and binding legal requirements: compliance with a legal obligation (Article 6(1)(c)). Establishing, exercising or defending legal claims: legitimate interests where necessary, subject to applicable safeguards and any additional requirements for the information concerned. Providing an email address or diagnostic report is voluntary. Without enough relevant information we may not be able to respond or investigate a particular issue. We do not use personal information for solely automated decisions producing legal or similarly significant effects, or for behavioural advertising profiling, in the current service. 12. Who may receive information Recipients depend on your use: the receiver and information services described above; Hostinger for website hosting; our email service provider for correspondence; your Android/device backup provider; and destinations you select for a lookup, export or share. Our support-data policy requires access within our organisation to be limited to people who need it for the enquiry, administration or security. Professional advisers, regulators, courts or law-enforcement bodies may receive information where disclosure is necessary and lawful, including for a binding legal requirement or a legal claim. We do not sell personal information or provide your support messages for advertising. Public radio feeds or DX data displayed in the app are not an invitation to publish private details about an operator or listener. 13. How long information is kept Ordinary support emails and diagnostic attachments: retained while the issue is open, then for six months after the enquiry is closed, after which we delete or anonymise them. A reopened matter is treated as open until resolved. Legal, security or dispute exceptions: relevant information may be retained beyond that period when necessary for an identified legal obligation, active security investigation or legal claim. Retention is limited to the information needed and the relevant obligation, investigation or claim; ordinary support history is not kept indefinitely by default. Local app records and saved images: remain until you remove them using available app or Android controls. There is no automatic expiry for your saved weather fax gallery. Caches and temporary diagnostics may be replaced or cleared by the app or Android. Exports and backups: remain until removed from the destination or expired under the backup provider's rules. Android backup or device transfer may include supported receiver settings, favourites, frequency memories and SWL entries; downloaded caches are excluded by the inspected backup rules. Website host and independent-service logs: apply the hosting service's configured retention or the independent operator's schedule. We do not assign an invented universal period to records controlled by unrelated operators. Contact us for information about website records processed for us; contact an independent operator for its own logs. We apply the six-month schedule to ordinary support records we control, including copies kept for support purposes. Where a service's recoverable backup prevents immediate physical removal, the retained copy must remain protected and out of ordinary use until the provider's backup cycle removes it. The exact hosting-log retention and provider-backup expiry settings have not yet been confirmed for this website deployment; application code alone cannot establish those periods. 14. Your controls and deletion requests Local records: use the relevant edit, clear or delete option where available. To remove the app's local storage as a whole, use Android Settings → Apps → AstraSDR → Storage → Clear storage, or uninstall the app. This removes local settings and records and may not be reversible. Files and backups: separately remove exported CSV/ADIF files, saved PNG copies and cloud backups from their chosen locations. They are not erased by clearing the original app record. Receiver identity and location: disable Receiver Identity sharing in the app and revoke Android location permission to stop future optional use. This cannot recall a previously disclosed identifier or third-party record. Information held by us: email support@astrasdr.com (mailto:support@astrasdr.com?subject=AstraSDR%20privacy%20request), explain your request and identify the relevant correspondence if you can. Do not include a password or government identity document unless we explain a proportionate need for verification through an appropriate channel. There is no online AstraSDR account to close in the current version. We cannot remotely erase your phone, a recipient's independent copy or an unrelated receiver operator's logs. We will explain any lawful reason for retaining information rather than simply refusing without explanation. 15. International processing and safeguards Receivers are located in different countries. Choosing a receiver or external service can send requests and connection information outside the UK. Hosting, email and Android-backup services may also use international infrastructure; the relevant locations depend on the contracted service and its configuration. For restricted transfers for which we are responsible, UK data-protection requirements apply. The appropriate route depends on the recipient and destination, for example an applicable adequacy regulation or contractual safeguards such as the UK International Data Transfer Agreement or UK Addendum, with any required assessment and supplementary measures. This policy does not claim that a particular mechanism covers every independent receiver or that every overseas service has equivalent protection. You may ask us which providers handle information held for us, the relevant processing locations and how to obtain information about applicable safeguards. Independent operators publish or provide their own transfer information. 16. Security and limitations Our security policy requires restricted administrative access to website and support information and appropriate use of the host and email provider's access controls. These requirements are not a claim that this policy preparation included an audit of the live hosting or mailbox settings. The public website is intended to be served over HTTPS. Local app storage and file access are subject to Android's application and permission controls. Receiver encryption is connection-dependent. Optional personal identifiers are restricted to verified encrypted Kiwi connections, but legacy services may still use unencrypted transport for other traffic. We do not promise complete anonymity, universal encryption, error-free software or absolute security. Avoid placing sensitive personal details in a receiver identifier, log note, public post or unnecessary report attachment. Security measures described here are proportionate controls, not a certification of every receiver operator or hosting configuration. 17. Your rights and complaints Subject to applicable law and the circumstances, you can request access, correction, erasure, restriction or portability of your personal information. You can object to processing based on legitimate interests and withdraw consent for optional processing without affecting earlier lawful processing. Contact support@astrasdr.com (mailto:support@astrasdr.com). We normally respond within one month. Where the law permits an extension because of complexity or the number of requests, we will explain it within the original response period. We may ask for proportionate information to confirm identity or clarify the records involved. Rights can be limited by lawful exemptions; we will explain an applicable limitation. You can complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint/ (https://ico.org.uk/make-a-complaint/), or another competent supervisory authority where applicable. You do not have to contact us first, although we welcome the chance to resolve your concern. 18. Children, beta registration and policy updates This website does not currently collect beta registrations, run a children's account system or ask for age information. Avoid sending unnecessary information about a child or another person in feedback, diagnostic notes or attachments. Contact us if you believe we have received such information inappropriately. If we introduce beta registration, newsletters, online accounts, advertising, new analytics or a materially different data flow, we will provide the relevant information and obtain consent where required before the new processing starts. A Facebook announcement alone does not enrol you in an email list. The date and version at the top identify this policy. Check it again before using a later release because development features and providers may change. ↑ Back to top (#top)