Effective Date: 2026-11-12
Niroga is a stage formation and rehearsal planning app for small teams. It helps users create local rehearsal plans, arrange performer positions, review walking paths, add reference images, record rehearsal notes, and save movement sheets. This Data Privacy Policy explains what information may be handled when you use Niroga, how that information is used, and the choices you have.
The native rehearsal tools store plans, performer details, stage layouts, reference images, voice cues, notes, versions and reports on your device. Startup and authentication are separate network operations: identifiers and technical information are sent to the application service as described in Section I. Exported images, device backups and content you send to another service are separate copies governed by your choices and the relevant service.
Niroga does not perform facial recognition, does not conduct biometric analysis, and does not create, store, or use face templates, faceprints, biometric identifiers, or biometric profiles. If you add a stage reference photo or other image that happens to include a person’s face, Niroga treats that image only as user-provided visual content for rehearsal reference.
The native image tools do not identify people from images, compare faces or infer identity, emotion, health or age. They process images to display, rotate, scale, preview or export your chosen reference material. Local image files and caches are subject to app and operating-system storage behavior; no immediate or fixed-time deletion of every temporary copy is promised.
Niroga keeps rehearsal content in the app’s local Core Data store and Application Support directory, uses encryption for the saved rehearsal archive, and relies on device and operating-system protections. Content is processed locally for editing, playback, analysis and report generation. If you independently email us for support, the information you choose to send is handled to respond to that request.
No method of storage or transmission is completely risk-free. You are responsible for protecting access to your device, using device passcodes or biometric unlock settings provided by your operating system, and being careful when exporting rehearsal reports, images, or other files to third-party apps or services.
Local storage and migration: Niroga uses device preferences for local settings, legacy rehearsal migration, a cached device identifier and a session token. The device identifier is also retained in iOS Keychain and may survive app removal or reinstallation. Photos and voice recordings are stored as separate local files. Removing local rehearsal records does not automatically erase Keychain entries, server-side records, exported files or backups.
Local rehearsal information is used for editing, playback, reports, drafts and saved versions. The startup service processes the device identifier and request metadata to initialize the service, establish a session, associate requests with the same device and deliver configuration. Language, region and time-zone settings accompany those requests. Support information you voluntarily email is used to respond to your request.
We do not use your rehearsal content for advertising. We do not use your information to build advertising profiles or behavioral profiles. We do not sell your personal information or user-generated content. We also do not use your plans, reference photos, voice cues, or rehearsal markers to train advertising systems or to target promotions.
These optional features use device permissions or the system photo picker only when you choose to use the relevant feature. Where iOS requires permission, access begins only after you grant it. Declining a permission limits the related feature; it does not prevent you from using the other local planning tools.
Camera: When you choose to take a stage reference photo, Niroga requests camera access if it has not already been granted. The camera is used to capture the reference image you choose to add. The image is processed and stored in the app on your device, without an automatic upload to us. If you deny camera access, you cannot take a new reference photo in the app, but you can still choose an image through the system photo picker.
Microphone: When you start recording a rehearsal voice cue, Niroga requests microphone access and begins recording only if permission is granted. Recordings are saved locally for playback with your rehearsal plan and are not automatically sent to us. If you deny microphone access, you cannot record a new voice cue; existing saved recordings are kept.
Adding images to Photos: When you confirm that you want to save generated rehearsal reports or individual movement sheets to Photos, Niroga requests permission to add images to your photo library. This is add-only access and does not grant Niroga access to read your entire library. If you decline, the report preview remains available in the app so you can try saving again after changing your permission settings.
Choosing existing photos: Importing stage references uses the system photo picker. Niroga receives only the images you select and creates local copies for your rehearsal plan; this does not require full photo-library read access. Cancelling the picker does not import a new image and leaves existing reference images unchanged.
Changing your choices: You can review or revoke camera, microphone and Photos add-only permissions in your device's Settings, where available. Revoking permission prevents future access under that permission; it does not automatically delete content already saved. You can remove reference images and voice cues within the app. Images saved to Photos are separate copies that you manage in Photos, and any synchronization or backup follows your device and service settings.
We do not sell your information. We do not share your user-created rehearsal content, reference images, exported movement sheets, voice cues, or rehearsal notes with third parties unless you choose to share them, request support that requires sending them, or disclosure is required by law.
The reviewed native app contains no third-party advertising, attribution, analytics or crash-reporting SDK. This does not mean that no data leaves the device: the application service receives the startup information in Section I, and a web server receives requests when its page is loaded. Apple distribution services, device backups, Photos synchronization, Google-hosted agreement pages and external services have their own data handling and settings. The native startup request does not include rehearsal photos, recordings or plans.
Native rehearsal content is processed locally, while startup identifiers and technical request information are transmitted to the application service. Website requests and support correspondence also leave your device. These services may process information outside your country or region; storage on your device alone is not an accurate description of all app processing.
Device backups, photo synchronization and external communications can involve additional processing by the services you choose. Those services operate under their own policies. Opening a linked policy or an in-app webpage is itself a network request and can disclose your IP address to the page provider.
User-created rehearsal content stored inside Niroga is generally kept on your device until you edit it, delete it, remove the app, reset the device, or otherwise clear the relevant local storage. Exported files or backups may remain wherever you save or share them, and you should manage those copies through the relevant device, cloud, or third-party service settings.
Device identifiers and session information have different lifetimes from rehearsal content. A cached identifier can persist in Keychain after uninstalling, and server-side records are not erased simply by removing the app. Support correspondence is separate from app storage. Contact us about retention or deletion of service records; we do not represent a verified fixed retention period for server records, backups or support mail in this policy.
Deletion requests are subject to applicable law and any retention necessary to meet legal obligations or resolve an ongoing request. If information must be retained, the response to your request should explain the relevant limitation. Deleting an original file does not delete copies you have exported or stored with another service.
Depending on your location, you may have rights to access, correct, delete, export, restrict, or object to the processing of personal information. You may also have the right to withdraw consent where processing is based on consent. Most rehearsal content can be reviewed, changed, exported, or deleted directly within the app or through your device storage controls.
Use the email in Section L to request access, correction or deletion of information associated with your use. Describe your request without sending passwords, session tokens or unnecessary sensitive content. Verification may be necessary to locate the correct records and protect other users. This contact route does not mean that uninstalling deletes server data, and it is not a substitute for an in-app account-deletion feature where such a feature is required.
User-provided data: Niroga may store information you enter or add, such as plan names, stage dimensions, performer numbers, formation points, movement timing, path waypoints, fixed area settings, rehearsal markers, voice cues, saved versions, reference images, reports, and exported movement sheets. This content is used to make the app work as a rehearsal planning tool.
Automatic network requests: On startup, Niroga sends a persistent device identifier to its application server and receives a session token. The device identifier is initially based on the iOS identifier for vendor, or a generated UUID when unavailable, and is cached in preferences and Keychain. Request headers include the device identifier, device model, iOS version, app version, bundle identifier, preferred language, device region setting, time zone. The destination server also receives your network IP address. The region setting is not GPS location. The native startup request does not upload rehearsal plans, photos or voice recordings.
Cookies and website data: Niroga can load remote content inside WKWebView as well as local rehearsal pages. Remote page providers receive requests and may use cookies or website storage for their sessions and features. The native absence of an advertising SDK does not establish what scripts on a remote page collect. Any collection through pages supplied as part of Niroga must be disclosed and comply with the same applicable privacy and consent requirements; a third-party policy does not excuse undisclosed app data collection.
We may update this Data Privacy Policy from time to time to reflect changes in the app, legal requirements, security practices, or operational needs. When we make changes, we will update the effective date above and, where appropriate, provide notice through the app, the App Store listing, or another reasonable method.
A policy update does not itself authorize a new use of your information. Where consent is required, it must be obtained before the relevant processing begins. Material changes will be identified through a reasonable notice method. You can review the policy and exercise your choices and rights described above.
This policy provides notice of information handling. Installing or continuing to use the app is not blanket consent to unrelated processing or cross-app tracking. Camera, microphone and Photos permissions are controlled through iOS, and any processing requiring separate consent must use an appropriate consent process.
If you add information about performers or other people, including children, obtain the necessary permission and follow applicable school, safeguarding and privacy requirements. Avoid adding unnecessary identifying or sensitive information. A parent or guardian may contact the address in Section L about a child's information. Local rehearsal content can be removed using the app's content controls; requests concerning server-side information require separate handling.
For questions: MausKeels420@hotmail.com