Release checklist: Before App Store submission, verify this page against the exact production build, backend behavior and every third-party SDK. App Store Connect disclosures must match actual data practices.
NodeLinker is designed for nearby communication and may request Local Network/Bonjour discovery, microphone, camera/flash and notification access only when related features are used. Location access is not required for the current nearby workflow.
Permissions
Depending on the feature used, NodeLinker may request Local Network/Bonjour discovery, microphone, camera/flash and notification access. Permissions should be requested only when the related nearby-chat, walkie-talkie or Morse feature is used. Location access is not required for the current nearby workflow, and the final permission set must match the shipping build.
Data minimization
Our product goal is to request and process only information needed for the feature the user chooses to use. Permission prompts should appear in context and explain why access is needed.
Third-party services
If analytics, crash reporting, AI services, cloud storage, advertising or other third-party SDKs are included in a production build, their data practices must be evaluated and reflected in this policy and in App Store Connect before release.
Data deletion and privacy requests
If the released version of NodeLinker creates an account or stores server-side user data, the final product must provide the appropriate account/data deletion path. Users may also visit our Privacy Choices page or contact us.
Security
We use reasonable technical and organizational measures appropriate to the services we operate. No method of storage or transmission can be guaranteed to be completely secure.
Contact
Questions about NodeLinker privacy can be sent to info@safeandsecurefamily.com.