iSCSI4NAS
Join the beta

Privacy Notice for iSCSI4NAS Home Edition

This notice applies to iSCSI4NAS Home Edition from the Mac App Store, to the beta through TestFlight and to the feedback service. Visits to our website are covered by the Website Privacy Notice.

Last updated: 5 November 2026 · Document version: 2026-11-05.1

Advertising and tracking

The app contains no advertising and does not incorporate any frameworks, SDKs or other tools for advertising, usage analytics or tracking. We do not track your use across other apps or websites. The feedback service uses device and security identifiers for approval, case association and abuse prevention, as described in sections 3 and 5.

1. Controller and contact

Aviontex GmbH, Bodenseestraße 2, 86343 Königsbrunn, Germany, is the controller for the processing by Aviontex described here. Full provider details are available in the app under “About iSCSI4NAS > Imprint” and in the imprint on our website.

Privacy questions and requests: privacy@iscsi4nas.de
General enquiries: hello@iscsi4nas.de
Support: support@iscsi4nas.de
Support during the beta: beta-support@iscsi4nas.de

2. On your Mac and in the local network

The app processes target addresses, iSCSI names (IQNs), connection and authentication settings, NAS and LUN properties, volume information and technical states. Profiles, settings, feedback drafts and the local report history are stored on your Mac. Saved CHAP secrets, the feedback identifier generated after the Bug Reporter is switched on and the private device key are stored in this Mac’s macOS Keychain. The app does not synchronise these items with iCloud.

Optional iCloud backup. You can switch on an iCloud backup under “Settings”. It is switched off by default. When it is on, the app places a backup of your target profiles in a Keychain item that macOS synchronises through iCloud Keychain. If you also switch on “Include credentials”, this backup also contains CHAP usernames and CHAP secrets. This option is also switched off by default. The feedback identifier and the private device key are not part of the backup. The backup is made at your request to provide the requested function under Article 6(1)(b) GDPR. Apple processes the synchronisation through iCloud under its privacy information. This does not give Aviontex access to the backup.

When discovering devices and establishing iSCSI connections, the app communicates with devices and endpoints in the networks you use. Services and connection states are automatically advertised on the local network through Bonjour. Recipients are other devices on the same local network, including devices you do not control. In particular, they may receive target IQNs, LUN identifiers, an identifier for the running Core instance and session, publication and reservation status. The local hostname used by the system may also become visible and may contain a device name you have assigned.

Bonjour coordination starts automatically with the Core (the app’s background process) and is a mandatory part of access protection. Before making a LUN available for writing, the app uses this coordination to check whether other initiators are advertising write access to the same LUN. A detected conflict or a failure of this detection prevents write access from being enabled. Coordination remains mandatory and active while connections are in use, ensuring continuous conflict checks. Advertisements for existing iSCSI sessions and LUNs made available for writing are updated automatically and withdrawn when the respective state no longer applies. Discovery of other initiators continues for as long as the Core is active. Closing the user interface does not end these processes. Aviontex GmbH is the controller for the app’s processing of connection and coordination data described here. The requested storage functions are provided on the basis of Article 6(1)(b) GDPR. Access conflicts are detected and prevented on the basis of Article 6(1)(f) GDPR. Our legitimate interest is preventing data loss and disruption to storage operations. This processing takes place on your Mac and in your networks. Bonjour advertisements are distributed exclusively within the local network.

Local diagnostics and technical logs may contain device names, network addresses, target identifiers and error details. They are not automatically uploaded to Aviontex. Local settings and saved reports are retained until removed through the respective app or system functions. Technical logs are rotated according to size and app launches. This local processing does not give Aviontex access to your NAS file contents, CHAP secrets or local logs. Transfers to Aviontex are described separately in the following sections.

3. Participation in and approval for the Bug Reporter

The Bug Reporter is switched off by default. When you switch it on under “Settings > General > Feedback”, the app generates its own random feedback identifier and stores it in the macOS Keychain. It calculates a SHA-256 hash of this identifier to use as the registration key. It also generates a device key pair for authentication. It shows you the registration key and an input field for your application. This preparation takes place exclusively on your Mac. The connection to the feedback service begins only when you submit the application. Please limit your application text to experience relevant to your participation and do not include particularly sensitive information.

Only when you explicitly submit the application does the app transmit your application text of up to 4,000 characters, the registration key and the public device key over HTTPS to bugreport.iscsi4nas.com. The underlying feedback identifier and the private device key remain in the macOS Keychain. The server stores the public key for device authentication. Aviontex personally decides whether to grant approval. Submitting an application does not grant access to the Reporter. If you contact us separately by email, section 7 applies to that message.

