RyzenN Privacy Policy

Effective date: 2026-06-22

RyzenN is a secure record access app for Client and Agent access roles. Approved information is securely provided through the RyzenN M2 Server. RyzenN is not the official source-record provider app unless separately authorized, does not sell products, does not change source records, does not process claims, and does not replace official provider documents. Provider-issued records and communications remain the final source of truth.

For app access, data availability, or record-visibility questions, contact the RyzenN administrator.

Data We Collect

RyzenN may collect:

• Client name, email address, phone number, identification number submitted for secure record matching, and linked Agent ID. The M2 Server retains a keyed match value rather than the plain registration identification number.
• Agent name, email address, and Agent ID.
• Account credentials and session records.
• Structured record details securely provided through the RyzenN M2 Server.
• Temporary uploaded PDF files during secure M2 processing.
• Foreground location, only when you ask Care Location to sort nearby listed healthcare facilities.
• Audit, security, support, and operational logs.
• Store purchase and access entitlement metadata, including store name, product identifier, transaction identifiers, verification status, renewal state, entitlement expiry, and an Apple/Google account-binding identifier used to keep Client Access tied to the signed-in Agent account. Store purchase tokens are sent transiently for verification and only a one-way token hash is retained by the M2 Server; RyzenN does not receive or store payment-card details.
• Agent activation metadata, including a one-way device-install identifier hash, store purchase claim, activation source, and Agent-account binding used to prevent an activation claim from being reused for another Agent account. Client registration does not require a purchase. The identifier is stored securely on the device and only its one-way hash is retained by the M2 Server.
• Free-trial request details, including Agent name, Agent ID, email address, phone number, request and review status, selected trial duration, and the same one-way device-install identifier hash used to keep one approval tied to one registration.
• Promotional entitlement metadata, including a server-side promo-code identifier, redemption timestamp, redemption limit state, and lifetime-entitlement status. The promo-code value is sent only for redemption verification and is not stored in plaintext.
• Device-side quick login state stored securely on the device.

How We Use Data

We use data to:

• Create and secure client and agent accounts.
• Use the supplied email address for account sign-in, security notices, recovery, and support.
• Match Clients to approved records available through their RyzenN M2 Server access scope.
• Securely retrieve and display structured record data from the RyzenN M2 Server.
• Sort listed healthcare facilities near your current location when you request that in Care Location.
• Maintain audit trails for security and record handling.
• Verify Agent activation and Agent Client Access purchases, then enforce Agent registration and linked-Client visibility entitlements.
• Notify Admin about free-trial requests, record the approval decision, and start approved Agent trial access at registration.
• Respond to support, account deletion, and data requests.
• Maintain backups and operational reliability.

Data Sharing

RyzenN does not sell user data and does not use user data for third-party advertising or tracking.

Data may be processed through infrastructure required to operate the RyzenN M2 Server service, including HTTPS ingress, secure server storage, monitoring, and backup systems. Apple App Store and Google Play process payment and store-account information under their own terms and privacy policies; RyzenN receives only the purchase data needed to verify and enforce Client Access. Data may be disclosed when required by law, regulation, security investigation, fraud prevention, or legitimate operational obligations.

Storage And Retention

RyzenN stores live structured records on the RyzenN M2 Server. E-certificates shown in the Agent app are local device copies paired with existing structured analysis; the app does not upload PDF files.

Structured records, audit events, deletion requests, and backup records may be retained where needed for legal, regulatory, security, fraud prevention, dispute resolution, or operational continuity.

Account And Data Deletion

Signed-in clients and agents can initiate account deletion from inside the RyzenN app. A web deletion request path is also available at:

https://ryzenn.rynoxx.net/legal/delete-account

When a deletion request is received, RyzenN will remove or deactivate account access and delete associated personal data that is not required to be retained. Some approved-record, audit, transaction, security, fraud-prevention, legal, or regulatory records may be retained where required.

Security

RyzenN uses HTTPS for production transport, server-side password hashing, session-token hashing, keyed one-way identification matching, device secure storage for quick login, and server-side access checks for client, agent, and admin workflows.

Care Location

Care Location is an informational directory where facility and location information is retrieved by the RyzenN server from publicly available internet sources. RyzenN requests foreground location only after you ask to sort nearby facilities. You can search the directory without sharing location. Coordinates are RyzenN-derived from listed addresses for map display and nearby sorting.

Care Location is not medical advice, emergency guidance, treatment advice, or confirmation of panel eligibility. Call the facility or check the source listing to confirm current status, panel eligibility, hours, and emergency suitability before travelling. Contact RyzenN support for directory availability issues.

Children's Privacy

RyzenN is not directed to children and does not knowingly create accounts for children.

Contact

Privacy inquiries and support requests: support@rynoxx.net

Support page: https://ryzenn.rynoxx.net/legal/support

Policy Review Appointments And Calendars

When you book a policy review, RyzenN stores the linked client and agent, meeting time, time zone, meeting instructions, request and confirmation state, and completion status on M2. Appointment details are available to the participating client and agent. Generic appointment notifications are delivered using the existing device notification service.

Calendar connection is optional and requires device permission. You select a writable calendar on your phone to save and update confirmed appointments. RyzenN does not upload unrelated calendar events or busy-time records to M2. Review availability is based on Agent date locks, existing reservations and booking notice, not events in the phone calendar.

Confirmed appointments can be saved to a selected writable device calendar, including Apple or Google calendars made available by the phone. Updates occur while RyzenN runs or returns to the foreground. Calendar providers process the saved events under their own terms. Disconnecting stops future updates but leaves existing calendar events for you to manage in Calendar. You can revoke calendar access in device Settings. Account deletion cascades appointment records; backup retention follows the policy above.

Review programmes also store shared discussion-topic selections and follow-up titles, assigned roles, due dates and completion. These are visible to both appointment participants. Preparation checklist selections are returned only to the participant who saved them. They are deleted with the parent appointment under the same backup-retention policy.

RyzenN retains an account-scoped in-app notification inbox containing update titles, messages, timestamps and read status. Notifications can remain visible even if device push delivery fails. Recent notifications and pending app-generated alerts are cached on the signed-in device for offline viewing. Notifications are not shared with other clients or unrelated agents.