After you have initiated submission of an application, the enabled function checks at app startup whether Aviontex has approved your Mac. A confirmed positive or negative result is stored locally for 24 hours. No further approval check is made during that period. After that, another check is made at the next app startup. The check does not itself grant approval. Only after approval is confirmed do the reporting functions become available under “Settings > Feedback” and the Reporter’s further checks and status requests begin. Reports are transmitted only when you explicitly submit them. Changes to device approval are detected at the next approval check. An explicit access denial from the server blocks the Reporter immediately.

The registration key is a stable pseudonymous identifier for the feedback registration. The app reuses the saved feedback identifier on subsequent launches and calculates the same registration key from it. It associates the application, approval, reports, replies and processing statuses with this registration. For device authentication, the app signs requests with the private device key. The server verifies the signature using the public device key. If the feedback identifier or the private device key is lost, the app can no longer use the existing registration. It does not automatically create a replacement registration. A new registration or a subsequent key change requires individual approval by Aviontex again. A personal user account, a login or additional information such as your name, email address or a password is not required.

Participation is voluntary. The Bug Reporter cannot be used without an application and individual approval. The other app functions remain available. You can switch the Reporter off and request deletion of its data as described in section 6. To participate again, switch it back on and apply for individual approval again. This does not restore deleted cases. We use the application and device association to assess your participation and technically enforce approval. The legal basis is Article 6(1)(f) GDPR. Our legitimate interest is to limit the support channel to the selected participants and protect it against unauthorised use.

4. Feedback, feature requests and support

Reports, messages and attachments are transmitted only when you explicitly submit them. You can submit bug reports, feature requests, questions and feedback on compatibility and performance.

A submission contains your text and category, device and case references and technical environment information: macOS version, app and bundled driver versions, source code revision identifier, build configuration, processor model and architecture. Selected images are re-encoded. Original file paths and image metadata are not transmitted. Visible image contents are preserved.

You can select NAS and LUN information separately and review it before attaching it. This uses existing observations, such as manufacturer, model, firmware, capacity, block size, partition and file system detection and connection and mount status. Target and LUN references are derived for the individual case. The structured attachment has no dedicated fields for original IQNs, IP addresses, serial numbers, volume names or mount paths. Preparing it does not establish an additional NAS connection or read file contents.

Please review text and images before submitting them. In particular, remove passwords, access keys, private files, names and contact details of people not involved and health information or other particularly sensitive details. Removing image metadata does not remove information visible in the image.

We use submissions to handle your requests, provide support, analyse errors and compatibility and improve the product. Where processing is necessary to provide contractually required support or error resolution, the legal basis is Article 6(1)(b) GDPR. Beyond this, we handle feature requests, general feedback and compatibility and performance enquiries on the basis of Article 6(1)(f) GDPR. Our legitimate interest is handling these requests and improving the software and its stability.

Related cases may be linked to a common issue. Other participants see only shared information supplied by the team, the status and the participant count, not your device identifier, individual reports, messages or attachments. General technical findings independent of people and devices may be retained.

We disclose report contents to NAS or storage manufacturers only with your separate consent for the individual case under Article 6(1)(a) GDPR. We first identify the recipient, the data concerned and, where applicable, the basis for a transfer outside the European Economic Area.

5. Hosting, security and recipients

Access to feedback is granted to people at Aviontex authorised to handle it and administer the service. The service is hosted by ALL-INKL.COM (Neue Medien Münnich), proprietor René Münnich, Hauptstraße 68, 02742 Friedersdorf, Germany. ALL-INKL.COM processes feedback-service data on our behalf and under our documented instructions as a processor under Article 28 GDPR. Applications, reports, messages, NAS information and attachments are stored in the database. Requests use HTTPS.

According to its privacy information, ALL-INKL.COM uses Neue Medien Münnich GmbH, Bautzener Str. 56, 02742 Neusalza-Spremberg, as an additional service provider for administrative and technical services, support and data centre services. ALL-INKL.COM and the GmbH have a contract governing this processing on its behalf. The GmbH’s authorised staff may access the data required for these purposes.

When you make a request, the server necessarily receives your IP address and request information. For abuse prevention, the service calculates a keyed IP hash. For IPv6, it uses the /64 network prefix. Security records in the database may contain pseudonymous device or source references, timestamps, request results and case references. This processing serves to protect against unauthorised access and abuse and to analyse errors under Article 6(1)(f) GDPR.

Access logs with truncated IP addresses and access statistics generated from them are enabled at the hosting provider. Logs may also include the time, requested path and client information. We do not automatically treat truncated addresses and technical identifiers as anonymous data. These analyses support technical operation and fault detection under Article 6(1)(f) GDPR.

Case notifications to the responsible team contain only the case identifier, category and a protected service link. Separate security alerts may include an error or blocking reason, a pseudonymous device or access reference and a shortened IP hash.

Aviontex and the processors it uses process feedback-service data exclusively in Germany.

Personal data breaches

A personal data breach is subject to the notification duties in Articles 33 and 34 GDPR. Where notification is required, we notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of the breach. Where a breach is likely to pose a high risk to your rights and freedoms, we inform you without undue delay in accordance with Article 34 GDPR. Processors are required to notify us without undue delay of personal data breaches of which they become aware.

6. Retention and deletion

Registration and cases

During normal operation, the application text stored on the server is permanently deleted in the next daily deletion run, no later than 24 hours after receipt of the application. This also applies if no decision has yet been made on the application. If approval or rejection occurs before then, the application text is immediately marked for deletion and blocked from access. Restorations are subject to the exception described under “Backup and restoration”. The access restrictions described there remain in place.

The technical registration, including the registration key, public device key, processing status and device approval, is retained until the registration is deleted or the feedback service is permanently discontinued. It is used to associate approval checks with the registration, control access and verify your entitlement to request deletion. This also applies after rejection. The application text is deleted independently within the period stated above. You can use the deactivation function to request deletion of the registration together with the associated cases. Administrative withdrawal of approval alone blocks access. It does not automatically delete existing cases. The following retention periods continue to apply to them.

For open or deferred cases, a first reminder is issued 30 days after the last message you submitted for that case. A second reminder follows after another 30 days. If the case remains open or deferred, it is automatically deleted seven days after the second reminder. Each new message you submit for that case restarts this period. Merely opening or reading a case and replies from the team do not restart it. After the next successful synchronisation, the reminders appear in the respective case under “Settings > Feedback > My Reports” and are also displayed in the web administration interface.

Closed cases are deleted 30 days after case closure. For grouped cases, the closure of the common issue determines the start of this period.

Deletion at your request

If you switch the Bug Reporter off before the first attempt to submit an application, the app removes the Reporter data prepared exclusively on your Mac, the feedback identifier and the private device key. No internet connection is required for this.

From the first submission attempt onwards, switching the Reporter off under “Settings > General > Feedback” causes the app to send an online, device-authenticated request to delete your application, registration and all associated reports, messages, NAS data and attachments. The affected records are marked for deletion and the deletion request is also recorded in a separate deletion log. This also applies to deletions initiated by administrators. Once the server confirms the request, the data is blocked from normal access through the app, by the team and by internal systems. During normal operation, final deletion from the active database takes place in the next daily deletion run within 24 hours. Restorations are subject to the exception described below, with the access restriction remaining in place. The retention period for closed cases does not delay this deletion.

The app waits for server confirmation even if delivery of the application is uncertain. Only then does it remove its local Reporter data, the feedback identifier and the private device key and confirm that the Reporter is off. Without a connection or if an error occurs, deactivation remains pending. The app retains the data and credentials needed to retry. It does not report deactivation as complete in that situation. Further Reporter activity remains blocked until completion.

At the next successful case synchronisation, the server tells the app which cases have been marked for deletion or already deleted. For this purpose, it stores only a verification value derived from the registration key, case identifier and original access token for each case. The app uses its existing access token for this request. After confirmation, it removes the locally stored case contents, attachments and access token. Only the case identifier and the status “Deleted on server” remain locally. This entry is not queried again. The server-side verification value is retained until the feedback service is permanently discontinued and is then deleted with its database. This allows devices reconnecting after a long period offline to recognise the deletion. The deletion periods for report contents and attachments apply independently.

Disabling the Reporter does not end your use of the app. Uninstalling the app alone, however, does not delete data already submitted to the feedback service.

Backup and restoration

Aviontex’s internal backup: Aviontex keeps exactly one backup of the feedback service’s database. It is created once a day after due deletions have been carried out and replaces the previous backup.

ALL-INKL creates its own system backups as part of its hosting operations. ALL-INKL.COM describes database backups from the previous day, approximately five to eight days earlier and approximately nine to twelve days earlier. For webspace files, it normally keeps two backups aged up to two and four weeks respectively. These additional backups follow the rotation intervals described by the provider. Details: ALL-INKL backup information.

Whenever a backup is restored, the database state is checked against the current, separately maintained deletion log before the service is made available again. The current log and its verification key are preserved during this process. Application texts marked for deletion or whose deletion time has been reached do not become accessible again as a result of restoration. They are permanently removed no later than the next daily deletion run. Device and case data marked for deletion remain blocked and are permanently removed in the next daily deletion run. For technical reasons, restoration may delay final removal by up to a further 24 hours. During this time, the affected data remain invisible and blocked from normal access through the service. If reconciliation fails or a backup is too old to reconcile safely, normal access to the service remains technically blocked. The log contains pseudonymous device, case, application and operation references and deletion-request and due times. Individual entries are removed only after our sole internal backup has been verified to contain the cleaned state and the previous backup has been replaced. Even after the deletion log is cleaned up, database states that are too old or inconsistent remain blocked if they cannot be reconciled safely. This procedure serves safe restoration and enforcement of deletions under Article 6(1)(f) GDPR.

Security and operational data

Separately delivered team notifications and security alerts are removed once the related case handling or investigation of the specific security incident is complete and they are no longer needed for it. The app’s deletion function cannot recall these emails.

7. Individual approval and support outside the app

Our email communication is also handled through ALL-INKL.COM in Germany. ALL-INKL.COM processes these data on our behalf under Article 28 GDPR, as described in section 5. Access is granted to the people at Aviontex responsible for handling the enquiry.

If you contact us outside the app for approval or support, we process the information you provide, such as your sender address, message, registration key and attachments. This correspondence is processed separately from feedback submitted through the app.

The legal basis is Article 6(1)(b) GDPR for necessary contractual support. Otherwise, Article 6(1)(f) GDPR applies to handling your enquiry and managing individually granted approvals. Emails for device approval, including the registration key provided, are deleted after the approval decision. In addition, these emails are cleared out daily. They therefore remain in active email storage for no more than 24 hours, even if no decision has yet been made. If the hosting provider creates a mailbox backup during this period, any copies it contains are overwritten as those backups rotate. Correspondence relating to support enquiries is deleted once the enquiry has been fully answered and the necessary follow-up questions have been resolved. Where individual support messages are subject to statutory retention requirements or are needed to establish, exercise or defend legal claims, only the part necessary for that purpose is retained for longer. The Bug Reporter’s deletion function does not cover separately sent messages. You can also request deletion through our privacy contact.

8. Apple, the App Store, TestFlight and update notifications

Update notifications, downloads and installation of new versions of this edition are handled through the Mac App Store. You can control whether updates are installed automatically in the App Store settings. Apple’s privacy notices apply to distribution, purchases and updates handled by Apple. Further information: App updates on Mac.

We provide beta versions through Apple's TestFlight. Apple's privacy notices apply to participation through TestFlight. Apple provides us with information about testers. If you are invited by email, this includes your name and email address. It also includes information about installations and sessions, crash reports and feedback with screenshots that you submit in TestFlight. We use this information to run the beta test and to analyse errors under Article 6(1)(f) GDPR. Our legitimate interest is a working and stable beta test. We delete extracts that we store ourselves after the related investigation is complete. Further information: Apple's Privacy Policy.

In macOS, you control the sharing of analytics and crash information with Apple and app developers under “Privacy & Security > Analytics & Improvements”. This may include hardware and software details, operating system and app versions and technical error and usage information. If you enable sharing with developers, Apple may provide us with crash and analytics data relevant to our app. Apple describes this sharing as not personally identifying. This transfer channel is independent of the Bug Reporter.

Apple is responsible for its own collection and processing and the associated international transfers. This processing may also take place in the United States. Apple’s Privacy Policy describes recipients, safeguards for international transfers and retention. Further details are provided in its Mac analytics information. If we receive such information, Aviontex processes it as a controller in its own right for error analysis and product improvement. Where the information provided contains personal data, Article 6(1)(f) GDPR applies to our processing. We delete personal-data extracts that we store ourselves after the related investigation is complete.

9. Your rights

Subject to the applicable GDPR conditions, you have rights of access, rectification, erasure, restriction of processing and data portability. You may withdraw consent at any time with effect for the future. This does not affect the lawfulness of earlier processing. You may complain to a data protection supervisory authority, in particular the Bavarian State Office for Data Protection Supervision (BayLDA).

Your right to object

You may object at any time, on grounds relating to your particular situation, to processing based on Article 6(1)(f) GDPR. We will then stop processing the data concerned unless we demonstrate compelling legitimate grounds overriding your interests, rights and freedoms or the processing serves the establishment, exercise or defence of legal claims.

For objections and other privacy requests, contact privacy@iscsi4nas.de. We need sufficient information, such as a case identifier or the registration key displayed in the app, to associate your Bug Reporter data with you. The case identifier is displayed with a copy function after submission and is available for saved cases under “Settings > Feedback > My Reports”. If we cannot establish a sufficient association, we cannot provide access to those data or delete them at your request. We will inform you of this. If we have reasonable doubts about your entitlement to make the request, we will ask for appropriate verification.

The service uses automatic security checks against abuse. You can ask us to review an incorrect access block. We do not use the described data for advertising profiling or automated decisions producing legal or similarly significant effects under Article 22 GDPR.