NavigatorIM Privacy Policy
Revision: 27 September 2026. Applies to NavigatorIM 2.4.2 for iPhone/iPad, native Apple Vision Pro Standard and separately authorized Enterprise deployments.
1. Publisher, contact and scope
ORTHOPRACTIS.COM SINGLE MEMBER P.C. (Orthopractis.com S.M.P.C.), Contact info@orthopractis.com for privacy requests and support. Publisher website: https://www.orthopractis.com.
This notice describes the app's processing and information you voluntarily send to the publisher. The publisher is responsible for its own support correspondence and any personal information it receives. An organization using the app is responsible for its own purposes, instructions, worksite information and device management. This notice does not make the publisher a remote custodian of files that remain only on your device.
NavigatorIM is a spatial model, fixture-layout and geometric-learning workspace. A medical-education demonstration uses synthetic teaching objects only. Do not import patient records, identifiable scans or other patient information for patient care. The app is not a patient-record system, diagnostic service or treatment-planning service.
2. What stays on the device
The standard app workflows process imported geometry, tracking observations, calibration values, model transforms and selected points on the device. This release has no publisher account, advertising SDK, advertising identifier use, embedded analytics uploader or automatic model/camera/point upload endpoint. It does not sell project information or use it for targeted advertising.
Camera frames, environment-derived spatial data, hand poses and accessory poses are not automatically sent by the app to the publisher. This is not a promise that the entire device is offline: Apple services, permission management, file providers, backup services, operating-system diagnostics and authorized Enterprise license services have their own behavior and policies.
The launch acknowledgement is a safety/use acknowledgement. It is not consent to tracking advertising, uploading projects, sending support material or waiving privacy rights. System permissions are separate choices.
3. Camera, motion, spatial sensing, hands and Muse
On iPhone and iPad, camera and motion-derived information supports foreground AR world tracking, compatible trained-reference recognition and model display. The app does not continuously record camera video and does not record microphone audio. Spoken instructions and warning tones are audio outputs. Operating-system keyboard dictation, when used, is a separate system service.
On native Vision Pro, supported tracking providers supply world/object anchors and poses. Optional hand tracking supplies joint, fingertip and wrist information for the features you enable. Optional Logitech Muse accessory tracking supplies accessory identity/state, poses and button or tip events. The current app uses one active spatial stylus. Pairing and accessory management also involve the platform and hardware provider.
Tracking observations update the current scene and enable coordinates you explicitly capture. Captured points can include a label, category, acquisition source, timestamp, coordinate frame and reference-file identity. The app does not automatically retain a continuous hand or accessory motion history for the publisher. This release does not implement facial identification, biometric identification, gaze recording, GPS location collection or a direct Vision Pro main-camera video feed.
Spatial coordinates, filenames, labels and geometry may themselves reveal personal or confidential information even without a person's name. Use non-sensitive examples when learning or filming.
4. Imports, preferences and local files
The app reads bundled resources and the files you choose through the platform's file interfaces. Supported imports can contain models, textures, trained reference objects and point data. A selected cloud file can be downloaded by its provider; the provider's account, transfer and storage policies apply. Import only content you are authorized to use.
Custom trained-reference files are copied into the app's Application Support storage. App preferences, including enabled reference roles and decorative logo-pulse settings, can persist in the app's own UserDefaults. Eligible local files may be included in system backups according to device settings. Some model imports use app-local temporary copies or security-scoped access while in use. Framework caches and temporary files can remain until cleaned up by the app or operating system.
A complete model/point/AR workspace is not automatically reconstructed at the next launch. Model transforms, temporary inspections and current point records are normally held in memory. Point-edit history and up to 32 local transform/opacity checkpoints per model are bounded undo conveniences, not a persistent backup. Stopping tracking is not the same as securely erasing every local file or backup.
5. Exports, photographs and recording
Exports and sharing occur when you request them. Depending on the chosen export, files can contain point labels and coordinates, reference information, timestamps and calibration or registration settings. The app prepares a local file and presents the system's export/share interface. Sharing Help exports the guide text, not an automatic attachment of project geometry. You select the destination or recipient.
The classic iOS marker workspace can add explicitly requested snapshots or reference-marker images to Photos. It requests add permission for that action. A snapshot may show surroundings and annotations; the app does not browse unrelated photos. Photos synchronization and later sharing follow your device and service settings.
Screen recording, mirroring or an external camera used to make a demonstration can capture what is visible, including surroundings, notifications and filenames. These are user-initiated or system-level activities, not an automatic publisher recording feature. Get appropriate permission, keep bystanders and confidential material out of view, and review a recording before publishing it. Never use identifiable patient material in a public demonstration.
Deleting a model or point in NavigatorIM does not delete its original source, retract an exported file, remove a photograph, erase a recording or recall a recipient's copy.
6. Local diagnostics and voluntary support
Local status indicators and developer/system logs can contain device/platform information, filenames, object names, error messages, model dimensions, coordinates, tracking state and reference identities. The app has no automatic diagnostic upload endpoint. Apple may supply developer diagnostics under Apple's own sharing settings; assess the data you choose to share there separately.
When you email support, the publisher receives the sender address, message and attachments you send. Supply only information needed to explain the problem. Avoid patient information, bystander images, passwords, confidential site plans and unnecessary full models. A small non-sensitive test file and exact reproduction steps are preferable when they are sufficient.
We use support information to answer requests, investigate defects, protect service/security records and handle related legal matters. It is not automatically added to a marketing list, sold, or used by the publisher to train a model on your private project files. A materially different future use requires appropriate notice and a lawful basis.
Support is voluntary. You can use the local app without emailing us, although withholding details necessary to reproduce a problem may limit the assistance possible. We do not use support information for automated decision-making producing legal or similarly significant effects, and we do not profile users for advertising.
7. Legal bases, recipients and international processing
For personal information received in support correspondence, the applicable basis may be steps you request in connection with a contract, performance of an applicable support contract, legitimate interests in responding to enquiries and maintaining reliable/secure software, or a legal obligation. Where a specific processing activity relies on consent, it can be withdrawn without affecting earlier lawful processing. A device permission does not create a blanket legal basis for unrelated processing.
Necessary email, hosting, security, professional-advice and support-administration providers may process information for those services, under applicable confidentiality and data-protection arrangements. Information may also be disclosed when legally required, to protect legal rights, or as part of a lawful business transfer with appropriate safeguards and notice where required. No automatic publisher project-upload service is introduced by this notice.
Support providers or their infrastructure may operate outside the European Economic Area. Where a transfer of personal information requires safeguards, the publisher must use an applicable lawful transfer mechanism, such as an adequacy decision or appropriate contractual safeguards, and any additional measures required for that transfer. Contact info@orthopractis.com for information about relevant recipients, destinations and safeguards or an available copy. This does not assert that a particular unverified provider, destination or safeguard is in use. Your independently selected Files, email, Photos and sharing services make their own disclosures.
8. Retention and deletion
Live observations are replaced or invalidated during tracking; captured workspace objects remain until removed, cleared or the process ends. Custom trained references and stored preferences remain until replaced, reset through an available control or the app-container data is removed. Temporary import/export copies and operating-system caches follow their actual cleanup lifecycle; no forensic secure-erasure guarantee is made.
Support information is kept only as long as needed for the request, reasonable related follow-up, security records and applicable legal obligations or disputes. Relevant factors include whether an issue remains unresolved, whether a file is still necessary to reproduce it and whether a legal retention duty applies. Unneeded attachments should be deleted or anonymized. Request deletion through the privacy contact; we cannot remotely erase information held only on your device, in another person's mailbox or by a provider you chose.
You can remove scene models and points, stop tracking, replace a reference and restore a bundled reference for a role that has one. An import-only role has no bundled file to restore. Deleting the app normally removes its app-container data; offloading is different and can preserve documents/settings. Backups and external exports need separate management. Keep original models and explicit exports you need; the app is not the only archive of your work.
9. Permissions, rights and complaints
Use available system settings to deny or revoke camera, world-sensing, hand, accessory or Photos permissions. Features needing a denied permission may be unavailable. You can decline the launch acknowledgement by closing the app. You can turn off speech, warning audio, optional hand capture and decorative animation using the relevant controls.
Subject to applicable law and its conditions, you may request access, correction, deletion, restriction, portability or object to processing of personal data held by the publisher. Where consent applies, you may withdraw it. We may request proportionate identity verification and will respond under applicable legal deadlines and exemptions. These rights are not reduced by a safety acknowledgement or by our not operating a project cloud service.
You may complain to a competent supervisory authority, including the Hellenic Data Protection Authority in Greece or an authority competent in your place of residence or work. Contact the publisher directly to request information or resolution; doing so does not remove your complaint rights.
The app is not directed at children and does not provide children's profiles. Avoid sending information about children to support. Demonstration participants need appropriate permission and supervision; permission to be filmed is distinct from agreement to use the app.
10. Organizations, security and updates
An Enterprise configuration may use Apple-authorized license and provisioning services. It is not a publisher-operated model-upload or surveillance service. Your organization may manage installations, permissions, backups, exports and device access, with its own notices and obligations. Enterprise labeling does not establish organizational compliance.
Use device authentication, current security updates, appropriate access controls and authorized file destinations. Local processing does not prevent exposure through an unlocked device, screenshot, recording, backup or an intentional export. No absolute security guarantee is made.
A release that materially changes data processing needs an updated policy and any required permission or consent before that processing. Published app-specific policy, included text and App Store privacy answers must describe the released behavior. Questions: info@orthopractis.com.
IMNailScrewAR — PRIVACY POLICY
Android Application
Effective date: 22 September 2026
1. WHO WE ARE
IMNailScrewAR is provided by Orthopractis.com S.M.P.C. (“Orthopractis”, “we”, “us” or “our”).
Contact:
Website: https://www.orthopractis.com
Support: https://www.orthopractis.com/navigation-system-for-intramedullar
Email: info@orthopractis.com
This Privacy Policy explains how the Android version of IMNailScrewAR handles information when you use the app. It applies to the app package com.orthopractis.imnailscrewar and should be read together with the app's Terms of Use.
2. PURPOSE OF THE APP
IMNailScrewAR is an experimental augmented-reality research, education and training application for studying intramedullary nail landmark-registration and locking-workflow concepts in controlled bench, model and sawbone settings. This release is not intended for patient-specific diagnosis, treatment planning or intraoperative navigation.
3. INFORMATION AND DEVICE RESOURCES USED BY THE APP
3.1 Camera
The app requests Android CAMERA permission because live camera images are necessary for ARCore marker recognition, tracking and rendering of augmented-reality overlays.
Camera images are processed during the AR session to recognize the supplied reference markers and estimate their position and orientation. The reviewed Build 5 does not contain developer-operated code that automatically uploads camera frames to an Orthopractis server.
The app does not request microphone permission.
3.2 AR registration, calibration and measurement information
The app calculates temporary AR poses, marker poses, calibration values, registration samples, landmark coordinates, distances, angles and related navigation geometry. In the reviewed build, these values are used locally for the active AR session and are not automatically uploaded to an Orthopractis server.
Registration samples are session data. Resetting the workflow clears the active registration set. Closing/clearing the app removes data that is held only in app/session memory, subject to normal Android operating-system behavior.
3.3 No user account
The reviewed build does not create an Orthopractis account and does not require a login, username or password.
3.4 No advertising or developer analytics SDK
The reviewed build does not include an advertising SDK or an Orthopractis-operated analytics SDK.
3.5 No location, contacts or microphone permission
The reviewed build does not request precise or approximate location permission, contacts permission or microphone permission. It does not use the ARCore Geospatial API or Cloud Anchors.
4. GOOGLE ARCORE / GOOGLE PLAY SERVICES FOR AR
IMNailScrewAR uses Google ARCore / Google Play Services for AR, a third-party platform component required for the app's augmented-reality functions.
According to Google's ARCore Data Safety documentation, ARCore may automatically collect certain data even when an app does not use Cloud Anchors or the Geospatial API. Google states that ARCore always collects:
• Google-account user identifiers when the user is signed in, or device identifiers when the user is not signed in;
• performance and diagnostic information relating to the app, ARCore SDK and device; and
• information about ARCore API usage and app activity.
Google states that these data are used for analytics, operation, diagnostics and improvement of AR experiences and are encrypted in transit on supported Google Play devices. Google also states that additional categories such as precise location or video data are collected when certain ARCore features such as Geospatial or Cloud Anchors are used. The reviewed IMNailScrewAR build does not use those features.
Google's processing is governed by Google's applicable terms, privacy policy and ARCore documentation. Orthopractis does not control Google's independent processing practices.
5. DATA SENT TO ORTHOPRACTIS
The reviewed app does not automatically transmit camera frames, AR poses, landmark coordinates, calibration values or patient information to Orthopractis servers.
If you voluntarily contact support by email, your email application—not IMNailScrewAR—sends the information you choose to provide. Orthopractis may then receive your name, email address, message contents and any attachments you voluntarily send. We use support communications to answer your request, investigate issues, protect the service and comply with legal obligations. We keep support correspondence only for as long as reasonably necessary for those purposes and any applicable legal requirements.
6. EXTERNAL LINKS
The app contains links to Orthopractis website, support, privacy and terms pages. Selecting one of these links opens the destination in your browser. Selecting the support email option opens your email application. Information processed by the browser, email provider, website host or other external service is governed by that service's own privacy terms and settings.
7. PATIENT, HEALTH AND SENSITIVE INFORMATION
IMNailScrewAR is not designed as a patient record system and does not require users to enter patient names, medical record numbers or other patient identifiers.
Do not intentionally place patient-identifying information in support messages, screenshots, recordings, filenames or other materials associated with the app. If the camera is used in an environment where people or confidential materials are visible, the user is responsible for obtaining any required consent and complying with institutional, professional and legal privacy obligations.
8. HOW WE USE INFORMATION
For the reviewed build, Orthopractis uses locally processed information only to provide the app's AR functions on the user's device. If you contact us, we use the information you voluntarily provide to deliver support, respond to questions, troubleshoot problems and protect our legal interests.
We do not sell personal data. The reviewed build does not use personal data for targeted advertising.
9. DATA SHARING
Orthopractis does not automatically receive or share the app's camera frames, AR registration points or calibration values through developer-operated servers in the reviewed build.
ARCore / Google Play Services for AR may collect information as described in Section 4. Android, Google Play, your device manufacturer, browser, email provider and network provider may also process information independently when providing their services.
We may disclose information that we actually hold if required by applicable law, lawful process, or where reasonably necessary to protect rights, safety, security or prevent abuse.
10. DATA RETENTION AND DELETION
The reviewed build does not maintain an Orthopractis cloud account or server-side record of AR session data.
Active registration and calibration information used by the app is local/session information. You can clear the active registration through the app's reset controls, clear the app's local data in Android settings, or uninstall the app.
If you have sent a support email and want to request deletion of support correspondence that Orthopractis still holds, contact info@orthopractis.com. We will consider the request subject to applicable legal obligations and legitimate record-keeping needs.
Data collected independently by Google through ARCore is subject to Google's retention, deletion and account/privacy controls.
11. SECURITY
The reviewed Android manifest does not request the INTERNET permission for Orthopractis-operated networking and disables cleartext HTTP traffic. The app nevertheless relies on Google Play Services for AR, which is a separate platform service and may communicate with Google. Google states that ARCore user data collected on supported Google Play devices is encrypted in transit using HTTPS.
No method of electronic processing can be guaranteed to be completely secure. Users must protect their device, operating-system access, local files and any exported or externally created materials.
12. CHILDREN
IMNailScrewAR is designed for adult professional, research and educational use. It is not directed to children and should not be marketed to children.
13. INTERNATIONAL USERS AND APPLICABLE LAW
Users are responsible for complying with privacy, health, research, professional and medical-device requirements that apply in their jurisdiction and institution.
Where the EU/EEA General Data Protection Regulation or similar law applies, you may have rights regarding personal information that Orthopractis actually holds, including rights of access, correction, deletion, restriction or objection where applicable. Contact info@orthopractis.com to make a request. Because the reviewed app does not create a user account or automatically upload AR session data to Orthopractis, we may not hold app-session personal data that can be retrieved by user identity.
14. CHANGES TO THIS POLICY
We may update this Privacy Policy when the app, SDKs, legal requirements or data practices change. The effective date above should be updated whenever a material revision is published. The policy in effect for the released version should accurately describe that version's behavior.
15. CONTACT
Privacy or support questions:
Orthopractis.com S.M.P.C.
Website: https://www.orthopractis.com
Support: https://www.orthopractis.com/navigation-system-for-intramedullar
Email: info@orthopractis.com
End of Privacy Policy.
HipNaviPro — Privacy Policy
Policy revision: 19 September 2026. Applies to HipNaviPro Android 1.0.1, Build 2, package com.orthopractis.hipnavipro. This app-specific policy describes this build; other Orthopractis products and the public website may have different practices.
1. Publisher and privacy contact
The publisher is Orthopractis.com Single Member P.C. For privacy questions, support or a request concerning information you have sent to us, email info@orthopractis.com. Website: https://www.orthopractis.com. Support page: https://www.orthopractis.com/. The public Privacy Policy is at https://www.orthopractis.com/privacy and the Terms of Use are at https://www.orthopractis.com/terms-of-use.
HipNaviPro is intended for education, synthetic demonstrations and non-patient bench evaluation. It is not intended to handle patient records, perform clinical navigation or support treatment decisions. Do not place patient identifiers in filenames, model files, screenshots, camera scenes or support messages.
2. Camera images and spatial processing
The camera is off until you accept the separate camera/AR disclosure, request live AR and grant Android Camera permission. During foreground AR, the app uses camera images and motion-derived poses through ARCore to recognize the six supplied reference images, display geometry and register the points you explicitly capture. The app does not use the camera in the background, continuously record video, record microphone audio or access your photo library.
Camera frames, marker identities and positions, point coordinates, local reference frames, timestamps and geometric results are processed in working memory. This build has no developer-operated camera-stream or case-data upload. The app does not identify faces or infer a person’s identity. Camera access can nevertheless reveal people and surroundings; use only an appropriate non-patient test environment.
A screenshot is created only when you choose the screenshot/export action. It may include the camera view, people, surroundings, displayed measurements and filenames. Review it before saving or sending it.
3. Google Play Services for AR and other platform services
AR features use Google Play Services for AR (ARCore), provided and updated separately by Google. Google’s Privacy Policy governs that service and its separate data processing. Its operation, diagnostics, service/device information, support checks, profile downloads and updates must not be confused with an Orthopractis upload feature. Read https://policies.google.com/privacy and https://developers.google.com/ar/develop/privacy-requirements before enabling AR.
HipNaviPro does not enable ARCore Cloud Anchors, the Geospatial API, account sign-in, a developer cloud backend or third-party app analytics/advertising SDKs. It does not request location, microphone, contacts, health-record or broad media-library permissions. Google Play, Android, your device manufacturer and document providers may process data under their own policies. Installing or updating AR services and checking device support may need internet access.
4. Information used during an app session
Working memory contains the current registration sequence, marker/reference observations, capture timestamps, instrument dimensions and confirmation status, selected hip side, derived angles/distances, display/layer settings and an optional model selected by you. Imported models are used as manually positioned visual context. The app does not create a persistent case database or automatically restore exported JSON sessions.
Launch acknowledgements and camera-disclosure acceptance are held only in memory for the current launch cycle. They are not stored in an account or transmitted to Orthopractis. New Activity creation or a new launcher entry asks again; returning from an external policy page or document picker does not silently count as acceptance or create a new acceptance record.
The app has no account registration, in-app purchase, subscription, ad identifier, personalised advertising or developer-operated behavioural analytics feature in this build. Distribution/payment information may be handled by Google Play if the publisher sells the app through that service.
5. File import, export and intentional transfers
Android’s system document picker gives access to a file you select or a destination you choose. The app does not scan all files or require all-files access. Supported imports are STL and a restricted static text-USDA/USDZ subset. Models may contain identifying geometry or names; do not use patient data.
Exports may include JSON, CSV, OBJ, STL, USDA, USDZ, a case ZIP, a screenshot or the supplied printable markers. Case exports can contain coordinates, dimensions, side, calibration values, timestamps, current/frozen reference poses, model names and calculated metrics. Portable scene geometry is in metres; a printed decimal is not an accuracy guarantee.
Files are exported only through a user-initiated action. A selected document provider may save locally or transfer files to a cloud account. The destination’s access controls, sync settings, retention and privacy terms apply. The app does not encrypt or password-protect the exported files itself and does not automatically send a copy to Orthopractis. Cancel the system picker to cancel that export.
6. External links and support messages
The five publisher links and approved technical/privacy references open only after you choose to leave the app for an external browser or email app. No case, image or measurement is attached to a web link. The browser/site may process IP address, cookies, device information and other data under its own policy. Local Help does not load remote pages or run JavaScript.
The support-email button opens a draft in your email app addressed to info@orthopractis.com, with an app-version subject. It does not send the message, attach files, collect your contacts or automatically include logs. You decide whether to write and send it. A sent support message can disclose your name/email address, message and any attachments you choose to add. Use only non-identifying examples.
We use support information that you send to answer the request, diagnose reported software issues and maintain the service. Relevant service providers, such as the publisher’s email/website providers, may process these communications to deliver support. These communications are not app-session uploads.
7. Purposes and legal bases for publisher processing
Optional camera processing occurs only after your in-app choice and Android permission. The app’s launch agreement is a software-use acknowledgement, not a blanket consent to unrelated processing, medical treatment or human-subject research.
Where data protection law applies to information received by the publisher, processing to answer a request or provide the service you ask for may be necessary to perform that service; limited support/security administration may be based on legitimate interests, and records required by law may be handled to meet legal obligations. Optional uses requiring consent will be explained and requested separately. We do not use this build to conduct automated decisions with legal or similarly significant effects about you.
8. Retention and deletion
The active case and model are retained in memory while the process continues. Tools → Reset session removes captures, fitted geometry and the imported model from the active case. Instrument dimensions remain until the process ends, but physical confirmation must be repeated. Undo removes the latest active capture. Ending or losing the process can discard all unsaved work; simply putting the app in the background does not necessarily end the process.
Files you previously exported are separate copies. Resetting the session, clearing app storage or uninstalling does not delete files saved through your document provider or copies sent elsewhere. Delete them using the Files app, chosen provider and any applicable trash/cloud-copy controls. The app cannot remotely erase recipients’ copies.
Support correspondence is retained only for as long as needed to resolve the request and for proportionate follow-up, security, legal or dispute-handling needs. Retention depends on the nature of the request and applicable obligations; information no longer needed should be deleted or anonymised. Contact info@orthopractis.com to request deletion of publisher-held correspondence. We cannot retrieve or delete a session that exists only on your device or in your selected file provider.
This app offers no user account, so there is no app account to delete. The absence of an account does not restrict your rights concerning support information you send to the publisher.
9. Your controls
You may decline the launch agreement and exit; accept it without enabling the camera; decline the separate camera request; use Help and Synthetic demonstration camera-free; stop AR with Tools → Stop AR / camera off; revoke Camera in Android app settings; cancel imports/exports; reset the active case; delete exported files with their provider; and uninstall.
Tools → Review launch consent stops AR and reopens the unchecked launch agreement. New consent is needed before live AR can restart. Withdrawal does not undo an export you already requested or recall a support message already sent.
10. Security and international services
The app’s manifest disables Android app backup and cleartext network traffic. Its local Help blocks network content, JavaScript and arbitrary file access; external destinations are restricted. These implementation measures are not a guarantee against every device, account, operating-system or provider risk, and the app does not provide secure erasure or encryption of exported files.
Protect your device with a screen lock, current software and appropriate provider/account permissions. Do not share secret keys, passwords or confidential medical data in error reports. Google, your chosen cloud/document provider and email/website providers may operate internationally. Their processing locations and transfer safeguards depend on the service used; review their notices. This policy does not claim a particular provider certification or transfer mechanism that has not been established.
11. Children and sensitive medical information
Hip
NaviPro is intended for adults conducting non-patient educational or engineering evaluation, not for children. It is not a children’s service and does not intentionally solicit children’s personal information or patient records. Contact the privacy email if you believe such information has been sent to us so that appropriate action can be taken.
12. Privacy rights and complaints
Depending on applicable law and the circumstances, you may have rights to access, correct, erase, restrict or object to processing of your personal information, request portability where applicable, and withdraw consent without affecting prior lawful processing. Contact info@orthopractis.com with the subject “HipNaviPro privacy request”. We may request proportionate information to verify and fulfil your request, and will respond within applicable legal time limits.
You may also complain to a competent data protection supervisory authority, including the Hellenic Data Protection Authority where appropriate. Rights requests about Google or your selected document/email provider may need to be directed to those providers. Nothing in this policy limits rights that cannot lawfully be limited.
13. Changes and policy availability
The policy revision and app version identify the practices described here. Material changes should be reflected in the app, the public Privacy Policy and the Google Play Data safety declaration before deployment. The offline copy is available from launch consent and Help without a camera or internet connection. The current published policy is at https://www.orthopractis.com/privacy; support is available at info@orthopractis.com.
CorectiAR
Effective section date: 18 September 2026
CorectiAR is an augmented-reality anatomical registration, geometric measurement and visualization application for qualified adult professional, research and trained users.
On-device processing
CorectiAR uses the camera and Google Play Services for AR (ARCore) to recognize printed reference images and estimate their poses. Live camera frames, reference-image poses, calibrated pointer positions, registered 3-D points, geometric calculations, measurements and imported STL/USDZ model data are used locally to provide the AR experience. CorectiAR does not intentionally transmit the user's registered anatomical points, measurements, screenshots, CSV exports or imported surface models to Orthopractis servers in this build.
ARCore
This application runs on Google Play Services for AR (ARCore), provided by Google and governed by Google's Privacy Policy. Google's current ARCore Data safety documentation states that ARCore automatically collects identifiers, performance/diagnostic data and ARCore API-usage/app-activity data for service operation, analytics and improvement. CorectiAR does not enable ARCore Geospatial or Cloud Anchor features in this build.
User-initiated files
SAVE IMAGE, EXPORT CSV and MARKERS write files to device storage only when requested by the user. IMPORT STL/USDZ reads only the document selected by the user through Android's system document picker. Users are responsible for lawful patient-data handling, de-identification, confidentiality, secure storage and later sharing.
Permissions
Camera is required for ARCore tracking. On Android 8–9, legacy write-storage permission may be used for user-initiated exports; modern Android versions use scoped storage. CorectiAR does not request background location, contacts, microphone, SMS or advertising-ID permissions.
Contact
Privacy questions: info@orthopractis.com
TagWeave - Privacy policy
Version 1.3.0 | 12 September 2026
About this policy
TagWeave: QR Field Notes 1.3.0 is provided by ORTHOPRACTIS.COM SINGLE MEMBER P.C. (Orthopractis). Contact info@orthopractis.com for privacy or support requests. Effective date: 12 September 2026. This policy describes the Android app, including its 3D and AR world, records, scanning, attachments, finding guidance, acknowledgements and exports. It is the TagWeave-specific policy; policies for other Orthopractis apps do not describe this app. The developer details and any legally required business address are available in the store’s developer profile.
Contact and public information
Website: https://www.orthopractis.com
Support and product guide: https://www.orthopractis.com/geotagging
Privacy Policy: https://www.orthopractis.com/privacy
Terms of Use: https://www.orthopractis.com/terms-of-use
Support and privacy contact: info@orthopractis.com
Acknowledgement on every launch and return
Before continuing into the notebook, scanning or AR, TagWeave presents the current terms, privacy information and field-safety limitations. Three initially unchecked boxes ask you to agree to the terms, acknowledge this policy and understand the limitations. You may read the complete documents offline, open public links, or decline and close. Declining does not delete your records. Agreement is held only in process memory for the foreground visit; no acceptance log, timestamp, signature or device identifier is sent to or retained by Orthopractis through this flow. A new launch or a return after the app has been fully backgrounded asks again. Ordinary navigation and rotation within TagWeave preserve the current visit. Returning from an external browser, Maps or file picker can therefore show the notice again, with the underlying form retained where Android keeps its activity state.
Acknowledging a privacy notice is not blanket consent to all processing. The launch boxes do not grant camera or location permission, send an email, initiate an export, activate live AR or start location tracking. Optional features have their own user actions, disclosures and Android permission prompts. Deny or revoke permissions through Android Settings whenever you wish. Choosing a feature does not waive data-protection or consumer rights. No marketing consent is requested.
Your records stay under your control
The app stores sites, point names, notes, materials, dimensions, optional phone coordinates and reported accuracy, capture times, groups, labels, selected photos and files, AR positions, service colours, visibility preferences, and structure connections in private app storage. These records can contain personal or confidential information you choose to enter. There is no TagWeave account, first-party server, advertising SDK, automatic cloud synchronization, or added first-party analytics SDK. Orthopractis cannot remotely see or restore your local site notebook.
Camera, motion and AR processing
Camera access is used while the scanner or AR screen is active. QR and barcode image recognition runs on the device. ARCore uses camera and motion information to estimate device movement, surfaces, and the printed reference pose. TagWeave does not implement camera-video recording, microphone recording, face identification, or a camera upload endpoint. Live camera frames and session anchors are not written into your notebook by TagWeave. Saved point positions are numerical coordinates relative to your site reference, with source, capture time and position mode. Overview placement, display lift, orbit and scale are presentation settings and do not rewrite saved physical coordinates. Your device’s screenshot or screen-recording tools may capture what is visible; those tools operate separately.
Google Play Services for AR
Optional live AR uses Google Play Services for AR (ARCore), provided by Google and governed by the Google Privacy Policy. Google’s ARCore disclosure describes collection of Google account identifiers or device-specific identifiers, performance and diagnostic information, and API-usage/app-activity information for analytics and service improvement. This collection is required for Google’s service and retained by Google; turning off a TagWeave layer does not turn off Google’s service telemetry. Google states that applicable data is encrypted in transit on supported Play devices and that it does not share these categories with third parties. This app does not enable Cloud Anchors, Geospatial API, cloud scene hosting, or their associated location/video upload flows. Google’s processing, retention, international transfers, and rights mechanisms are described in its policies: https://policies.google.com/privacy and https://developers.google.com/ar/develop/play-safety-label. Live AR is optional; the ordinary notebook and 3D overview do not require its camera session.
Location and permissions
Location is requested only when you choose a fresh phone-location fix or enable distance guidance in Find this point. Finding guidance reads foreground updates for up to one minute, stops when you leave that screen, and keeps the live fix only in memory. It estimates distance and bearing to your saved coordinate. A fix older than 20 seconds is not eligible for saving. Saving requires a separate review and confirmation; doing so stores latitude, longitude, reported horizontal accuracy, optional available altitude, fix time and a phonePosition source label in the selected point. This is the phone position, not a detected pipe location. There is no background-location service or automatically saved movement trail.
The finding screen retains the previous coordinate in the point's coordinate history when you confirm a replacement. This history travels with complete JSON, field-pack and encrypted-recovery exports, and remains even if you later remove the current coordinate. Delete the point/site and any recovery snapshots or external copies to remove those records; clearing Android app storage removes all of the local app's data. Basic record editing may replace or remove the current coordinate without creating this finding-history entry. A label-match confirmation and its time are screen/session information, not a safety inspection or a remotely stored event. Camera and location permissions can be denied or revoked in Android Settings; the corresponding features then remain unavailable until granted. The system document picker provides selected-file access. The app does not request broad storage, contacts, microphone, or media-library access. Manually entered coordinates are also stored with their source and unknown accuracy. After its confirmation dialog, opening Google Maps sends only the selected saved latitude and longitude in a Maps URL; the destination app or browser applies its own policies and may use its own location permissions. User-directed KML imports into Google My Maps disclose the selected exported point and connection information to Google.
Hazard presentation and display preferences
Electrical and gas warning arrows are generated locally from the saved service classification or the app's existing name/type-based service suggestion. They do not use a gas sensor, electrical detector, remote hazard feed, person profiling or automated safety assessment. Warning arrows are attached to visible projected record positions; classifications may be incorrect, incomplete or hidden by filters. Turning off pulse animation retains static warnings. The motion preference is stored locally; system animation and screen-reader settings can also suppress motion. No preference data is sent to Orthopractis.
Photos, documents, QR labels and models
Photos you select are copied into app storage as resized JPEG images. General documents and model attachments are copied without redacting their contents or embedded metadata. TagWeave renders its own spheres and connecting structures; it does not automatically upload attachments or convert arbitrary model files into an AR mesh. Opening an attachment grants the chosen external app access to that file. New compact TagWeave identifier QR labels contain site/point identifiers; earlier versions also included a serial. Numeric Code 128 barcodes encode a stable point UUID-derived number and a check digit; legacy MuseTag labels may embed record data. Anyone who receives an export or readable label may learn its contents. Legacy encryption is a compatibility format and is not a confidentiality guarantee.
Exports, sharing and recipients
JSON and field packs include saved AR coordinates, source labels, structure endpoints, colours, dimensions, notes, and other retained project fields. CSV is a summary and is not a full backup. Field packs can include selected photos and documents. Labels and PDFs contain the information visibly printed on them. Ordinary JSON, field packs, CSV, KML, identifier labels and their PDFs are not password protected by TagWeave. Encrypted recovery .twr files and the payloads in their PDF417/QR recovery sets are passphrase protected as described below. Visible label text and set identifiers remain readable. Only when you invoke an Android share, external viewer, maps, browser, or email action do those recipients receive the information you choose to disclose. Their terms and privacy policies apply. Check the recipient and remove sensitive material before sharing.
Purpose and legal basis
Local processing enables the record, scanning, AR and export features you request. Your organization may have its own responsibilities for personal data it places in the notebook or sends to others. If you voluntarily contact Orthopractis, your email address, message and files you send are processed to respond, troubleshoot and maintain service records. Where applicable, the legal basis is providing requested support or taking steps connected with that service; handling abuse, service administration and defending legal claims relies on legitimate interests, subject to your rights. Legally required records rely on the applicable legal obligation. Permission prompts give you device-level control and do not waive your data-protection rights. Google explains the legal bases for its own service processing in its privacy policy.
Retention and deletion
Local records remain until you remove their point/site, clear app storage or uninstall. Deleting a point also removes structure connections attached to that point. Point deletion leaves an identifier/timestamp tombstone inside the remaining site to preserve deletion history; delete the site or all app storage to remove that local history. Unreferenced stored attachments are pruned on point/site deletion. Temporary imports and exports may remain in app cache until Android clears it or you clear storage/uninstall. App cloud backup and automatic device transfer are disabled; keep a field-pack backup you control. Deleting local data does not delete copies exported to other apps, recipients, screenshots, or Google’s retained AR service information. Support correspondence is retained while needed to resolve your request, administer the service, comply with applicable obligations, or establish, exercise or defend legal claims, and should be removed when those purposes no longer require it.
Security, service providers and international processing
Android app-private storage and operating-system controls limit ordinary access; the notebook has no separate app password. Ordinary exports are readable files; only the specifically selected encrypted recovery format has passphrase protection. Device loss, malware, shared-device access and recipient handling can expose your information. Use device security and controlled backups. Orthopractis may use email and hosting providers to handle messages or operate separately published support pages. Those services may process information outside your country subject to applicable safeguards. The app itself has no first-party upload service. Google’s independent international processing is described in its policy. Opening the support, privacy, terms or home page leaves the native offline document and uses your browser. The Orthopractis website is hosted using Wix infrastructure, which can handle IP addresses, request/browser information and essential security or operational cookies. Website forms, optional analytics, embeds or marketing tools, if enabled by the site operator, are governed by the website's corresponding notices and cookie choices. This app does not automatically open those pages, copy its notebook to Wix, subscribe you to marketing or submit a support form. The supplied TagWeave support-page content adds no analytics, advertising or automatic location collection.
Your rights and choices
Depending on your location and the processing involved, you may request access, correction, erasure, restriction, portability, or object to certain processing, and withdraw consent where consent is the basis. Use app editing, export and deletion for local records. Contact info@orthopractis.com about information actually held by Orthopractis; we may need proportionate identity verification. We cannot retrieve data stored only on your device or erase copies held by independent recipients. Contact Google through its privacy controls for Google-held information. You may complain to your local data-protection authority; in Greece, the Hellenic Data Protection Authority is at https://www.dpa.gr. These rights are subject to applicable conditions and lawful exceptions.
Children, automated decisions and updates
TagWeave is intended for adult field-documentation users. It is not directed at children and has no public social feed or account registration. Orthopractis does not use the app to make automated decisions with legal or similarly significant effects about people, or to serve behavioural advertising. Changes to app processing will be reflected in a revised dated policy and, where required, a notice or additional choice before new processing begins.
Encrypted recovery and unique identifiers
The recovery feature processes the complete containing site's JSON locally, including all points and connected structures, optional coordinates and retained unknown fields. A point-level export therefore also includes other records in that site; review the scope before sharing. Separate attachment file contents are not embedded unless already present inside JSON. The passphrase is used locally to derive an AES-256-GCM key through PBKDF2-HMAC-SHA256 (600,000 iterations), with fresh random salt and nonce. It is not sent to Orthopractis, included in the export or deliberately saved as a preference. Temporary runtime memory and user-visible keyboard/clipboard/screenshot behavior are subject to the device environment; the app does not promise immunity to a compromised device. There is no master recovery key or password-reset service. Once restored, the decrypted records become ordinary local notebook data; the notebook itself is not encrypted with the recovery passphrase. Weak passwords and copies disclosed to others can expose the content. Barcode fragments, set identifiers, part counts and lengths remain visible. A public point number or identifier QR is a lookup key, not an access-control credential.
Recovery storage, snapshots and deletion controls
Scanned encrypted fragments persist in app-private recovery storage until cleared, successfully restored or removed with app data. Decrypted previews are held for the current screen; restoring writes the records to the ordinary local notebook. Before recovering over an existing site, a separate app-private JSON snapshot of the current site is kept for rollback. These snapshots may retain deleted site data and are not encrypted by a separate app passphrase. They survive individual point/site deletion. Recovery > Clear recovery history and export copies removes pending fragments, pre-restore snapshots and temporary export copies, while keeping active sites. Android app-data clearing or uninstall removes all local app data. Exported files, prints, recipient copies and Google My Maps imports remain outside this deletion control. Local snapshots are retained until you use these controls; no developer server receives them.
Specific user controls
Use Edit record to correct or remove the current location or change point information. Use Find this point to review a phone fix before saving it and to stop active guidance. Use Display in the AR world to switch warning motion off. Use Delete point or Tools > Delete this site to remove active records. Use Tools > Scan / import encrypted recovery > Clear recovery history and export copies to remove pending recovery fragments, pre-restore snapshots and temporary export copies. Use Android Settings > Apps > TagWeave > Storage > Clear storage to remove the entire local notebook, preferences and private copies. These operations cannot recall paper labels, files already shared, email attachments or maps imported into an external account. Store an authorized backup before destructive deletion if you still need the data.
For a privacy request, contact info@orthopractis.com and identify that it concerns TagWeave. Do not send recovery passphrases or private site files merely to ask a question. We will respond within applicable legal time limits; additional information may be needed to identify a request, and lawful retention exceptions may apply. If your employer or client supplied the data, also contact that organization's responsible person. No sale or behavioural-advertising use of app notebook data is performed by Orthopractis in this release.
CT VOXEL RESEARCH — PRIVACY POLICY
Version 1.0, Build 43
Effective date: September 10, 2026
Developer and data-contact entity
ORTHOPRACTIS.COM SINGLE MEMBER P.C.
Website: https://www.orthopractis.com
Support: info@orthopractis.com
Privacy: https://www.orthopractis.com/privacy
1. Scope
This policy applies to the public iOS/iPadOS, macOS, and visionOS Standard editions of CT Voxel Research. The public app provides local DICOM visualization, user-directed ROI geometry, and descriptive raw image-intensity statistics for research and education.
2. Data selected by the user
The app can process DICOM files, folders, and ZIP archives selected by the user. DICOM data can contain image pixels, study/series identifiers, dates, scanner and acquisition information, spatial geometry, and other metadata. Depending on the source, the original files may contain personal or health information. Users must process only data they are authorized to use.
3. Local processing
Selected data are copied into the app’s sandboxed local workspace and analyzed on the device. The app does not require an Orthopractis account and does not automatically transmit DICOM files, image pixels, ROI values, or generated reports to Orthopractis.
4. Generated data
The app can create local technical records containing ROI geometry, source-voxel coordinates, available patient-coordinate geometry, raw HU descriptive statistics, voxel counts, physical ROI volume, source metadata, technical warnings, and per-slice traceability. These records remain local unless the user explicitly exports or shares them through an Apple system interface.
5. Review demonstration
The bundled App Review study is synthetic, contains no real patient information, and is processed offline through the same importer used for user-selected data.
6. Data collection by Orthopractis
The public Build 43 contains no advertising SDK, third-party analytics SDK, user account, cloud synchronization, or automatic support-upload function. Orthopractis does not receive app-processed DICOM data or measurements unless a user deliberately sends information through email or another external service.
7. Apple and external services
Apple may process App Store transactions, crash or diagnostic information, and system-service data according to Apple’s policies and the user’s device settings. When a user exports or shares a file, the chosen destination is governed by that provider’s privacy terms.
8. Retention and deletion
Imported studies remain in the app’s local container until the user deletes a study, removes all local studies from Settings, or deletes the app. Exported copies are controlled by the destination chosen by the user. Orthopractis cannot remotely delete local files that were never transmitted to it.
9. Security
The app uses Apple sandboxing and user-selected file access. No software can guarantee absolute security. Users and institutions remain responsible for device security, access control, backups, de-identification, and compliance with applicable privacy and research requirements.
10. Children and patient data
The app is not directed to children. A professional or institution using data relating to a minor must have an appropriate legal basis, authorization, safeguards, and ethics or institutional approval when required.
11. Rights and inquiries
For privacy inquiries concerning information deliberately sent to Orthopractis, contact info@orthopractis.com. Rights may include access, correction, deletion, restriction, objection, and complaint to a competent supervisory authority, subject to applicable law.
12. Changes
This policy may be updated when the app or legal requirements change. The effective version is identified by its date and build reference.
OSTEOPOROSIS CT
PRIVACY POLICY
Version 2.3.0 (Build 41)
Effective date: September 9, 2026
Last updated: September 9, 2026
1. PURPOSE AND SCOPE
This Privacy Policy explains how ORTHOPRACTIS.COM SINGLE MEMBER P.C. ("Orthopractis," "we," "us," or "our") handles information in connection with the Osteoporosis CT application (the "App").
The App is available in distinct editions for iOS/iPadOS, native macOS, visionOS Standard, and a separately entitled visionOS Enterprise edition intended for private or managed institutional distribution. This Policy applies to all editions unless a section states otherwise. The public App Store editions do not include the Enterprise main-camera entitlement.
This Policy covers information processed by the App, information voluntarily sent to us for support, and information associated with use of our support and legal links. It does not replace the privacy notices, medical-record policies, research protocols, security policies, or legal obligations of the healthcare institution, clinician, researcher, or other organization that uses the App.
2. APP PROVIDER AND PRIVACY CONTACT
App provider and publisher:
ORTHOPRACTIS.COM SINGLE MEMBER P.C.
Email: info@orthopractis.com
Website: https://www.orthopractis.com
App support: https://www.orthopractis.com/osteoporosisct
General privacy page: https://www.orthopractis.com/privacy
Terms of Use: https://www.orthopractis.com/terms-of-use
For personal information that you deliberately provide directly to Orthopractis, such as a support email, Orthopractis is the controller of that information under applicable data-protection law.
For patient imaging or health information processed solely on your device under your or your institution's direction, Orthopractis does not receive, host, remotely access, or determine the clinical purpose of that information. The clinician, healthcare institution, research institution, or other organization using the App ordinarily determines the purpose and lawful basis for that local processing and remains responsible for its obligations as controller, covered entity, custodian, healthcare provider, researcher, or equivalent role under applicable law.
3. PRIVACY SUMMARY
The current Build 41 App is designed as a local-first medical-imaging tool.
The App does not require an Orthopractis account or login.
The App does not contain advertising.
The App does not use an advertising identifier.
The App does not track users across apps or websites.
The App does not include third-party advertising, behavioral analytics, or data-broker SDKs.
The App does not use HealthKit.
The App does not automatically upload DICOM studies, CT images, measurements, calibration entries, reports, camera frames, or patient data to Orthopractis.
The App does not sell personal information or health information.
The App does not use patient information for marketing or profiling.
The App processes user-selected files locally to provide its functions. A user may deliberately export a report or open an external website or email application. Those actions are controlled by the user and may transfer information to a destination selected by the user.
4. INFORMATION PROCESSED LOCALLY BY THE APP
4.1 User-selected DICOM studies and archives
The App allows the user to select DICOM files, folders, or ZIP archives through the operating system's document-selection interface. The App does not scan the entire device or automatically import the user's medical files.
Imported DICOM files may contain:
- CT pixel data and Hounsfield Unit values;
- patient, study, series, acquisition, institution, scanner, and protocol metadata embedded by the originating imaging system;
- direct identifiers or protected health information that may remain present in the original DICOM files, even when the App does not display or explicitly parse every identifier;
- Study Instance UID, Series Instance UID, SOP Instance UID, study or acquisition dates, series description, study description, modality, manufacturer, scanner model, image type, protocol name, kVp, reconstruction kernel, slice geometry, pixel spacing, contrast-related tags, and other source attributes needed for reconstruction, quality assessment, or provenance.
The App's user interface and reports are designed not to request or intentionally export patient name, patient identifier, or date of birth. This does not mean that the original imported DICOM file is anonymous. Users must treat imported studies as potentially identifiable health information unless the files have been properly de-identified by an authorized process before import.
4.2 Derived image and measurement data
The App locally derives information needed for its medical-imaging and measurement workflow, including:
- a reconstructed CT volume;
- linked axial, coronal, and sagittal multiplanar views;
- source-voxel coordinates and, where available, patient-coordinate information derived from DICOM geometry;
- region-of-interest center, dimensions, orientation, rotations, and inclusion logic;
- included, excluded, and padding-voxel counts;
- mean, median, minimum, maximum, standard deviation, percentiles, and other attenuation statistics;
- attenuation-band counts and percentages;
- physical region and accepted-voxel volumes;
- image sampling, spacing, dimensions, and quality flags;
- calibration slope, intercept, residuals, coefficient of determination, root-mean-square error, fitted range, extrapolation status, and other validation information when a calibration workflow is used;
- report provenance and method-version information.
These values are processed on the user's device. The current App does not transmit them to an Orthopractis server.
4.3 User-entered information
Users may enter or select information such as:
- a local study alias;
- phantom or calibration-profile identification;
- phantom serial or lot number;
- calibration certificate or controlled-manual identifier and date;
- material basis and density unit;
- scanner, tube voltage, reconstruction kernel, slice thickness, field of view, and protocol information;
- locally measured phantom Hounsfield Unit values and assigned reference densities;
- validation notes, approval status, approver name or initials, or related quality-control information.
Users should not enter a patient's name, patient identifier, date of birth, contact information, or other direct identifier into a free-text alias, note, filename, or calibration field unless they are lawfully authorized to do so and the identifier is necessary under their institution's controlled workflow.
4.4 Local workspace metadata
To manage imported studies, the App may create a local workspace identifier and manifest containing a random workspace UUID, import date, optional user-created alias, and original source filenames. Original filenames may themselves contain identifying information. The user or institution is responsible for appropriate naming practices.
4.5 Enterprise visionOS main-camera data
Only the separately distributed and appropriately entitled visionOS Enterprise edition may access the Apple Vision Pro main camera, subject to Apple authorization, institutional deployment, operating-system permission, and device capability.
When that Enterprise feature is used:
- camera frames are used for the live in-application preview or supported enterprise workflow;
- frames are processed in memory;
- the App does not automatically record, save, associate with a patient, analyze for identity, upload, or transmit those frames to Orthopractis;
- the institution must establish its own lawful basis, notice, consent, environmental safeguards, and access controls before using a camera in a clinical, research, or workplace environment.
The public visionOS Standard App Store edition does not contain this Enterprise camera entitlement.
5. INFORMATION THE APP DOES NOT AUTOMATICALLY COLLECT OR TRANSMIT TO ORTHOPRACTIS
In the current Build 41 public App Store editions, the App does not automatically send Orthopractis:
- DICOM files or CT pixels;
- patient identifiers or health records;
- regions of interest or measurement results;
- calibration profiles or certificate entries;
- exported PDF, JSON, CSV, or XLSX reports;
- camera images or video;
- precise or coarse location;
- contacts, calendars, photos, microphone recordings, motion data, or Bluetooth data;
- advertising identifiers or device fingerprints;
- browsing history, search history, purchase history, or product interactions;
- analytics events or behavioral profiles;
- crash logs through a developer-operated analytics SDK;
- account credentials, because the App has no Orthopractis account system.
This statement describes the audited Build 41 source and must be reviewed if later versions add a server, account, cloud synchronization, analytics SDK, remote support upload, artificial-intelligence service, telemetry, or other network-based feature.
6. PURPOSES OF LOCAL PROCESSING
The App processes selected data locally only as necessary to:
- import and decode user-selected DICOM data;
- reconstruct and display linked multiplanar CT images;
- define, display, edit, and quantify regions of interest;
- calculate attenuation and physical-volume statistics;
- apply a user-selected and locally validated QCT calibration relationship when all required evidence is available;
- document native pQCT or HR-pQCT provenance or a separately validated cross-modality study without reproducing proprietary manufacturer algorithms;
- generate user-requested technical and measurement reports;
- maintain the user's local study workspace;
- provide Help, scientific references, product information, and safety limitations;
- support a separately authorized Enterprise camera preview where applicable.
7. DEVICE PERMISSIONS AND USER CHOICE
The App requests access only when needed for a feature.
File access: The App uses the operating system's document picker. On macOS, access is limited by the App Sandbox and user-selected file permissions. Where required, the App uses security-scoped access for the selected resource.
Camera access: Main-camera access is limited to the separately entitled visionOS Enterprise edition. It is not part of the public Standard edition. The operating system presents its own permission request.
External links and email: Selecting Website, Privacy, Terms, Support, scientific references, or manufacturer links may open Safari, the user's default browser, or an email application. The user chooses whether to proceed.
The App does not require access to Contacts, Photos, HealthKit, Location, Microphone, or advertising tracking for its core Build 41 functions.
8. LOCAL STORAGE AND SECURITY
Imported studies are copied to an application-controlled local workspace so that the App can decode and review them reliably. The workspace is stored within the App's sandbox or container. The App applies operating-system file protection and backup-exclusion attributes where the platform supports them.
On macOS, the App uses sandboxed, user-selected file access. On iOS-family platforms, operating-system data-protection mechanisms may apply according to device state and platform behavior.
No software can guarantee absolute security. Device security depends on factors outside the App, including passcode strength, biometric configuration, operating-system status, device management, physical control, backup settings, malware, shared-device use, and the security of destinations selected for export.
Users and institutions should:
- use a device passcode and current operating-system security updates;
- restrict device and file access to authorized persons;
- use institution-approved storage and sharing destinations;
- avoid identifiable filenames and aliases where not necessary;
- de-identify research data before import when required;
- maintain their own backup, retention, audit, breach-response, and secure-disposal procedures;
- verify that exports reach the intended recipient;
- avoid sending patient-identifiable information to ordinary support email.
The App is not a substitute for an institutional picture archiving and communication system, electronic health-record system, medical-device cybersecurity program, or compliant records-management system.
9. RETENTION AND DELETION OF LOCAL DATA
Imported workspaces remain in the App's local container until one of the following occurs:
- the user deletes the individual study from the App;
- the user selects the App's command to delete all imported DICOM data;
- the operating system removes the App and its data;
- an authorized device-management process removes the data;
- the operating system purges eligible temporary information.
Deleting or uninstalling the App generally removes its local container, subject to operating-system behavior. "Offload App" or a similar storage-management operation may preserve app data. Device backups, snapshots, institutional backup systems, previously exported files, email attachments, cloud-provider copies, or copies made by other applications may remain after deletion from the App.
Generated reports may be staged in operating-system-managed temporary storage for sharing. The operating system controls when temporary files are purged; immediate secure erasure is not guaranteed. The user must separately delete every exported or destination copy.
Orthopractis cannot remotely view, retrieve, correct, or delete files that remain only on the user's device or in a destination chosen by the user.
10. REPORTS, EXPORTS, AND SHARING
The App can generate PDF, JSON, CSV, and XLSX reports at the user's request. Reports may contain sensitive technical or health-related information, including:
- study or series descriptions and identifiers;
- source and patient-coordinate values;
- scanner and acquisition information;
- measurement and quality results;
- calibration information and validation notes;
- dates, provenance fingerprints, report timestamps, and scientific references.
The reporting workflow is designed to omit source CT pixels and to avoid intentionally including patient name, patient identifier, or date of birth. Nevertheless, a report is not guaranteed to be anonymous. Unique identifiers, descriptions, dates, coordinates, filenames, device context, free text, or combination with other records may permit identification.
When the user activates the system share interface, the user chooses the destination, such as Files, AirDrop, email, messaging, a cloud-storage provider, a hospital application, or another installed app. That destination's terms, privacy practices, retention, security, and recipient access then apply. Orthopractis does not choose the recipient, cannot recall a sent file, and cannot delete a destination copy.
Users must inspect every report before sharing, confirm that the recipient is authorized, use an approved secure channel, and comply with professional secrecy, data-protection, medical-record, research, and institutional requirements.
11. SUPPORT COMMUNICATIONS
The App may provide a link that opens the user's email application. It does not silently send an email or attach a DICOM study.
When a user voluntarily contacts us, we may receive the information the user chooses to provide, such as:
- name and email address;
- organization and professional role;
- app version, platform, device model, and operating-system version;
- description of a technical issue;
- screenshots, diagnostic text, or attachments deliberately included by the user.
We use support information to respond, investigate defects, protect the App, maintain correspondence, and meet legal obligations. We retain it only as long as reasonably necessary for those purposes, dispute handling, security, or legal recordkeeping, and then delete or anonymize it when appropriate.
Do not send DICOM studies, patient names, patient identifiers, dates of birth, faces, medical-record screenshots, or other identifiable health information to info@orthopractis.com unless Orthopractis has expressly authorized a secure transfer method and the required legal and contractual safeguards are in place. Ordinary email may not be appropriate for protected health information.
Acceptance of this Policy does not create a business associate agreement, data-processing agreement, clinical-service agreement, or research agreement between Orthopractis and the user's institution.
12. APP STORE, APPLE, AND OPERATING-SYSTEM DATA
Apple may process information independently in connection with the App Store, purchases, downloads, updates, device services, TestFlight, crash reporting, diagnostics, or settings chosen by the user. Apple acts under its own terms and privacy policy.
Orthopractis may receive aggregated sales information, App Store performance information, customer reviews, or diagnostics made available by Apple. Such information is used for distribution, support, security, and product improvement. Orthopractis does not control the information Apple independently collects and does not receive a user's locally imported DICOM study through the App Store.
Users can manage Apple analytics-sharing and privacy settings through the applicable Apple device settings.
13. WEBSITE, EMAIL, AND EXTERNAL LINKS
The App contains links to Orthopractis webpages, email, scientific publications, standards organizations, phantom or equipment manufacturers, and other third parties. Opening a link leaves the App and may disclose ordinary web-request information, such as IP address, browser type, cookies, or referring information, to the selected website or service.
The App does not embed those external sites as a hidden data-collection mechanism. The privacy policy of the destination applies after the user opens it. Orthopractis is not responsible for the privacy or security practices of independent third-party websites.
Use of the Orthopractis website is also subject to the website privacy notice and cookie practices presented there.
14. DISCLOSURE OF INFORMATION HELD BY ORTHOPRACTIS
Because the current App does not automatically upload medical-imaging data to us, Orthopractis ordinarily has no App patient dataset to disclose.
For support or business information that Orthopractis actually holds, we may disclose only as necessary:
- to service providers acting under appropriate obligations for email, website hosting, security, professional advice, or business administration;
- to comply with law, court order, regulatory request, or enforceable legal process;
- to investigate fraud, security incidents, misuse, or threats to rights and safety;
- in connection with a lawful corporate transaction, subject to applicable notice and safeguards;
- with the individual's or institution's direction or consent.
We do not sell App personal data. We do not share App personal data for cross-context behavioral advertising. We do not use health information for advertising or data-broker purposes.
15. SPECIAL-CATEGORY, HEALTH, AND MEDICAL INFORMATION
DICOM images and derived measurements may constitute health information, medical records, special-category personal data, protected health information, or similarly regulated information.
The user and the user's institution are responsible for determining and documenting an appropriate legal basis and any additional condition required for processing health data, including patient care, professional secrecy, public-interest healthcare, research, consent, ethics approval, employment rules, or other applicable grounds.
The user is also responsible for complying with, as applicable:
- the EU General Data Protection Regulation and national implementing law;
- Greek medical confidentiality and health-record requirements;
- HIPAA and applicable United States state health-privacy laws;
- research ethics, institutional review board, and informed-consent requirements;
- hospital, university, employer, payer, and imaging-center policies;
- contractual restrictions imposed by the source of the DICOM study;
- medical-device and clinical-software requirements in the relevant territory.
The App's availability in an app store does not establish that a particular clinical or research use is legally authorized.
16. LEGAL BASES FOR INFORMATION RECEIVED BY ORTHOPRACTIS
Where Orthopractis receives personal information directly, such as a support request, the applicable legal bases may include:
- taking steps at the user's request or performing a contract;
- our legitimate interests in providing support, securing the App, preventing misuse, maintaining records, and improving reliability, balanced against the individual's rights;
- compliance with legal obligations;
- establishment, exercise, or defense of legal claims;
- consent, where consent is requested and is the appropriate basis.
For local patient data, the user or institution, not Orthopractis, is responsible for selecting the lawful basis and health-data condition for the intended use.
17. INTERNATIONAL DATA TRANSFERS
The App itself does not automatically transfer DICOM or measurement data to Orthopractis or to a developer-operated cloud service.
A user may choose an export destination in another country or contact support from another country. The user or institution is responsible for confirming that a chosen destination is permitted. Where Orthopractis or one of its service providers transfers support information outside the European Economic Area, we will use a lawful transfer mechanism where required by applicable law.
18. DATA-PROTECTION RIGHTS
Depending on applicable law, an individual may have rights concerning personal information held by Orthopractis, including access, correction, deletion, restriction, portability, objection, and withdrawal of consent where processing is based on consent.
To exercise a right concerning information actually held by Orthopractis, contact info@orthopractis.com and identify the request sufficiently for us to locate the relevant record. We may need to verify identity and authority. Rights may be limited by applicable exceptions, professional secrecy, legal retention obligations, or the rights of others.
Orthopractis cannot provide, correct, export, or erase a DICOM study that exists only inside the user's local App container and has never been transmitted to Orthopractis. The user must use the App's deletion controls or device-management tools for that local data. For patient records controlled by a healthcare or research institution, the request should ordinarily be directed to that institution.
Individuals in the European Economic Area may lodge a complaint with the competent supervisory authority. In Greece, information about submitting a complaint to the Hellenic Data Protection Authority is available at:
https://www.dpa.gr/en/individuals/complaint-to-the-hellenic-dpa
We encourage individuals to contact us first so that we can attempt to address the concern.
19. UNITED STATES STATE PRIVACY NOTICES
To the extent applicable United States state privacy laws apply to information held by Orthopractis:
- we do not sell personal information obtained through the App;
- we do not share personal information obtained through the App for cross-context behavioral advertising;
- we do not process App health data for targeted advertising or data-broker profiling;
- individuals may submit applicable access, correction, deletion, or appeal requests by emailing info@orthopractis.com;
- we will not discriminate against an individual for exercising an applicable privacy right.
Because local DICOM files are not transmitted to Orthopractis, such files are not part of an Orthopractis consumer-profile database.
20. CHILDREN
The App is a professional medical-imaging tool and is not directed to children as users. It is intended for adult qualified professionals, trained researchers, and authorized institutional personnel.
A DICOM study may concern a minor patient. The healthcare or research institution is responsible for the authority, consent or other lawful basis, safeguards, retention, access control, and disclosure rules applicable to that minor's information.
21. AUTOMATED DECISION-MAKING AND PROFILING
Orthopractis does not receive App measurements for advertising or user profiling. The App performs deterministic image-processing and measurement calculations selected by the user. It does not make an autonomous treatment decision, establish a legally binding decision about a patient, or replace professional interpretation.
22. CLINICAL AND RESEARCH LIMITATIONS RELEVANT TO PRIVACY
The App is not a patient portal, telemedicine service, cloud PACS, electronic health record, or emergency service. It does not automatically notify a clinician, patient, emergency service, manufacturer, regulator, or Orthopractis about a result.
Users must not assume that a local result has been backed up, transmitted, entered into the medical record, reviewed by another professional, or preserved for a legally required period. Those actions remain the user's or institution's responsibility.
23. SECURITY INCIDENTS
If a user suspects loss, unauthorized access, misdirected export, device compromise, or disclosure of patient data, the user should follow the incident-response and breach-notification procedure of the responsible institution. Contact Orthopractis at info@orthopractis.com when the suspected incident concerns an App vulnerability or information actually received by Orthopractis.
24. CHANGES TO THIS POLICY
We may update this Policy to reflect changes in the App, law, distribution, security, or our practices. The updated version will state a revised date and will be made available through the App, App Store privacy link, or Orthopractis website as appropriate.
A material change in data transmission, tracking, account services, analytics, cloud processing, or third-party SDKs will require review of the App's privacy disclosures and App Store privacy answers before release.
25. CONTACT
Privacy and support questions may be directed to:
ORTHOPRACTIS.COM SINGLE MEMBER P.C.
Email: info@orthopractis.com
Website: https://www.orthopractis.com
Support: https://www.orthopractis.com/osteoporosisct
Tremor Lab / HandTremor — Privacy Notice
Version 3.5.0 · Build 350 · Updated 30 August 2026 · iPhone, iPad and Apple Vision Pro editions
1. Publisher and privacy contact
Orthopractis — ORTHOPRACTIS.COM SINGLE MEMBER P.C., Mantzaridi 3, Panorama, 55236 Thessaloniki, Greece — provides the app and responds to app-support and privacy correspondence. Contact info@orthopractis.com (mailto:info@orthopractis.com). Website: orthopractis.com (https://www.orthopractis.com). App support: HandTremor support (https://www.orthopractis.com/handtremorapp).
This notice describes Tremor Lab / HandTremor version 3.5.0, not every product or website operated under the Orthopractis name. Orthopractis ordinarily cannot access, retrieve or remotely delete app records that remain only on your device. A clinician, clinic, employer, university or other organization may separately decide why and how another person's information is processed. That organization is responsible for its own legal role, participant information, lawful basis, confidentiality, retention and research approvals.
2. Information processed on your device
Depending on the edition and choices you make, the app processes camera images or ARKit hand-joint estimates, hand-side labels, landmark coordinates, timestamps, image orientation and dimensions, capture-source and recognition-engine metadata, recording-quality indicators, descriptive motion estimates, and task/session context you enter. Context can include coded participant/examiner identifiers, notes and event dates. Such records may be personal or health-related even without a person's name.
The all-18-measurements-by-two-hands live table and retained measurement cards process current values, technical/status flags and timestamps/ages needed to distinguish fresh, stale, insufficient and previous results. Optional user reference ranges store numeric bounds and their metric/source/engine/task/unit context locally. These are operator-entered settings, not inferred diagnoses or population-normal values. Table colors and educational clinical-context pages do not generate a diagnosis from a participant's measurements.
If you explicitly start a measurement timeline during an active trial, the app retains a bounded in-memory history for the table, individual charts and optional TXT/JSON reports. One checkpoint is requested per scheduled second. The record includes actual elapsed/wall capture time, scheduled second, missed ticks, tracking gaps and new-versus-reused analysis flags. Delays are not filled with catch-up or invented snapshots; reused results retain their freshness status and are not new observations. Opening table/chart windows alone does not activate history or capture. Timeline collection is separate from raw-landmark session storage and optional video.
Optional video records the visible camera scene and can include people, rooms, screens or documents. A hand-focused analysis does not make the footage anonymous. Use coded identifiers and avoid capturing unnecessary personal information.
The app has no Orthopractis user-account requirement, HealthKit integration, advertising identifiers, behavioral-advertising SDK, automatic third-party analytics, disease classifier, generative AI chat or remote inference service. Do not mistake local machine-learning hand detection for an AI medical consultation.
3. Recognition, camera frames and optional video
Apple Vision or the bundled MediaPipe hand-landmarker estimates camera landmarks locally. MediaPipe uses packaged scripts, model files and WebAssembly CPU execution in a nonpersistent WebKit environment. It does not download a recognition model at runtime or send frames to a cloud recognition provider. Native visionOS tracking uses ARKit rather than this camera recognition setting.
Ordinary landmark capture processes camera frames transiently; it does not automatically retain a camera movie. Silent video is a separate, affirmative choice during an eligible camera trial. A visible recording indicator is provided. No microphone audio is requested or recorded by this workflow. Obtain the necessary permission from participants and bystanders before recording.
You may explicitly import an authorized video. The app creates a separate protected video-only copy, removes audio from that copy and leaves the external original unchanged. On-device reanalysis produces a separate derived report; it does not overwrite the original video or live measurement record. Current limits include 10 minutes and 512 MB per recording/import, up to 4096 pixels per side for imports, and a selected range of up to 60 seconds per reanalysis report.
Enterprise main-camera access requires Apple's approved entitlement and license, device-policy eligibility and separate operating-system permission. Standard Vision Pro receives no live camera video through the companion connection. Native skeleton-only capture cannot create a camera recording.
4. Nearby companion connection
The optional iPhone companion sends extracted hand landmarks, relative timing and source/engine metadata to an explicitly paired Vision Pro, not camera images, video or microphone audio. Discovery uses generic app aliases. Pairing uses a one-time key and authenticated proofs; the app adds connection-specific AES-GCM encryption to required Multipeer Connectivity transport encryption.
Remembered pairing secrets use device-local Keychain protection. This allows a previously trusted device to reconnect when the permitted companion workflow is enabled. Stop companion mode or forget pairing to prevent future reconnection. Use only devices and networks you are authorized to use. Encryption reduces exposure but is not a guarantee against every security risk.
5. Local storage, retention and deletion
Session summaries, retained raw landmarks, optional recordings and derived reports are stored in the app's local container using the platform's complete-file-protection option and backup-exclusion settings. The app does not automatically upload them to Orthopractis or store health records in an app-managed iCloud database. Device security, lock state, operating-system behavior and organizational controls still matter; do not rely on device/iCloud backup as your retention mechanism for these records.
User reference ranges are retained locally as non-participant-specific settings across launches until changed or removed using the range controls, or until the app's local settings are removed. They are separate from saved session/video records. Deleting sessions/videos does not clear them; use Configured measurement limits to remove an entry or the separately confirmed Reset all configured limits action.
An activated timeline requests one snapshot per second, up to 600 snapshots or 600 seconds, for one active trial. Actual capture timing and missing scheduled ticks are retained; a precise real-time schedule is not guaranteed. It stops at its bound instead of overwriting earlier entries. Ending/cancelling capture or the trial stops collection; the retained history remains in memory for review/export until explicitly cleared or the app process ends. It does not automatically start for the next trial or survive relaunch. Clear an existing timeline before starting a replacement. It is not automatically added to saved session archives or uploaded.
Saved records remain until you delete them, the app container is deleted, or platform policy removes them. Capture limits are resource safeguards, not a retention schedule. The operator or deploying organization must decide and apply an appropriate retention period. App Offload is not the same as Delete App and may preserve data.
Use Sessions or the video library to delete selected items. Settings also provides deletion of all local sessions, raw landmarks, videos and derived video reports. Deleting a video removes its linked derived reports, but not independent live measurement records. Deletion is irreversible inside the app. Local deletion or uninstalling the app does not recall copies already exported to another destination or recipient.
6. Export and external destinations
Sharing is user-directed. Session JSON, metrics/raw CSV and Markdown reports are available through explicit export. The video-library interface exports derived JSON reports; it has no raw-video sharing button. Exported timing uses relevant elapsed intervals rather than the device's uptime clock. Review the content and destination before exporting: coded identifiers, dates, notes, landmarks and measurements can still identify or reveal information about someone.
Live-measurement snapshot export is a separate explicit CSV or JSON action. Tapping Export snapshot freezes the displayed values and metadata while capture continues; the export sheet then offers format choice, a health-data notice and Files destination selection. Changing format does not refresh the snapshot, and this is not an automatic per-frame recording. The file includes both hands' available values and status, source/engine/task/unit context, relevant timestamps/ages and the bounds used to evaluate user references. Participant notes and raw device-uptime values are not included in these snapshots. Even without those fields, motion values, dates and context can be sensitive; review the file and destination before sharing.
The timeline's explicit Export action freezes the whole retained history before TXT/JSON format selection. A health-data notice and acknowledgement precede saving, sharing or selectable-preview copying. Both formats include all 36 values per checkpoint at full numeric precision, dates, actual elapsed/wall capture time, scheduled seconds/missed ticks, analysis-generation/input-age context, new/reused flags, quality/status/gaps, source/engine/task/units, synthetic labels and applied reference bounds. Unavailable values remain unavailable, not zeros. The report omits participant/examiner identifiers and free text, notes, session/trial identifiers and raw device-uptime values. These omissions do not make it anonymous: dates, measurements and context remain sensitive. Later capture or format changes do not refresh the frozen run. No report is automatically sent to Orthopractis or another recipient.
For an acknowledged Share action, the app prepares an immutable, app-private temporary .txt or .json source file with the matching transfer type and asks the system to transfer a copy rather than grant access to the original. These source files use complete file protection and backup exclusion. Each report is limited to 32 MiB; TXT and JSON share the recognized private cache limit of 64 MiB and 64 files. The Save to Files action does not add a source file to this cache and remains an alternative if the cache is full.
Closing the report, cancelling a system share, clearing the timeline or deleting sessions/videos does not immediately erase these temporary source files: doing so could interrupt a receiving app's copy. Only recognized files from an earlier app process that are at least 24 hours old become eligible for removal at a later app initialization or share preparation. Current-process files are retained; the operating system may also purge temporary storage. This is an eligibility rule, not a promise of deletion exactly 24 hours after sharing. Files saved externally, clipboard contents and system/recipient copies remain outside these cleanup controls.
A browser, email app, Files provider, receiving organization or other export destination has its own privacy practices, storage locations and retention rules. Only send records to a destination authorized for their sensitivity. Once a copy leaves the app, the recipient controls it. The app does not automatically attach records to a support email.
7. Launch choices and operating-system permissions
Each new app process begins with launch acknowledgement unset. Decline keeps capture, recording, spoken guidance and automatic companion activity closed. Acceptance is held in memory for that process; bringing an existing window forward is not a new launch. Withdrawal in Settings stops active capture, timeline collection, companion transmission, guidance and reanalysis; saving already captured frames may finish. Withdrawal does not recall a system transfer already requested or itself erase previously saved or exported information. Eligible old private share files may be cleaned during app initialization before acceptance; this cleanup does not start capture or transmit data.
Video recording needs its own separate confirmation. Apple also controls camera, hand-tracking and local-network permissions, which you can manage in system Settings. These permissions and the launch notice are not substitutes for a patient's clinical consent, a research consent record, or a lawful basis for processing another person's health data.
8. Information Orthopractis receives and privacy rights
Orthopractis may receive what you deliberately send in support or privacy correspondence, such as your email address, organization, app/device version and issue description. Do not send patient-identifiable records to ordinary support email. Support correspondence is used to respond, maintain the app, resolve issues and satisfy applicable recordkeeping or legal obligations. It is retained for the relevant support purpose and applicable legal or claim periods, then deleted or anonymized unless a legal hold applies.
Opening a website or using email leaves the local app workflow. Website hosting, logs, cookies and email-provider processing must be understood from the relevant service notices and actual publisher practices. Apple also processes store transactions and user-enabled platform diagnostics under its own policies. This app does not add automatic capture-data uploads, tracking or advertising to those services.
Where applicable, contact the responsible controller about access, correction, deletion, restriction, portability, objection or withdrawal of consent, and the right to complain to a supervisory authority. Orthopractis can respond about information it receives and controls; your clinic or organization may control locally held clinical or research records. Health-data processing requires an appropriate legal basis and any additional condition required by law. There is no blanket GDPR, HIPAA or medical-device certification in this notice.
9. Changes and contact
Material changes to processing require an updated notice matching the installed version. The app does not silently add remote AI processing through this release. Review the current product-specific notice and your organization's procedures when updating.
Published Privacy Policy (https://www.orthopractis.com/privacy) · Terms of Use (https://www.orthopractis.com/terms-of-use) · App support (https://www.orthopractis.com/handtremorapp) · info@orthopractis.com (mailto:info@orthopractis.com)
ScoliosisApp Privacy Policy
Apple platforms — iOS, iPadOS, and visionOS
Effective date: 22 August 2026 | Version 1.0The clean TXT file in the delivery pack is the copy-ready version. Approve the legal entity, final signed-build data flow, regulatory classification, distribution territories, and App Store EULA choice before publication.
This Privacy Policy explains how ScoliosisAppPro for iPhone, iPad, and Apple Vision Pro (the “App”) handles information and how Orthopractis handles direct App support and legal correspondence. It applies to the Apple-platform editions described here. An Android edition or a future release with materially different data practices will be covered by an updated or platform-specific notice. Opening an external website leaves the App; website logs, cookies, and site tools must be described in a separate accurate website and cookie notice.
The App is designed as a local-first posterior-surface capture, mesh-review, and research/professional-review tool. The current Apple edition does not contain an Orthopractis account system, advertising SDK, tracking SDK, third-party analytics SDK, or automatic upload of scans to an Orthopractis server. Local processing does not mean that every file is anonymous or risk-free: a surface mesh, colour data, body landmarks, measurements, or report may be personal, biometric-like, or health-related information when it identifies or relates to a person.
1. Who is responsible for this Policy
The provider and privacy contact for the App and its public support pages is ORTHOPRACTIS.COM SINGLE MEMBER P.C. (Monoprosopi IKE) (“Orthopractis”, “we”, “us”, or “our”), Mantzaridi 3, Panorama, 55236 Thessaloniki, Greece. Email: info@orthopractis.com. Phone: +30 694 425 0035. Website: https://www.orthopractis.com.
Orthopractis is responsible for personal information it actually receives and controls, such as support correspondence or website contact information. Orthopractis ordinarily cannot see, retrieve, or remotely delete scans, imported meshes, reports, or exports that remain only on a user’s device or in a destination selected by the user.
A clinician, clinic, hospital, university, research institution, employer, or other deploying organization may determine why and how subject or patient information is captured, stored, used, or shared. That operator or organization is responsible for its own legal role, notices, consent or other lawful basis, confidentiality duties, retention schedule, security controls, and data-subject requests. This Policy does not replace the operator’s own privacy notice or research consent form.
2. Information processed by the App
Depending on platform, hardware, edition, and the features selected, the App may process the following information on the device or during an encrypted nearby-device session:
Live camera images or bounded image regions; measured scene depth; LiDAR or spatial/scene-reconstruction geometry; camera calibration; device pose, motion, and world-tracking information.
Body or pose landmarks, shoulder/hip reference points, confidence values, and camera-derived overlays used for local visualization and alignment.
Surface points, colour samples incorporated into a mesh, triangle geometry, capture boundaries, scale and registration information, imported meshes, and technical metadata.
Derived measurements, quality-control results, comparison values, reports, and investigational or research-oriented indicators, which may include AI1, AI2, AI3, AIglobal, OSAI-R, dOSAI, QCI, Candidate Cobb, or Projected Cobb outputs.
User-selected imported files and locally created exports, including USDZ, OBJ, STL, PLY, XYZ, CSV, JSON, and text reports, where supported by the installed edition.
Local operational preferences and transient nearby-pairing information such as the device name, peer display name, identifier-for-vendor, device capabilities, calibration state, or connection status. In the reviewed iOS edition, the accepted legal-copy version and acceptance date/time are stored in UserDefaults; in the reviewed visionOS edition, launch-consent state is held in memory for that launch rather than persisted in the same way.
The current Apple edition does not request microphone access and does not use HealthKit. The core workflow does not require an Orthopractis user account.
3. Camera, depth, spatial, and landmark processing
Camera, depth, spatial, tracking, and landmark inputs are used to frame a bounded posterior region, guide capture, reject unstable motion, reconstruct or refine a surface mesh, display a preview, calculate technical measurements or quality indicators, and prepare user-controlled files.
Live/raw camera frames—including the low-resolution images used in a paired session—are processed transiently in memory and are not intentionally written to persistent storage or automatically uploaded to Orthopractis. Pixel colour may nevertheless be sampled into generated surface geometry. An exported mesh can therefore persist colour and remain sensitive or identifiable even though the live/raw camera frames are not saved.
Standard visionOS uses public world-sensing/scene-reconstruction features and may receive data from one or two paired iPhone or iPad camera nodes. A separately entitled Enterprise edition may use approved Apple Vision Pro main-camera features. Permission prompts and available features differ between these editions.
4. Nearby Apple-device pairing
In compatible paired workflows, local-network browsing can begin automatically after the post-consent interface appears. Nearby Apple devices may automatically discover or invite one another and exchange a repeated stream of full-frame 320 × 240 grayscale/luma images—the full low-resolution camera field rather than an anatomical crop—plus calibration and timing information, body landmarks, camera transforms and intrinsics, geometry, measurements, quality information, device name, peer display name, identifier-for-vendor, capabilities, and operational status needed for real-time capture. A device or peer name may contain a person’s name. The App uses Apple Multipeer Connectivity with encryption required.
This version does not add a user-entered pairing code or separate identity-authentication step and can automatically accept peer invitations or certificates. Encryption protects the transport but does not by itself prove the identity of a nearby peer. Nearby traffic is not an automatic upload to an Orthopractis server. The user or deploying organization must operate in a controlled environment, use trusted devices and networks, check the participating device names, end the session when finished, and comply with local-network and institutional security rules.
5. Local files, imports, exports, and retention
The App creates persistent files when a user imports content or performs a capture, report, or export action that writes a file. In the reviewed visionOS workflow, pressing Final Capture automatically creates a persistent export package containing mesh, measurement, report, and quality/QCI files; it does not require a separate Export action. On iOS, generated exports are written under the App’s Documents/Scoli_Exports folder; imported meshes are copied to Documents/ImportedMeshes. On visionOS, generated files may be written under Documents/ScoliosisAppProVision_Exports. The App enables system document/file-sharing workflows, so these files may be visible through Files or connected-device file sharing.
Generated export folders are marked as excluded from device backup where the operating system honors that setting. The reviewed source did not explicitly exclude Documents/ImportedMeshes from backup. Because personal health information must not be stored in iCloud, that exclusion and real device-transfer/backup behavior must be corrected and verified before the App is released for personal health information; until then, do not import or retain personal health information in that folder. Files moved to another location, cloud provider, backup, recipient, or institutional system follow that destination’s rules. Do not assume that deleting an active scan or resetting a view deletes previously generated or imported files.
Local files remain until the user deletes them through Files or another available file-management route, uses Delete App to remove the App and its local container, or deletes every copy at its destination. Apple’s Offload App function preserves Documents and app data and is not a deletion method. Deleting the App does not recall copies already exported, shared, backed up, or received by another person or service. Orthopractis does not receive or retain a copy merely because a user creates, previews, saves, or shares a file.
6. Information Orthopractis may receive
The App does not automatically send scans or measurements to Orthopractis. Orthopractis may receive limited information in these circumstances:
Support or legal correspondence: email address, name, organization, app version, device/operating-system details, a description of the issue, and attachments voluntarily sent by the sender.
External website use: opening an Orthopractis support, privacy, or terms page leaves the App. IP addresses, browser/device data, security logs, pages requested, cookies, and site tools are not generated by the App workflow and must be covered by the separate, current website and cookie notice after a live-site processor and cookie audit.
App Store and platform information: Apple may process downloads, purchases, platform diagnostics selected in Apple settings, and other store or device services under Apple’s policies. Apple may make limited sales, crash, or diagnostic information available to developers.
Information required by law: information received from a competent authority or maintained to establish, exercise, or defend legal claims.
Do not send patient or subject names, dates of birth, medical record numbers, images, meshes, measurements, or health records to Orthopractis’s public support email. No patient-file support-transfer channel was established in the reviewed materials.
For information Orthopractis controls, retention is based on these criteria: support and legal correspondence is kept until the request and any promised follow-up are complete and applicable support, recordkeeping, and legal-claim periods expire; complaint, safety, regulatory, accounting, or legal-claim records are kept for the applicable statutory or limitation period or while a legal hold applies. Website log and cookie retention belongs in the separate website/cookie notice and must match the host’s actual configuration.
Apple controls its original App Store and platform records. If Orthopractis receives a developer copy of crash or diagnostic information, it is kept only while needed to investigate or correct the issue, document a release or security decision, meet a legal duty, or handle a related claim. When the applicable purpose and retention criterion ends, Orthopractis deletes or anonymizes the information unless continued retention is required by law.
7. Purposes and lawful bases
Where Orthopractis processes personal information it actually receives, the purposes and legal grounds may include:
Providing requested support, maintaining the App, administering applicable Terms, and responding to communications—performance of a contract or steps requested before a contract, and our legitimate interests in supporting the product.
Protecting the App, website, users, and rights; preventing misuse; troubleshooting; and maintaining security—our legitimate interests and, where applicable, legal obligations.
Maintaining tax, accounting, regulatory, safety, complaint, and legal records—compliance with legal obligations and establishment, exercise, or defense of legal claims.
Responding to privacy requests and consent choices—compliance with legal obligations and, where processing relies on consent, that consent until it is withdrawn.
Health-related information can be a special category of personal data under European law. Orthopractis does not ask users to transmit patient health information through ordinary support channels. The operator or deploying organization must identify an appropriate Article 6 basis and, where required, an Article 9 condition or other applicable authorization for its own patient, professional, or research processing. General acceptance of App Terms is not a substitute for valid clinical or research consent.
8. Sharing and recipients
Orthopractis does not sell personal information and does not use App-derived camera, depth, body/pose, health, or research data for behavioral advertising, cross-app tracking, marketing profiles, or use-based data mining.
Information may be disclosed only as relevant to the circumstances described below:
To a destination deliberately selected by the user, such as Files, AirDrop, email, messaging, cloud storage, an institutional repository, or another installed app. The destination’s terms, privacy practices, access controls, and retention then apply.
Between nearby Apple devices participating in an active encrypted pairing session. This version relies on automatic local discovery and does not add a user-entered pairing code.
To service providers supporting email, security, or professional advice. A provider acting on Orthopractis’s behalf may process information only for authorized purposes and must, through contract and applicable law, protect it to at least the same level described in this Policy. An independent provider or destination acts under its own notice where it determines its own purposes.
To Apple and other platform providers for store distribution and platform services under their own notices.
To authorities, courts, advisers, insurers, or transaction counterparties where required by law, necessary to protect rights or safety, or relevant to a legitimate corporate transaction.
On-device libraries and model runtimes, including MediaPipe-related components and SwiftTasksVision, are used for local functionality. As configured in this edition, those components do not automatically transmit App capture data to Orthopractis or to a third-party analytics service.
9. Security
The App reduces exposure through local processing, Apple permission prompts, app-container isolation, system file interfaces, required encryption for nearby Multipeer Connectivity sessions, and user-directed destinations. Generated export directories are marked to avoid backup where supported; the reviewed imported-mesh directory requires the backup-exclusion correction and verification described in Section 5 before health-data use.
No method of capture, storage, transmission, or deletion is completely secure. Users and deploying organizations must use device passcodes, current operating-system updates, managed-device controls where appropriate, trusted networks and recipients, access-controlled storage, secure backups, minimum-necessary capture, and verified deletion. Export formats are portable and should not be assumed to be encrypted containers.
10. Your choices, consent, and deletion
Decline the launch notice; do not grant Camera, Motion, World Sensing, Main Camera, Local Network, or another requested system permission; or do not select a file or destination in a document picker. Some features will then be unavailable.
Revoke system permissions in Apple Settings and stop nearby pairing from the participating devices.
End capture and clear transient working state. This does not delete files already written to Documents or shared elsewhere.
Delete generated exports and imported copies through Files or another available file-management route; delete destination copies separately.
Use Apple’s Delete App function to remove the local app container and preferences, subject to device-management, backup, and external-copy behavior. Offload App preserves Documents and app data and does not delete those files.
For information actually held by Orthopractis, send a request to info@orthopractis.com. We may need to verify identity and may retain information where required by law or necessary for legal claims.
Because Orthopractis ordinarily does not possess device-local scans or exports, it normally cannot locate or delete them remotely. Requests about a cloud provider, recipient, hospital system, research database, or other selected destination must be directed to that controller or provider.
11. Privacy rights
Depending on applicable law and subject to exceptions, an individual may have rights to be informed; access personal information; correct inaccurate information; request deletion; restrict processing; object; receive portable data; withdraw consent without affecting earlier lawful processing; and obtain human review of a solely automated decision that produces legal or similarly significant effects.
The App generates technical outputs but is not intended to make autonomous legal, treatment, or clinical decisions. A qualified user must review outputs. To exercise rights concerning information actually controlled by Orthopractis, contact the address in Section 17. EEA users may complain to their local supervisory authority or the Hellenic Data Protection Authority at https://www.dpa.gr/en/individuals/complaint-to-the-hellenic-dpa. Users elsewhere may contact the regulator responsible in their jurisdiction.
Residents of California and other U.S. states may have additional rights under applicable state law. Orthopractis does not sell App-derived personal information or share it for cross-context behavioral advertising. Requests may be sent to the same privacy contact.
12. Children and minors
The App is not directed to children as independent users. An operator must not scan a minor unless the parent, guardian, or other legally authorized representative has given the permission required by law and the activity is appropriate under professional, institutional, safeguarding, and research rules. Assent from the minor and independent ethics review may also be required.
Do not use the App to create an online profile of a child, for advertising to a child, or for unsupervised self-diagnosis. If you believe child-related information was sent directly to Orthopractis without appropriate authority, contact us promptly.
13. Health care, research, and institutional use
The App does not make an operator, institution, or Orthopractis compliant with the GDPR, HIPAA, medical-device rules, research law, or professional confidentiality duties by itself. Each organization must assess whether the App is permitted in its setting, configure appropriate technical and organizational controls, document responsibility for files and devices, and enter any required agreements.
Health-related human-subject research must use a study-specific informed-consent process describing purpose, duration, procedures, risks, benefits, confidentiality, sharing, contact information, and withdrawal, and must obtain independent ethics/IRB approval where required. The App’s launch acknowledgement is not a research informed-consent form.
14. International transfers
Device-local information remains wherever the user or institution keeps the device and selected copies. Website, email, platform, support, and selected destination providers may process information in other countries. Where Orthopractis is responsible for an international transfer and law requires a safeguard, it will use an available legal mechanism such as an adequacy decision or approved contractual protections, as applicable.
15. Third-party services and links
The App links to Orthopractis support, privacy, terms, and email destinations. Apple, Wix, email providers, cloud storage, messaging, document providers, and other selected services operate under their own policies. Orthopractis is not responsible for a third party’s independent processing. Review the destination before sending sensitive information.
16. Changes to this Policy
We may update this Policy to reflect App features, platform or SDK changes, security improvements, legal requirements, or support practices. The revised effective date and version will be posted. Material changes affecting capture or disclosure may also be presented in the App. The policy and App Privacy label must be updated before release when a new build introduces a materially different data flow.
17. Contact
Privacy and legal requests: info@orthopractis.com
Provider: ORTHOPRACTIS.COM SINGLE MEMBER P.C. (Monoprosopi IKE)
Address: Mantzaridi 3, Panorama, 55236 Thessaloniki, Greece
Phone: +30 694 425 0035
Website: https://www.orthopractis.com
Support: https://www.orthopractis.com/scoliosisapppro
Privacy Policy: https://www.orthopractis.com/privacy
Terms of Use: https://www.orthopractis.com/terms-of-use
POTSI APP PRIVACY POLICY
Effective date and last updated: 27 August 2026
1. WHO WE ARE AND WHAT THIS POLICY COVERS
Potsi App (Android package com.orthopractis.potsiapp) is provided by ORTHOPRACTIS.COM S.M.P.C. (“Orthopractis”, “we”, “us”, or “our”). This Privacy Policy explains how the Android edition of Potsi App accesses and processes information, how user-controlled exports work, and what information Orthopractis may receive when a user separately contacts support or visits an external website.
Website: https://www.orthopractis.com
Potsi App support page: https://www.orthopractis.com/potsi-app
Direct Privacy Policy page: https://www.orthopractis.com/potsi-app-privacy-policy
Terms of Use: https://www.orthopractis.com/potsi-app-terms-of-use
Privacy and support contact: info@orthopractis.com
2. APP PURPOSE
Potsi App is a professional image-measurement aid for marking eight posterior-trunk anatomical landmarks and calculating geometric POTSI, FAI, and HAI values. It is designed for appropriately trained and authorised users. It is not an emergency service, not a substitute for clinical examination or professional judgement, and does not automatically classify a result as normal, abnormal, diagnostic, or treatment-indicating.
3. INFORMATION THE APP ACCESSES OR PROCESSES ON THE DEVICE
Only after a deliberate user action, the app may access and process:
• A user-selected image from Android Photos or a document provider.
• The first page of a user-selected PDF.
• A photograph created by an installed external camera application and written to a temporary, app-controlled content URI.
• Limited source metadata needed to open the item, such as its display name, MIME type, dimensions, and image orientation.
• The selector position, P1–P8 point coordinates, pan and zoom transforms, and the active landmark.
• Derived POTSI, FAI, and HAI values, component values, annotations, and a user-requested report or annotated PNG.
An image of a person’s back, its file name, the selected anatomical points, and derived measurements may be personal data, sensitive health-related data, or identifiable clinical information depending on the image and the user’s context.
4. HOW THE INFORMATION IS USED
The app uses the selected or captured image to display the measurement workspace, guide P1–P8 point selection, calculate the preserved geometric formulas, render labels and construction guides, and prepare a result only when the user requests save or share. The app does not use the image or measurements for advertising, behavioural profiling, cross-app tracking, or automated identity recognition.
5. LOCAL PROCESSING; NO AUTOMATIC ORTHOPRACTIS UPLOAD
The Android release is designed without an Internet permission, an Orthopractis account system, an advertising SDK, a tracking SDK, or a third-party analytics SDK. Potsi App does not automatically transmit selected images, camera photographs, point coordinates, calculations, or exports to Orthopractis. Orthopractis cannot remotely view or retrieve material that remains only in the app or on the user’s device.
6. PHOTOS, FILES, PDF, AND CAMERA ACCESS
Photo and document selection is performed through Android’s system picker or a compatible installed provider. The app requests only a scoped read grant for the item chosen by the user and does not request broad photo-library or storage access. The app does not retain a persistable document permission after the active selection workflow.
Camera capture is delegated to an installed camera application. Potsi App itself does not request the Android CAMERA runtime permission. The camera application receives a temporary, grant-scoped URI for the requested photograph. The camera provider and any selected photo or document provider operate under their own privacy terms.
7. STORAGE, RETENTION, AND DELETION
Active image data, point coordinates, transforms, and calculations are held for the current app session and are removed from the active workspace when the user closes or replaces the image, resets the work, or the app process ends. Potsi App does not create a cloud account, remote patient record, or automatic measurement-history database.
A temporary camera file is deleted after successful decoding or cancellation when possible. As a fallback, the app removes camera-cache files older than approximately two hours when cleanup runs. A temporary annotated image prepared for sharing is stored in app cache and cleanup removes share-cache files older than approximately twenty-four hours; Android may remove cache data earlier.
When the user chooses Save, the annotated PNG is written to the device’s Pictures/PotsiApp collection and remains there until the user or device administrator deletes it. When the user chooses Share, copies created by the selected recipient, messaging app, email app, nearby-sharing service, cloud provider, or institutional system remain under that destination’s retention and deletion rules. The original imported source remains under the control of its original Photos or Files provider.
Uninstalling Potsi App removes its app-private files and cache, subject to Android behaviour. It does not delete copies already saved to Pictures, exported, shared, backed up by another service, or received by another person.
8. USER-INITIATED SHARING AND THIRD PARTIES
Information leaves the app only after a deliberate action such as Save, Share, opening a web page, or composing an email. Android’s MediaStore, system share sheet, browser, email client, camera application, photo picker, document provider, and any destination selected by the user are separate services with their own privacy practices. Orthopractis does not receive a copy merely because the user saves or shares a result.
9. SUPPORT COMMUNICATIONS AND WEBSITE USE
If a user voluntarily contacts info@orthopractis.com, Orthopractis may receive the sender’s name, email address, organisation, device or app version information, the support message, and any attachment the sender chooses to include. Do not send identifiable patient photographs, medical record numbers, dates of birth, or confidential health records through ordinary support email. Use a synthetic or properly de-identified example.
Support correspondence is retained only as long as reasonably needed to answer the request, document follow-up, maintain security and product records, comply with legal duties, or establish, exercise, or defend legal claims, after which it is deleted or anonymised where appropriate. A user may request deletion of support material controlled by Orthopractis by emailing the privacy contact, subject to records that must be retained by law.
Opening an Orthopractis web page leaves the app. Website hosting, security logs, cookies, and contact forms are governed by the applicable website notice and settings.
10. SECURITY
The app reduces exposure by using local processing, no direct Internet permission, scoped Android content grants, a non-exported grant-controlled cache provider, read-only share grants, disabled app backup, bounded image decoding, and a privacy shield when the app leaves the foreground. No device, storage medium, or transfer method can be guaranteed completely secure. Users and deploying organisations remain responsible for device access controls, de-identification, authorised recipients, institutional storage, retention schedules, backups, and secure deletion.
11. PATIENTS, MINORS, AND AUTHORISATION
Potsi App is not directed to children as independent users. A clinician, parent, guardian, institution, researcher, or other responsible operator must obtain every permission, consent, legal basis, ethics approval, and institutional authorisation required before photographing, importing, measuring, storing, or sharing information about another person, including a minor. Acceptance of the app notice is not a substitute for patient consent or research consent.
12. USER CHOICES AND DATA RIGHTS
A user can decline the launch acknowledgement and close the app; avoid selecting or capturing an image; close or replace the active image; clear points; delete saved results from Pictures or another destination; remove shared copies where the destination permits; and uninstall the app to remove app-private data. Potsi App does not create user accounts, so there is no app account to delete.
Privacy rights vary by jurisdiction. Orthopractis can respond only regarding information it actually controls, such as support correspondence. Requests concerning copies held by a hospital, clinic, employer, cloud provider, recipient, or other destination must be addressed to that controller or provider.
13. DATA SALE, ADVERTISING, AND AUTOMATED DECISIONS
Orthopractis does not sell app-derived images, point coordinates, measurements, or reports. The app does not contain advertising, does not use app data for personalised advertising, and does not make an automated diagnosis, treatment recommendation, eligibility decision, or other decision producing legal or similarly significant effects.
14. INTERNATIONAL USE
Users and deploying organisations are responsible for determining whether their use is permitted in their jurisdiction and clinical or research setting. Where European data-protection law applies, the healthcare professional, clinic, hospital, university, or other organisation deciding why and how patient information is processed may act as the controller for that processing and must provide its own notices, legal basis, safeguards, retention rules, and data-subject procedures.
15. CHANGES TO THIS POLICY
We may update this Privacy Policy when app functionality, data practices, legal requirements, or platform rules change. The public page will show a revised effective date. Material changes should also be reflected in the in-app notice and Google Play declarations before the related release is submitted.
16. CONTACT AND DIRECT LINKS
Developer: ORTHOPRACTIS.COM S.M.P.C.
Website: https://www.orthopractis.com
Potsi App support: https://www.orthopractis.com/potsi-app
Potsi App Privacy Policy: https://www.orthopractis.com/potsi-app-privacy-policy
Potsi App Terms of Use: https://www.orthopractis.com/potsi-app-terms-of-use
Privacy and support email: info@orthopractis.com
SurfaceScan Privacy Policy
==========================
Wix-ready policy for iOS, iPadOS, visionOS, and Android
PUBLIC WEBSITE LEGAL COPY - REVIEW WITH COUNSEL BEFORE PUBLICATION
Prepared for Orthopractis.com SMPC | 24 August 2026
EFFECTIVE DATE
--------------
24 August 2026
1. SCOPE AND CONTROLLER
-----------------------
This Privacy Policy explains how SurfaceScan is designed to handle information on iPhone, iPad, Apple Vision Pro, and Android. SurfaceScan is provided by Orthopractis.com SMPC ("Orthopractis", "we", "us", or "our"). This policy applies to the SurfaceScan application, optional encrypted local iPhone-to-Vision pairing, and the SurfaceScan support page.
2. INFORMATION USED BY THE APP
------------------------------
To provide bounded surface capture, SurfaceScan uses camera RGB images, available device depth or spatial geometry, camera calibration, and device pose. These inputs are processed transiently to create points and meshes inside the user-selected three-dimensional box.
- SurfaceScan does not record microphone audio.
- SurfaceScan does not create an Orthopractis account.
- SurfaceScan does not use an Orthopractis advertising, tracking, or developer analytics service.
- SurfaceScan does not automatically upload scans to Orthopractis or to an Orthopractis cloud service.
3. LOCAL PROCESSING AND OPTIONAL NEARBY PAIRING
-----------------------------------------------
Capture, geometric fusion, colour projection, preview generation, quality adjustment, and PLY, OBJ, STL, or USDZ file creation are designed to run on the capture device. A local preference records the accepted notice version and timestamp for audit purposes but does not bypass the next-launch disclosure. In the Apple editions only, current-launch consent and required system permission automatically start a required-encryption Multipeer Connectivity session for compatible roles. The Android edition does not use this Apple live route. The Apple transport connection remains provisional until a SurfaceScan hello verifies the camera/viewer roles, Build 36, and protocol. Only after verification can capture controls, status, live RGB-D, a box-local preview, and a separately finalized protected mesh pass directly between nearby accepted Apple devices. Apple’s authoritative transport membership is checked immediately before every send; if a participant is gone, its queued chunks, partial transfers, preview/final work, and replaceable traffic are cancelled before bounded recovery and fresh verification. The route has no Orthopractis or cloud relay, and the live preview is never eligible for export.
4. EXPORTED AND SHARED FILES
----------------------------
Camera-derived data can leave an accepted iPhone or iPad through the encrypted nearby Apple Vision route described above. Otherwise, a scan leaves SurfaceScan only after the user deliberately selects Save or Share. Exported files may contain identifiable surface information, including colour, body contour, scars, tattoos, or other visible features. The user controls the nearby device, destination, recipient, retention, and deletion of those files.
- Save uses the operating system document picker.
- Share uses the operating system share interface, which may offer AirDrop, Quick Share, nearby devices, messaging, email, cloud storage, or another installed application.
- A selected third-party destination processes the file under its own privacy policy and terms.
- Orthopractis does not receive a copy merely because the user saves or shares a file.
5. TEMPORARY FILES AND RETENTION
--------------------------------
SurfaceScan may create a temporary file in an application-controlled cache while preparing a Save or Share action. The app removes the prepared Apple file after completion or cancellation. Android share-cache files are subject to application cleanup and are not intended as permanent storage. Files copied to Files, local storage, a cloud provider, or a recipient remain until deleted by the user or that provider.
6. ANDROID AND GOOGLE PLAY SERVICES FOR AR
------------------------------------------
The Android edition runs on Google Play Services for AR (ARCore), which is provided by Google and governed by the Google Privacy Policy. Google states that current ARCore automatically collects app-install-specific pseudonymous identifiers, performance and diagnostic data, and AR API usage data for analytics, service operation, and improvement. Google states that it does not share those categories with third parties.
- SurfaceScan does not use ARCore Cloud Anchors.
- SurfaceScan does not use the ARCore Geospatial API and does not request location permission.
- Orthopractis does not receive ARCore diagnostic or API-usage data directly through this app.
- See Google ARCore privacy requirements: https://developers.google.com/ar/develop/privacy-requirements
- See Google Privacy Policy: https://policies.google.com/privacy
7. PERMISSIONS
--------------
Camera: Required to capture RGB images and support AR/depth surface reconstruction.
Motion / device pose: Used to align overlapping observations in one coordinate system.
World sensing / scene reconstruction: Used by visionOS Standard and Enterprise to anchor the box and obtain public spatial geometry.
Local network / Bonjour: Used only after current-launch consent when compatible iPhone/iPad-to-Vision Pro discovery and streaming are active; the user can stop or disconnect the route.
Files / share interface: Invoked only after the user selects Save or Share.
8. SUBJECT PERMISSION AND SENSITIVE SURFACE CONTENT
---------------------------------------------------
Users must scan only themselves or a person who has given permission. Users should avoid intimate regions and unnecessary facial capture. Surface files should be treated as potentially sensitive and identifiable even though SurfaceScan does not perform face recognition, identity matching, diagnosis, or health profiling.
9. CHILDREN
-----------
SurfaceScan is not directed to children. A parent, guardian, clinician, researcher, educator, or other responsible adult must determine whether a minor may be scanned and must obtain any permission required by law, ethics approval, institutional policy, or professional duty.
10. SECURITY
------------
SurfaceScan reduces exposure by processing locally, avoiding an Orthopractis account or upload service, requiring encryption for the optional nearby paired session, validating peer role/build/protocol, bounding mesh transfers, using operating system file interfaces, and granting temporary read access to a selected share destination. No method of storage or transfer is completely secure. Users and deploying organizations are responsible for device security, nearby-device verification, recipient verification, access control, backup, retention, and secure deletion.
11. YOUR CHOICES
----------------
- Do not accept the launch notice or do not grant camera/world-sensing permission if you do not wish to use capture.
- Use the operating system Settings application to revoke permissions.
- Delete saved files from their destination and remove copies from recipients or cloud providers where possible.
- Delete the SurfaceScan app to remove app-local preferences and cache data, subject to operating system backup behavior.
12. INTERNATIONAL USERS AND LEGAL RIGHTS
----------------------------------------
Privacy rights vary by location. Because Orthopractis does not operate an account or scan-upload service in this version, it generally does not possess the user's scans. Requests concerning data held by a selected third-party destination must be directed to that provider. Questions about this policy may be sent to the contact below.
13. CHANGES
-----------
We may update this Privacy Policy when SurfaceScan features, SDKs, legal requirements, or data practices change. The effective date will be revised. Material changes may also be presented through an updated in-app consent notice.
14. CONTACT
-----------
Operator: Orthopractis.com SMPC
Website: https://www.orthopractis.com
Support page: https://www.orthopractis.com/surfacescan
Email: info@orthopractis.com
Privacy Policy: https://www.orthopractis.com/privacy
Terms of Use: https://www.orthopractis.com/terms-of-use
SurfaceScan Privacy Policy
==========================
Wix-ready policy for iOS, iPadOS, visionOS, and Android
PUBLIC WEBSITE LEGAL COPY - REVIEW WITH COUNSEL BEFORE PUBLICATION
Prepared for Orthopractis.com SMPC | 24 August 2026
EFFECTIVE DATE
--------------
24 August 2026
1. SCOPE AND CONTROLLER
-----------------------
This Privacy Policy explains how SurfaceScan is designed to handle information on iPhone, iPad, Apple Vision Pro, and Android. SurfaceScan is provided by Orthopractis.com SMPC ("Orthopractis", "we", "us", or "our"). This policy applies to the SurfaceScan application, optional encrypted local iPhone-to-Vision pairing, and the SurfaceScan support page.
2. INFORMATION USED BY THE APP
------------------------------
To provide bounded surface capture, SurfaceScan uses camera RGB images, available device depth or spatial geometry, camera calibration, and device pose. These inputs are processed transiently to create points and meshes inside the user-selected three-dimensional box.
- SurfaceScan does not record microphone audio.
- SurfaceScan does not create an Orthopractis account.
- SurfaceScan does not use an Orthopractis advertising, tracking, or developer analytics service.
- SurfaceScan does not automatically upload scans to Orthopractis or to an Orthopractis cloud service.
3. LOCAL PROCESSING AND OPTIONAL NEARBY PAIRING
-----------------------------------------------
Capture, geometric fusion, colour projection, preview generation, quality adjustment, and PLY, OBJ, STL, or USDZ file creation are designed to run on the capture device. A local preference records the accepted notice version and timestamp for audit purposes but does not bypass the next-launch disclosure. In the Apple editions only, current-launch consent and required system permission automatically start a required-encryption Multipeer Connectivity session for compatible roles. The Android edition does not use this Apple live route. The Apple transport connection remains provisional until a SurfaceScan hello verifies the camera/viewer roles, Build 36, and protocol. Only after verification can capture controls, status, live RGB-D, a box-local preview, and a separately finalized protected mesh pass directly between nearby accepted Apple devices. Apple’s authoritative transport membership is checked immediately before every send; if a participant is gone, its queued chunks, partial transfers, preview/final work, and replaceable traffic are cancelled before bounded recovery and fresh verification. The route has no Orthopractis or cloud relay, and the live preview is never eligible for export.
4. EXPORTED AND SHARED FILES
----------------------------
Camera-derived data can leave an accepted iPhone or iPad through the encrypted nearby Apple Vision route described above. Otherwise, a scan leaves SurfaceScan only after the user deliberately selects Save or Share. Exported files may contain identifiable surface information, including colour, body contour, scars, tattoos, or other visible features. The user controls the nearby device, destination, recipient, retention, and deletion of those files.
- Save uses the operating system document picker.
- Share uses the operating system share interface, which may offer AirDrop, Quick Share, nearby devices, messaging, email, cloud storage, or another installed application.
- A selected third-party destination processes the file under its own privacy policy and terms.
- Orthopractis does not receive a copy merely because the user saves or shares a file.
5. TEMPORARY FILES AND RETENTION
--------------------------------
SurfaceScan may create a temporary file in an application-controlled cache while preparing a Save or Share action. The app removes the prepared Apple file after completion or cancellation. Android share-cache files are subject to application cleanup and are not intended as permanent storage. Files copied to Files, local storage, a cloud provider, or a recipient remain until deleted by the user or that provider.
6. ANDROID AND GOOGLE PLAY SERVICES FOR AR
------------------------------------------
The Android edition runs on Google Play Services for AR (ARCore), which is provided by Google and governed by the Google Privacy Policy. Google states that current ARCore automatically collects app-install-specific pseudonymous identifiers, performance and diagnostic data, and AR API usage data for analytics, service operation, and improvement. Google states that it does not share those categories with third parties.
- SurfaceScan does not use ARCore Cloud Anchors.
- SurfaceScan does not use the ARCore Geospatial API and does not request location permission.
- Orthopractis does not receive ARCore diagnostic or API-usage data directly through this app.
- See Google ARCore privacy requirements: https://developers.google.com/ar/develop/privacy-requirements
- See Google Privacy Policy: https://policies.google.com/privacy
7. PERMISSIONS
--------------
Camera: Required to capture RGB images and support AR/depth surface reconstruction.
Motion / device pose: Used to align overlapping observations in one coordinate system.
World sensing / scene reconstruction: Used by visionOS Standard and Enterprise to anchor the box and obtain public spatial geometry.
Local network / Bonjour: Used only after current-launch consent when compatible iPhone/iPad-to-Vision Pro discovery and streaming are active; the user can stop or disconnect the route.
Files / share interface: Invoked only after the user selects Save or Share.
8. SUBJECT PERMISSION AND SENSITIVE SURFACE CONTENT
---------------------------------------------------
Users must scan only themselves or a person who has given permission. Users should avoid intimate regions and unnecessary facial capture. Surface files should be treated as potentially sensitive and identifiable even though SurfaceScan does not perform face recognition, identity matching, diagnosis, or health profiling.
9. CHILDREN
-----------
SurfaceScan is not directed to children. A parent, guardian, clinician, researcher, educator, or other responsible adult must determine whether a minor may be scanned and must obtain any permission required by law, ethics approval, institutional policy, or professional duty.
10. SECURITY
------------
SurfaceScan reduces exposure by processing locally, avoiding an Orthopractis account or upload service, requiring encryption for the optional nearby paired session, validating peer role/build/protocol, bounding mesh transfers, using operating system file interfaces, and granting temporary read access to a selected share destination. No method of storage or transfer is completely secure. Users and deploying organizations are responsible for device security, nearby-device verification, recipient verification, access control, backup, retention, and secure deletion.
11. YOUR CHOICES
----------------
- Do not accept the launch notice or do not grant camera/world-sensing permission if you do not wish to use capture.
- Use the operating system Settings application to revoke permissions.
- Delete saved files from their destination and remove copies from recipients or cloud providers where possible.
- Delete the SurfaceScan app to remove app-local preferences and cache data, subject to operating system backup behavior.
12. INTERNATIONAL USERS AND LEGAL RIGHTS
----------------------------------------
Privacy rights vary by location. Because Orthopractis does not operate an account or scan-upload service in this version, it generally does not possess the user's scans. Requests concerning data held by a selected third-party destination must be directed to that provider. Questions about this policy may be sent to the contact below.
13. CHANGES
-----------
We may update this Privacy Policy when SurfaceScan features, SDKs, legal requirements, or data practices change. The effective date will be revised. Material changes may also be presented through an updated in-app consent notice.
14. CONTACT
-----------
Operator: Orthopractis.com SMPC
Website: https://www.orthopractis.com
Support page: https://www.orthopractis.com/surfacescan
Email: info@orthopractis.com
Privacy Policy: https://www.orthopractis.com/privacy
Terms of Use: https://www.orthopractis.com/terms-of-use
SkinScanMedical Privacy Policy
==============================
Wix-ready policy for iOS, iPadOS, visionOS, and Android
PUBLIC WEBSITE LEGAL COPY - REVIEW WITH COUNSEL BEFORE PUBLICATION
Prepared for Orthopractis.com SMPC | 18 August 2026
EFFECTIVE DATE
--------------
18 August 2026
1. SCOPE AND CONTROLLER
-----------------------
This Privacy Policy explains how SkinScanMedical is designed to handle information on iPhone, iPad, Apple Vision Pro, and Android. SkinScanMedical is provided by Orthopractis.com SMPC ("Orthopractis", "we", "us", or "our"). This policy applies to the SkinScanMedical application and the SkinScanMedical support page.
2. INFORMATION USED BY THE APP
------------------------------
To provide bounded surface capture, SkinScanMedical uses camera RGB images, available device depth or spatial geometry, camera calibration, and device pose. These inputs are processed transiently to create points and meshes inside the user-selected three-dimensional box.
- SkinScanMedical does not record microphone audio.
- SkinScanMedical does not create an Orthopractis account.
- SkinScanMedical does not use an Orthopractis advertising, tracking, or developer analytics service.
- SkinScanMedical does not automatically upload scans to Orthopractis or to an Orthopractis cloud service.
3. LOCAL PROCESSING
-------------------
Capture, geometric fusion, colour projection, preview generation, quality adjustment, and PLY, OBJ, STL, or USDZ file creation are designed to run on the device. A local preference records the version of the consent notice accepted on that device.
BASELINE, FOLLOW-UP, LANDMARKS, AND IMPORTED FILES
--------------------------------------------------
Build 15 can store protected baseline/follow-up sessions locally and import a user-selected PLY. These data can include geometry, colour, landmarks, protocol labels, box dimensions, registration results, and comparison reports. They are potentially identifiable and remain under the user or deploying organization's control.
4. EXPORTED AND SHARED FILES
----------------------------
A scan leaves SkinScanMedical only after the user deliberately selects Save or Share. Exported files may contain identifiable surface information, including colour, body contour, scars, tattoos, or other visible features. The user controls the destination, recipient, retention, and deletion of those files.
- Save uses the operating system document picker.
- Share uses the operating system share interface, which may offer AirDrop, Quick Share, nearby devices, messaging, email, cloud storage, or another installed application.
- A selected third-party destination processes the file under its own privacy policy and terms.
- Orthopractis does not receive a copy merely because the user saves or shares a file.
5. TEMPORARY FILES AND RETENTION
--------------------------------
SkinScanMedical may create a temporary file in an application-controlled cache while preparing a Save or Share action. The app removes the prepared Apple file after completion or cancellation. Android share-cache files are subject to application cleanup and are not intended as permanent storage. Files copied to Files, local storage, a cloud provider, or a recipient remain until deleted by the user or that provider.
6. ANDROID AND GOOGLE PLAY SERVICES FOR AR
------------------------------------------
The Android edition runs on Google Play Services for AR (ARCore), which is provided by Google and governed by the Google Privacy Policy. Google states that current ARCore automatically collects app-install-specific pseudonymous identifiers, performance and diagnostic data, and AR API usage data for analytics, service operation, and improvement. Google states that it does not share those categories with third parties.
- SkinScanMedical does not use ARCore Cloud Anchors.
- SkinScanMedical does not use the ARCore Geospatial API and does not request location permission.
- Orthopractis does not receive ARCore diagnostic or API-usage data directly through this app.
- See Google ARCore privacy requirements: https://developers.google.com/ar/develop/privacy-requirements
- See Google Privacy Policy: https://policies.google.com/privacy
7. PERMISSIONS
--------------
Camera: Required to capture RGB images and support AR/depth surface reconstruction.
Motion / device pose: Used to align overlapping observations in one coordinate system.
World sensing / scene reconstruction: Used by visionOS Standard and Enterprise to anchor the box and obtain public spatial geometry.
Files / share interface: Invoked only after the user selects Save or Share.
8. SUBJECT PERMISSION AND SENSITIVE SURFACE CONTENT
---------------------------------------------------
Users must scan only themselves or a person who has given permission. Users should avoid intimate regions and unnecessary facial capture. Surface files should be treated as potentially sensitive and identifiable even though SkinScanMedical does not perform face recognition, identity matching, diagnosis, or health profiling.
9. CHILDREN
-----------
SkinScanMedical is not directed to children. A parent, guardian, clinician, researcher, educator, or other responsible adult must determine whether a minor may be scanned and must obtain any permission required by law, ethics approval, institutional policy, or professional duty.
10. SECURITY
------------
SkinScanMedical reduces exposure by processing locally, avoiding an Orthopractis account or upload service, using operating system file interfaces, and granting temporary read access to a selected share destination. No method of storage or transfer is completely secure. Users and deploying organizations are responsible for device security, recipient verification, access control, backup, retention, and secure deletion.
11. YOUR CHOICES
----------------
- Do not accept the launch notice or do not grant camera/world-sensing permission if you do not wish to use capture.
- Use the operating system Settings application to revoke permissions.
- Delete saved files from their destination and remove copies from recipients or cloud providers where possible.
- Delete the SkinScanMedical app to remove app-local preferences and cache data, subject to operating system backup behavior.
12. INTERNATIONAL USERS AND LEGAL RIGHTS
----------------------------------------
Privacy rights vary by location. Because Orthopractis does not operate an account or scan-upload service in this version, it generally does not possess the user's scans. Requests concerning data held by a selected third-party destination must be directed to that provider. Questions about this policy may be sent to the contact below.
13. CHANGES
-----------
We may update this Privacy Policy when SkinScanMedical features, SDKs, legal requirements, or data practices change. The effective date will be revised. Material changes may also be presented through an updated in-app consent notice.
14. CONTACT
-----------
Operator: Orthopractis.com SMPC
Website: https://www.orthopractis.com
Support page: https://www.orthopractis.com/skinscan
Email: info@orthopractis.com
Privacy Policy: https://www.orthopractis.com/privacy
Terms of Use: https://www.orthopractis.com/terms-of-use
SkinScan Privacy Policy
=======================
Wix-ready policy for iOS, iPadOS, visionOS, and Android
PUBLIC WEBSITE LEGAL COPY - REVIEW WITH COUNSEL BEFORE PUBLICATION
Prepared for Orthopractis.com SMPC | 19 August 2026
EFFECTIVE DATE
--------------
19 August 2026
1. SCOPE AND CONTROLLER
-----------------------
This Privacy Policy explains how SkinScan is designed to handle information on iPhone, iPad, Apple Vision Pro, and Android. SkinScan is provided by Orthopractis.com SMPC ("Orthopractis", "we", "us", or "our"). This policy applies to the SkinScan application and the SkinScan support page.
2. INFORMATION USED BY THE APP
------------------------------
To provide bounded surface capture, SkinScan uses camera RGB images, available device depth or spatial geometry, camera calibration, and device pose. These inputs are processed transiently to create points and meshes inside the user-selected three-dimensional box.
- SkinScan does not record microphone audio.
- SkinScan does not create an Orthopractis account.
- SkinScan does not use an Orthopractis advertising, tracking, or developer analytics service.
- SkinScan does not automatically upload scans to Orthopractis or to an Orthopractis cloud service.
3. LOCAL PROCESSING
-------------------
Capture, geometric fusion, colour projection, preview generation, quality adjustment, and PLY, OBJ, STL, or USDZ file creation are designed to run on the device. A local preference records the version of the consent notice accepted on that device.
4. EXPORTED AND SHARED FILES
----------------------------
A scan leaves SkinScan only after the user deliberately selects Save or Share. Exported files may contain identifiable surface information, including colour, body contour, scars, tattoos, or other visible features. The user controls the destination, recipient, retention, and deletion of those files.
- Save uses the operating system document picker.
- Share uses the operating system share interface, which may offer AirDrop, Quick Share, nearby devices, messaging, email, cloud storage, or another installed application.
- A selected third-party destination processes the file under its own privacy policy and terms.
- Orthopractis does not receive a copy merely because the user saves or shares a file.
5. TEMPORARY FILES AND RETENTION
--------------------------------
SkinScan may create a temporary file in an application-controlled cache while preparing a Save or Share action. The app removes the prepared Apple file after completion or cancellation. Android share-cache files are subject to application cleanup and are not intended as permanent storage. Files copied to Files, local storage, a cloud provider, or a recipient remain until deleted by the user or that provider.
6. ANDROID AND GOOGLE PLAY SERVICES FOR AR
------------------------------------------
The Android edition runs on Google Play Services for AR (ARCore), which is provided by Google and governed by the Google Privacy Policy. Google states that current ARCore automatically collects app-install-specific pseudonymous identifiers, performance and diagnostic data, and AR API usage data for analytics, service operation, and improvement. Google states that it does not share those categories with third parties.
- SkinScan does not use ARCore Cloud Anchors.
- SkinScan does not use the ARCore Geospatial API and does not request location permission.
- Orthopractis does not receive ARCore diagnostic or API-usage data directly through this app.
- See Google ARCore privacy requirements: https://developers.google.com/ar/develop/privacy-requirements
- See Google Privacy Policy: https://policies.google.com/privacy
7. PERMISSIONS
--------------
Camera: Required to capture RGB images and support AR/depth surface reconstruction.
Motion / device pose: Used to align overlapping observations in one coordinate system.
World sensing / scene reconstruction: Used by visionOS Standard and Enterprise to anchor the box and obtain public spatial geometry.
Files / share interface: Invoked only after the user selects Save or Share.
8. SUBJECT PERMISSION AND SENSITIVE SURFACE CONTENT
---------------------------------------------------
Users must scan only themselves or a person who has given permission. Users should avoid intimate regions and unnecessary facial capture. Surface files should be treated as potentially sensitive and identifiable even though SkinScan does not perform face recognition, identity matching, diagnosis, or health profiling.
9. CHILDREN
-----------
SkinScan is not directed to children. A parent, guardian, clinician, researcher, educator, or other responsible adult must determine whether a minor may be scanned and must obtain any permission required by law, ethics approval, institutional policy, or professional duty.
10. SECURITY
------------
SkinScan reduces exposure by processing locally, avoiding an Orthopractis account or upload service, using operating system file interfaces, and granting temporary read access to a selected share destination. No method of storage or transfer is completely secure. Users and deploying organizations are responsible for device security, recipient verification, access control, backup, retention, and secure deletion.
11. YOUR CHOICES
----------------
- Do not accept the launch notice or do not grant camera/world-sensing permission if you do not wish to use capture.
- Use the operating system Settings application to revoke permissions.
- Delete saved files from their destination and remove copies from recipients or cloud providers where possible.
- Delete the SkinScan app to remove app-local preferences and cache data, subject to operating system backup behavior.
12. INTERNATIONAL USERS AND LEGAL RIGHTS
----------------------------------------
Privacy rights vary by location. Because Orthopractis does not operate an account or scan-upload service in this version, it generally does not possess the user's scans. Requests concerning data held by a selected third-party destination must be directed to that provider. Questions about this policy may be sent to the contact below.
13. CHANGES
-----------
We may update this Privacy Policy when SkinScan features, SDKs, legal requirements, or data practices change. The effective date will be revised. Material changes may also be presented through an updated in-app consent notice.
14. CONTACT
-----------
Operator: Orthopractis.com SMPC
Website: https://www.orthopractis.com
Support page: https://www.orthopractis.com/skinscan
Email: info@orthopractis.com
Privacy Policy: https://www.orthopractis.com/privacy
Terms of Use: https://www.orthopractis.com/terms-of-use
OrthoTennis 2.3.0 · Build 23
Prepared 16 August 2026
OrthoTennis is designed for local processing and local storage. It contains no advertising SDK, tracking SDK, developer analytics service, user account system or developer-operated cloud upload. Selected Photos/Files videos and retained camera recordings are stored in the private app container as user-managed case evidence until deleted. Data leaves a device only when the user deliberately exports or shares a file, contacts support, or enables encrypted nearby-device pairing.
1. Scope and controller
This policy applies to OrthoTennis for iPhone, iPad and Apple Vision Pro. The product is provided by ORTHOPRACTIS.COM SINGLE MEMBER P.C. Questions and privacy requests may be sent to info@orthopractis.com.
2. Data processed by the app
Depending on the features selected, the app may process live camera frames, deliberately selected Photo Library or Files videos, retained case recordings, pose landmarks, body-part confidence, tennis-ball observations, camera calibration, stereo points, motion measurements, player names or codes, team names, session notes, time-coded analysis sidecars and generated reports. These items are processed for app functionality and remain under the user’s control.
3. On-device processing
Skeleton recognition, ball recognition, Kalman filtering, motion analysis, session calculations and report generation are performed on the device. The app does not automatically upload camera frames, imported video, player records or reports to an Orthopractis server.
4. Nearby Apple-device pairing
When pairing is enabled, the iPhone or iPad and Apple Vision Pro communicate over an encrypted local Multipeer Connectivity session. The paired path transmits derived pose, ball, stereo, marker and operational-status observations. Raw paired-camera pixels and evidence-video files are not sent through this path. The developer does not receive the paired traffic.
5. Local storage and retention
Players, teams, sessions, recognition preferences, retained case videos and synchronized analysis sidecars are stored in the app’s local container. A selected Photos or Files movie is copied into app-owned case storage before analysis; external security-scoped access is then released. Retention continues until the user deletes the managed video, deletes its session, removes the app, or manages an exported copy separately. Measurements-only recording does not retain a case movie.
6. User-directed export and support
CSV, JSON, case video or other files leave the app only when the user invokes an export or system share action. Shared copies are controlled by the selected destination and cannot be recalled by OrthoTennis. Information voluntarily sent by email to support is processed only to answer the request and maintain necessary business records.
7. No tracking or advertising
The app does not use information for cross-app tracking, targeted advertising, data brokerage or behavioural profiling. It contains no advertising network and no developer-operated analytics SDK.
8. Permissions
Camera permission is used for live tennis capture. Photo Library and document-provider access is used only for a video deliberately selected by the user. Local-network permission is used for nearby Apple-device pairing. Vision Pro Enterprise camera and world-sensing access is used only in the separately entitled Enterprise target.
9. Children and recorded athletes
A parent, guardian, club or authorised operator should supervise use involving minors. The operator must have a lawful basis and appropriate consent to record and analyse every athlete. The app is not designed to create an online profile of a child and does not transmit youth-player data to the developer.
10. Security
The app uses Apple platform sandboxing, local file protection provided by the operating system, and encrypted Multipeer Connectivity for paired observations. No security method can guarantee absolute protection; users should protect their devices, exports and backups.
11. Deletion and privacy choices
Users can delete individual managed case videos and their analysis sidecars, delete complete sessions and case directories inside the app, delete exported copies in their destination, and remove all app-held data by deleting the app. Deleting an in-app case video does not remove or recall copies previously exported or shared. For support-email records or other information directly supplied to Orthopractis, users may request access, correction or deletion at info@orthopractis.com, subject to legal retention obligations.
12. International and legal rights
Where applicable, users may have rights under the GDPR or other privacy laws, including access, correction, deletion, restriction, objection and data portability. Because core app records are stored locally and are not available to the developer, many requests can be completed directly on the user's device.
13. Changes
The policy may be updated when functionality or legal requirements change. The effective date displayed in the app and on the published privacy page identifies the current version.
Website: https://www.orthopractis.com
Support: https://www.orthopractis.com/orthotenis
Privacy: https://www.orthopractis.com/privacy
Terms: https://www.orthopractis.com/terms-of-use
Email: info@orthopractis.com
ORTHOGAIT JR PRIVACY POLICY
Effective date: August 14, 2026
1. WHO WE ARE
OrthoGait JR is provided by ORTHOPRACTIS.COM S.M.P.C. (Monoprosopi IKE), Greece. Contact: info@orthopractis.com. Website: https://www.orthopractis.com. Support: https://www.orthopractis.com/orthogait-jr.
2. SCOPE
This policy describes how the OrthoGait JR applications for iPhone, iPad, and Apple Vision Pro handle information. It covers clinician-guided assessment, patient self-test workflows, live camera capture, locally retained evidence, imported images and videos, reprocessing, reports, local-network pairing, subscriptions, and local stability diagnostics.
3. LOCAL-FIRST DESIGN
The released application is designed to operate without an Orthopractis account and without automatically uploading patient or clinical information to an Orthopractis server. Patient records, case codes, clinician information, procedure and side, symptoms, notes, movement estimates, imported media, silent case videos, pose traces, thumbnails, processing settings, quality checks, reports, and evidence packages are stored in the app’s protected local container unless an authorized user deliberately exports or shares them.
The app performs body-pose recognition, stabilization, metric calculation, quality assessment, report generation, and media reprocessing on the device. The source release does not include advertising, behavioral profiling, cross-app tracking, or a third-party analytics service. StoreKit transactions are processed by Apple under Apple’s policies; the app evaluates verified transaction entitlements locally.
4. INFORMATION HANDLED ON THE DEVICE
Depending on the features used, the app may handle:
• Patient/case identifiers and optional demographic or clinical context entered by an authorized user.
• Clinician name, role, professional identifier, and clinic branding.
• Procedure, operated side, recovery phase, protocol tasks, assistance, safety authorization, symptoms, notes, and quality decisions.
• Camera frames while live capture is active, body landmarks, derived movement estimates, gait events, confidence, and quality indicators.
• Silent case video, pose JSONL traces, measurement CSV files, thumbnails, processing metadata, and file-integrity hashes when evidence retention is selected.
• Images or videos selected through the system document or photo interface. The original is copied into protected app storage before analysis. Audio removal from imported video is best effort; the app warns when audio may remain.
• Locally generated PDF, CSV, JSON, research, and complete-case export packages.
• Bounded, patient-data-free stability diagnostics recording launch and handled-error events.
5. CAMERA, PHOTOS, FILES, WORLD SENSING, AND LOCAL NETWORK
Camera access is requested only when a user starts live capture or a compatible system-camera workflow. Microphone access is not requested for live evidence recording. File and photo access occurs only after a user selects content using the system interface.
The Apple Vision Pro Enterprise configuration can use Apple-approved main-camera and world-sensing capabilities only when the app, entitlement, provisioning profile, license, and device authorization permit it. The ordinary visionOS build remains usable through paired iPhone/iPad capture, imported media, saved cases, and immersive review.
When the user starts paired operation, devices on the same trusted local network may exchange abstract body-joint, metric, confidence, quality, recognizer, and protocol-state packets. Normal paired operation does not transmit raw camera images or case video to Orthopractis. This device-to-device function is controlled by the user.
6. EXPORT AND SHARING
The app shares information only when an authorized user deliberately invokes an export or share action. Exports can contain identifiable health information, media, clinician details, or patient codes. The user or responsible organization chooses the destination and is responsible for recipient authorization, secure transfer, retention, deletion, and compliance with professional and legal duties. Complete-case ZIP files are portable and are not represented as encrypted containers.
7. DATA COLLECTION FOR APP STORE PRIVACY DISCLOSURE
Apple defines “collection” for the App Store privacy label as transmitting data off the device in a manner that allows the developer or a third-party partner to access it for longer than necessary to service a real-time request. In the audited Build 135 source, clinical and media processing is on-device and no Orthopractis clinical-data backend, advertising SDK, or analytics SDK is present. Subject to verification of the final signed archive, dependency privacy reports, and production configuration, the recommended App Store Connect answer is “No, we do not collect data from this app.” If any future release introduces a server, remote support upload, analytics, crash reporting, cloud synchronization, or another third-party data path, the privacy label and this policy must be updated before release.
8. RETENTION
Local records remain until an authorized user deletes an attempt, media item, assessment, or patient where deletion is permitted; clears the app’s storage; or uninstalls the app. Some deletion operations are restricted when linked clinical history must remain internally consistent. Exported copies and files shared to another app, device, organization, backup, or recipient are outside the app’s control and must be deleted separately.
9. DELETION AND PRIVACY CHOICES
Inside the app, authorized users can delete eligible media, processing runs, attempts, assessments, and unlinked patients; archive or restore patients; disable spoken guidance; choose whether case video is retained; decline camera permission; and stop local-network pairing. Device permissions can also be changed in Apple Settings. For questions or a request concerning information directly held by Orthopractis through support correspondence, contact info@orthopractis.com. Because patient records are normally stored only on the user’s device, Orthopractis usually cannot retrieve or delete them remotely.
10. SECURITY
The app uses Apple app-container isolation, local file-protection attributes, bounded resources, transactional media commits, and integrity hashes for evidence inventory. No storage system can be guaranteed absolutely secure. Users should maintain device passcodes, current system updates, appropriate backups and organizational controls, and should not share identifiable exports through insecure channels.
11. CHILDREN, PATIENT SELF-TEST, AND EMERGENCIES
The app is not directed to children. Patient self-testing must be authorized for the specific case, performed only when clinically permitted, and stopped for concerning symptoms or unsafe conditions. The app is not an emergency service. Urgent symptoms require appropriate local emergency or clinical care.
12. THIRD-PARTY AND APPLE SERVICES
Apple may process App Store purchases, subscriptions, system permissions, diagnostics chosen in Apple settings, and other platform services under Apple’s own policies. Bundled pose/runtime components are used for app functionality. The developer must review the Xcode Privacy Report and all dependency manifests for every release.
13. INTERNATIONAL USE
The responsible clinician or organization must determine whether use, retention, export, and patient self-testing are lawful and clinically appropriate in the applicable country, institution, and care setting.
14. CHANGES
This policy may be updated for feature, security, legal, or platform changes. The effective date and public website copy should be updated before the related app version is submitted.
15. CONTACT
ORTHOPRACTIS.COM S.M.P.C. (Monoprosopi IKE)
Website: https://www.orthopractis.com
Support: https://www.orthopractis.com/orthogait-jr
Privacy choices: https://www.orthopractis.com/privacy
Email: info@orthopractis.com
ORTHOGAIT JR PRIVACY CHOICES AND DELETION
• Decline or revoke Camera permission in Apple Settings.
• Do not start paired-device local networking, or stop the connection from the app.
• Choose Ask Every Task, Always Save, or Never Save for case video.
• Disable spoken protocol guidance.
• Import only media that is authorized and necessary.
• Delete eligible media items and processing runs in Case Media.
• Delete eligible attempts/assessments or archive/restore patients according to the app’s consistency rules.
• Use the consent reset control on the launch page to require a new acknowledgement.
• Uninstall the app to remove its local container, subject to any separate device backup behavior.
• Delete exported copies separately from Files, email, cloud storage, institutional systems, or recipient devices.
OrthoGait JR normally stores patient data only on the user’s device. Orthopractis therefore generally cannot view, retrieve, correct, or delete those local records remotely. For information held directly by Orthopractis through a support message, contact info@orthopractis.com.
ORTHOTENIS PRIVACY POLICY
Page URL to use: https://www.orthopractis.com/privacy
Support page: https://www.orthopractis.com/OrthoTenis
Contact: info@orthopractis.com
OrthoTenis is a tennis player and team performance-analysis application. The app uses the device camera or user-selected video/image media to estimate body movement, ball movement, contact events and quality measurements for tennis training documentation.
What we process:
- player/team profile information entered by the user;
- recorded or imported video/image media selected by the user;
- pose landmarks, ball observations, contact/bounce candidates, calibration and measurement outputs;
- export files generated by the user;
- Google Play Billing entitlement information when subscriptions are used.
Where processing occurs:
Analysis principally runs on the device. Retained media and results are stored locally in app-managed storage unless the user exports them. The user controls export through the Android share sheet.
Consent:
The operator must have permission to record and analyse every player. For minors, clubs, schools and teams, guardian/team/club permission may be required.
Deletion:
Deleting a session removes the app-managed result and retained media copy. Exported files outside the app must be deleted separately by the user.
No ads:
This build does not include advertising SDKs. This build does not sell player data.
Limitations:
OrthoTenis is not a medical device, not a diagnosis/treatment tool and not electronic line calling.
ORTHOGAIT JR PRIVACY POLICY
=================================================
Effective date: 1 August 2026
App version referenced: 1.1.0
1. WHO WE ARE
-------------
OrthoGait JR is provided by ORTHOPRACTIS.COM SINGLE MEMBER P.C. (“Orthopractis”).
Website: https://www.orthopractis.com
Product and support: https://www.orthopractis.com/orthogait-jr
Email: info@orthopractis.com
A clinic, hospital, research institution, clinician, or other organization using OrthoGait JR may be a separate data controller for the patient and staff information it enters, captures, stores, exports, or shares. That organization is responsible for its lawful basis, privacy information, professional secrecy, access controls, retention schedule, research approvals, and data-subject requests.
2. PURPOSE OF ORTHOGAIT JR
--------------------------
OrthoGait JR supports total knee arthroplasty (TKA) and total hip arthroplasty (THA) recovery assessments, standardized movement tasks, camera-based pose estimation, capture-quality review, patient and clinician records, baseline-to-follow-up comparison, reports, advanced movement tools, optional calibrated two-phone triangulation, and Google Play subscription access.
3. INFORMATION PROCESSED ON THE DEVICE
--------------------------------------
Depending on the functions selected, the app may process:
- live camera frames or a user-selected image;
- estimated body landmarks, confidence, timing, frame, orientation, and calibration data;
- derived gait, joint, pelvis, trunk, spine, balance, quality, and functional measurements;
- patient code, name, date of birth, sex, height, mass, notes, procedure, operated side, surgery date, follow-up phase, assistive device, pain score, KOOS JR or HOOS JR value, clinician interpretation, and patient summary;
- clinician name, role, email, and professional registration information;
- locally generated PDF, CSV, and research exports;
- settings and subscription entitlement state.
4. CAMERA AND ON-DEVICE PROCESSING
----------------------------------
Camera permission is requested for live capture. OrthoGait JR does not request background camera access. Pose estimation is designed to run on the Android device. The standard single-phone workflow does not intentionally upload raw movement video or the clinical database to an Orthopractis clinical-data server.
5. OPTIONAL TWO-PHONE MODE
--------------------------
When the user explicitly enables the paired workflow, the Secondary phone sends normalized pose landmarks, confidence values, frame metadata, timestamps, orientation, and calibration information to the Primary phone over the selected local network. The current socket does not intentionally send raw video, patient names, reports, or the app database. It is not TLS-encrypted. Use this function only on a trusted private network and never expose the port to the public internet.
6. LOCAL STORAGE AND BACKUP
---------------------------
Patient, clinician, assessment, session, optional landmark-sample, and settings data are stored in the app’s private Android storage. The database is protected by the Android application sandbox; Orthopractis does not claim separate database-level encryption. Security also depends on Android device encryption, a secure passcode or biometrics, supported software, and the deploying organization’s controls.
The app disables Android application backup and the supplied extraction rules exclude the clinical database and export directory. Organizations must still verify their actual managed-device, device-transfer, retention, and backup configuration.
7. GOOGLE PLAY SUBSCRIPTIONS
----------------------------
Google Play processes payment transactions. Orthopractis does not receive the user’s full payment-card details. The app may process product and base-plan identifiers, offer information, purchase token, order ID, purchase time, subscription state, expiry, automatic-renewal state, acknowledgement state, app package, and app version to display, restore, and verify paid access.
Production paid access is designed to require an Orthopractis-controlled HTTPS verification service. The service may retain protected or hashed purchase/order identifiers and subscription lifecycle state for entitlement, support, fraud prevention, accounting, dispute handling, and audit. It is not intended to receive patient records or movement video.
8. REPORTS AND SHARING
----------------------
PDF, CSV, and research exports are created only after a user command. Android’s share interface lets the user select the destination. The selected recipient or service controls subsequent processing. Exported or previously shared copies must be protected and deleted at their destination separately.
Deidentification reduces but does not eliminate reidentification risk, especially for landmark trajectories, dates, unusual clinical combinations, and free-text notes.
9. WHY INFORMATION IS PROCESSED
-------------------------------
Information is processed to provide the requested assessment, calculate and display measurements, evaluate capture quality, store and compare authorized records, create requested reports, operate paired-device functionality, provide and restore subscription access, prevent misuse or fraud, troubleshoot support issues, and meet legal or accounting obligations.
10. DATA MINIMISATION
---------------------
Enter only information necessary for the authorized purpose. Prefer a coded patient identifier when names are not required. Do not record covertly. Avoid unnecessary sensitive free text. The deploying organization must establish its own lawful basis, patient information or consent, access controls, research ethics where applicable, and retention rules.
11. RETENTION AND DELETION
--------------------------
Authorized users can delete local sessions, assessments, patients, and clinicians through the app. Deleting the app or clearing app data removes local app-private records, but it does not remove files that were exported or shared elsewhere.
Purchase-verification data may be retained during the subscription and for a reasonable period afterward where required for support, fraud prevention, accounting, disputes, or legal compliance. Requests may be sent to info@orthopractis.com. A clinic or institution should define and document its own clinical retention schedule.
12. SECURITY
------------
Use a supported and updated Android device protected by passcode or biometrics. Restrict access to authorized personnel, secure exports, avoid public Wi-Fi for paired capture, and follow the organization’s incident-response process.
13. CHILDREN AND VULNERABLE PERSONS
-----------------------------------
The app is designed for trained adult professional users and is not directed to children. Assessment of a minor or a person unable to provide authorization must follow applicable consent, safeguarding, supervision, and legal requirements.
14. INTERNATIONAL AND REGULATORY USE
------------------------------------
Privacy, medical-device, professional, research, and record-retention laws vary. The deploying organization is responsible for determining its controller/processor role, lawful basis, international-transfer safeguards, processor agreements, and any regulatory status applicable to its use.
15. YOUR RIGHTS AND CONTACT
---------------------------
To ask about Orthopractis-held subscription/support information, request access, correction, restriction, or deletion where applicable, contact:
ORTHOPRACTIS.COM SINGLE MEMBER P.C.
Email: info@orthopractis.com
Website: https://www.orthopractis.com
Support: https://www.orthopractis.com/orthogait-jr
For patient information held only by a clinic or institution, contact that organization directly.
16. CHANGES TO THIS POLICY
--------------------------
We may update this policy when app functions, data flows, providers, or legal requirements change. The public policy, in-app notice, Google Play Data safety form, Health apps declaration, and actual production behavior should remain consistent.
TOUCH3D SCAN PRIVACY POLICY
Effective date: 30 July 2026
App version covered: Touch3D Scan 1.9 for Apple Vision Pro
Publisher: ORTHOPRACTIS.COM SINGLE MEMBER P.C.
1. SCOPE
This section explains how Touch3D Scan handles information in the submitted Apple Vision Pro build. It applies to the app’s volume viewer, slice controls, registration workflows, Hand and optional Muse input, SAM request export, reviewed surface-manifest import, user-initiated exports, support links, and related website support.
This Touch3D Scan section should appear prominently near the top of the public Privacy Policy page. It should not be hidden among unrelated policies for other applications.
2. INTENDED USE
Touch3D Scan is intended for visualization, education, research, demonstration, engineering evaluation, and software testing. It is not a certified diagnostic workstation or a cleared surgical-navigation system and must not be the sole basis for diagnosis, treatment, surgery, emergency care, or another medical decision.
3. NO ACCOUNT, ADVERTISING, OR BEHAVIORAL TRACKING
The submitted build:
• does not require an Orthopractis account or login;
• does not include advertising;
• does not include behavioral or cross-app tracking;
• does not include an Orthopractis analytics service;
• does not include an automatic patient-study upload service;
• does not sell app data.
The app privacy manifest declares tracking as false and contains no collected-data entries for developer transmission.
4. INFORMATION PROCESSED LOCALLY
Depending on the operator’s choices, the app may locally process:
• CT, MRI, DICOM, NRRD/NHDR, NIfTI, MetaImage, RAW, VTK/VTI, image-stack, mesh, glTF/GLB, USD, or related user-selected files;
• file names and technical metadata needed to open a selected study;
• dimensions, voxel spacing, orientation, intensity range, modality, series description, crop, downsampling, and rendering settings;
• window/level, opacity, transfer-function, clipping, slice, slab, Cine, stack, and presentation settings;
• scan-side point A coordinates;
• patient-space point B coordinates captured through Hand or optional Muse tracking;
• surface-trace points, zone labels, model-surface samples, surface normals, and correspondence data;
• software transformations, residuals, inliers, rejected points, quality gates, coverage, and independent holdouts;
• SAM prompt descriptions, study fingerprints, requests, and reviewed surface manifests selected or exported by the user;
• Help, training, consent, and interface state for the current running session.
This information may be sensitive health or biometric-context information when it relates to an identifiable person. The operator must use only data that the operator is authorized to process.
5. FILE ACCESS AND TEMPORARY PROCESSING
The operator selects files through system file interfaces. The app reads those files locally and does not modify the original source file. Compressed formats may be decompressed into an app-controlled temporary location for processing. Temporary decompression files are removed after the operation where the implementation permits.
The original file and any copies held by iCloud Drive, an institutional file provider, backup service, or another selected destination remain under that provider’s controls and privacy terms.
6. NO AUTOMATIC ORTHOPRACTIS UPLOAD
The submitted build does not automatically transmit selected studies, volume data, masks, points, Hand or Muse coordinates, registration transformations, residuals, or results to Orthopractis.
Method 3 exports a request only when the user chooses to export it. Any transfer to an external segmentation service occurs outside the automatic core app workflow and is controlled by the operator. That service’s contract, security, retention, and privacy practices apply independently.
If a future Touch3D release introduces an Orthopractis server, account, analytics, crash-reporting SDK, cloud synchronization, or automatic upload, this policy and the App Store privacy answers must be updated before that release.
7. HAND, WORLD, AND OPTIONAL ACCESSORY TRACKING
The app may request:
• World Sensing to place the volume, points, and guides in immersive space;
• Hand Tracking to use the selected index fingertip for point capture or surface tracing;
• Accessory Tracking and Game Controller access to use an optional compatible Muse spatial stylus.
Tracking information is used for the active visualization and registration session. The submitted build does not automatically transmit those coordinates to Orthopractis.
8. USER-INITIATED EXPORTS AND EXTERNAL DESTINATIONS
Information leaves the app only when the operator deliberately selects an external action, such as:
• exporting a SAM request;
• saving or sharing a report, manifest, image, model, or other prepared file;
• opening a Files destination or another file provider;
• opening the support, privacy, or terms website;
• opening an email composer;
• independently sending material to a segmentation, research, institutional, cloud, or communication service.
The selected destination processes the transferred material under its own terms. The operator must review the content and destination before sharing. Do not send identifiable patient information or clinical images through ordinary support email.
9. CONSENT ON EVERY APP-PROCESS LAUNCH
The app presents a consent, privacy, safety, and terms acknowledgement after each new application-process launch. Acceptance applies only to the current running process and is not stored as permanent consent.
This in-app acknowledgement does not replace patient consent, a lawful basis for health-information processing, institutional approval, research approval, confidentiality duties, or any authorization required by the operator’s profession or jurisdiction.
10. RETENTION AND DELETION
The submitted build is designed primarily around the active local session. Closing the active study, resetting registration, or terminating the app clears in-memory session information according to operating-system behavior. Temporary processing files are removed by the app where the implementation provides that cleanup.
User-created exports remain in the destination selected by the user until deleted there. Source files remain with the original Files provider. Deleting Touch3D Scan removes its app container subject to Apple platform, backup, device-management, and file-provider behavior.
Support correspondence and website records are separate from the app workflow and may be retained only as long as reasonably necessary for support, security, legal, accounting, or regulatory purposes.
11. SECURITY AND OPERATOR RESPONSIBILITIES
Touch3D Scan relies on the Apple platform sandbox and system file interfaces. No technical measure can remove all risk.
The operator and responsible organization must:
• control access to Apple Vision Pro and linked storage;
• use only authorized and appropriately de-identified data;
• comply with patient-consent, confidentiality, institutional, research, records, security, and retention requirements;
• validate any external service and transfer method;
• prevent unauthorized screen viewing or recording;
• inspect every export before sharing;
• repeat registration after relevant movement or tracking interruption.
12. CHILDREN
The app is not directed to children as a consumer service. It is intended for adults and supervised professional, engineering, or research use. A subject’s age does not itself authorize processing. The operator must have the appropriate authority and safeguards for every subject and dataset.
13. INTERNATIONAL, PROFESSIONAL, AND REGULATED USE
Privacy, health-data, medical-device, professional-practice, research, and records requirements differ by country and intended use. The operator and deploying organization are responsible for determining whether the app may be used in their context.
The presence of a disclaimer does not by itself determine regulatory status. Orthopractis must assess the submitted configuration and intended use for every territory in which it is distributed.
14. WEBSITE AND SUPPORT COMMUNICATIONS
When a person visits the Orthopractis website or contacts support, the website host, cookie tools, email provider, security services, and other business providers may process ordinary web or correspondence information such as IP address, browser/device information, cookie choices, name, email address, message content, and support details.
Website and support practices are separate from the local core app workflow. The website cookie notice and consent tool must accurately describe those practices.
15. DATA SUBJECT REQUESTS AND WITHDRAWAL
Questions, privacy requests, or deletion requests concerning information held by Orthopractis through support or website communications may be sent to:
Do not include identifiable patient information or clinical images in ordinary email. Where identity verification is required, Orthopractis may request sufficient information to verify the request without collecting unnecessary clinical information.
Consent for an independently selected external service must be withdrawn through that service or the responsible organization.
16. CHANGES
This policy may be updated when the app, website, external services, law, or platform requirements change. The effective date must be revised when the published policy changes materially.
17. CONTACT
ORTHOPRACTIS.COM SINGLE MEMBER P.C.
Email: info@orthopractis.com
Support page: https://www.orthopractis.com/touchseect
DYNAMIC HIP PRIVACY POLICY
PUBLIC EDUCATIONAL RELEASE 1.1 BUILD 17
Effective date: 28 July 2026
1. SCOPE
This section applies to Dynamic Hip for iOS/iPadOS and DynamicHipVision for visionOS, published by Orthopractis.
2. NO ACCOUNT OR ORGANIZATION MEMBERSHIP
The public app has no account creation, login, invitation, organization whitelist, managed-device requirement, or private backend.
3. INFORMATION PROCESSED LOCALLY
When the user chooses to use the app, it may process:
- an image explicitly selected from Photos or Files, or captured through a supported camera workflow;
- non-identifying reference-series inputs such as reference years/months, selected reference series, reference height, and reference weight;
- calibration-marker diameter;
- 19 landmark coordinates, placement history, selector position, pan, and zoom;
- calculated geometry, mathematical model indices, graphs, warnings, and manual scenario values;
- 3D visibility and presentation preferences;
- user-prepared text, CSV, or annotated-image exports.
Do not enter names, dates of birth, medical-record numbers, contact details, or other identifiers. Prefer de-identified educational images.
4. IMAGE HANDLING
The image importer creates an orientation-normalized working bitmap for display and landmark annotation. The original source file is not modified. The working bitmap is not intended to preserve embedded source metadata.
5. ACTIVE-SESSION RECOVERY
To reduce loss of unfinished work, the app stores the normalized working image and workspace settings in its local Application Support container. Loading a new image replaces the active session. Remove Image deletes the active local recovery session.
6. NO AUTOMATIC UPLOAD OR TRACKING
The current public app does not include developer-operated analytics, advertising, behavioural tracking, cloud synchronization, or automatic image/result upload to Orthopractis.
7. USER-INITIATED SHARING
When a user opens a website, email composer, Files destination, Photos destination, or system share sheet, the selected external service processes the transferred item under its own privacy terms. Review every export before sharing. Do not send identifiable medical images or personal health information through ordinary support email.
8. APPLE SERVICES
Photos, camera, Files, system sharing, App Store purchase processing, crash diagnostics selected in device settings, and operating-system services are controlled by Apple and the user's settings. Consult Apple's privacy information for those services.
9. SECURITY
The app relies on the device sandbox and platform security. Users remain responsible for device access controls, backups, institutional policy, lawful authority to process images, and secure export destinations.
10. CHILDREN
The public app is intended for adults and supervised education. It is not designed to collect personal information from children. Do not use a child's identifiable image or information without appropriate authority and safeguards.
11. DATA DELETION
Use Remove Image to delete the active app-local working session. Deleting the app removes its app container from the device, subject to operating-system backup behavior. Copies previously exported are controlled by the user and the selected destination.
12. CHANGES
This policy may be updated when functionality, law, or platform requirements change. The effective date will be revised.
13. CONTACT
Website: https://www.orthopractis.com
Support: https://www.orthopractis.com/dynamichip
Email: info@orthopractis.com
CobbAngleApp Privacy Policy
Effective date: 24 July 2026Website: https://www.orthopractis.comCobb Angle support: https://www.orthopractis.com/cobb-anglePrivacy Policy page: https://www.orthopractis.com/privacySupport email: info@orthopractis.com
1. Scope
This Privacy Policy explains how CobbAngleApp handles information when an operator uses the app to load an image, place Cobb measurement points, calculate an angle, recover unfinished work, or create an export. It also explains what happens when the operator opens an external Orthopractis website, support page, email composer, Photos destination, Files destination, or system share destination.
2. Information processed by the app
Depending on operator choices, CobbAngleApp may process:
an image selected from Photos or Files, or captured with Camera;
a source description such as a file name or “Photos selection”;
the selected Standard or Extended S1/CSVL method;
registered point coordinates, point order, selector position, zoom, pan, lock state, and panel settings;
the calculated Cobb angle and displayed reference geometry;
an annotated image, text report, or CSV point table created at the operator's request;
technical app-local recovery information needed to restore unfinished work.
The app does not require the operator to create an Orthopractis account.
3. On-device image preparation
The app creates a new orientation-normalized working bitmap and may reduce its pixel dimensions to keep point placement, pan, zoom, recovery, and export responsive. The current source limits the longest working-image dimension to 6144 pixels. The app does not modify the source image or source file and does not intentionally copy embedded source metadata into the new working bitmap.
4. Local active-session recovery
To reduce loss of unfinished work when the app is suspended, closed, or terminated, the app stores the current normalized working image and related measurement state in the app's local Application Support container. This state may include method, point coordinates, placement history, selector state, zoom, pan, lock state, visibility settings, and guidance position.
Loading another image replaces the active recovery image. Choosing Remove Image deletes the app-local active recovery folder. Deleting the app or its local data also removes app-local recovery data, subject to operating-system and device-management behavior. The app marks the recovery folder as excluded from backup where the operating system supports that setting.
5. Consent at launch
The app requests an authorization, privacy, and professional-responsibility acknowledgement after every fresh application launch. Acceptance applies only to the current running app session and is not saved as permanent consent. A recovered measurement is not shown until the launch form is accepted again.
The in-app acknowledgement does not replace patient consent, a lawful basis for health-information processing, institutional approval, confidentiality duties, or any authorization required by the operator's role or jurisdiction.
6. No automatic developer upload, advertising, or behavioral tracking
The described app source does not include an app-side workflow that automatically uploads clinical images, points, or measurements to an Orthopractis server. It does not include in-app advertising, behavioral-tracking code, or developer-operated analytics. Its privacy manifest declares tracking as false and contains no collected-data entries for app transmission.
7. Operator-controlled destinations
Information leaves the app only when the operator chooses a system or external destination, for example:
saving an annotated image to Photos;
sharing an annotated image, report, or CSV through the system share interface;
saving a prepared file to Files or another selected provider;
opening the Orthopractis website, support page, Privacy Policy, or Terms of Use;
opening an email composer.
Those destinations and services process information under their own terms and privacy practices. The operator must inspect the content and selected destination before completing an export or message.
8. Clinical images and confidentiality
Use only images and information that the operator is authorized to process. Prefer de-identified material where possible. Protect the device and app access. Follow applicable confidentiality, retention, access-control, consent, security, and institutional requirements. Do not send identifiable clinical images through ordinary support email.
9. Data retention and deletion
The app keeps only one active local recovery session. It remains until it is replaced by another image, removed with Remove Image, removed with app-local data, or removed when the app is deleted, subject to operating-system behavior. Operator-created exports remain in the destination chosen by the operator until deleted there under that destination's controls.
10. Security
The app uses the operating system's app container and system-controlled Photos, Files, Camera, and sharing interfaces. No storage method is guaranteed to eliminate all risk. Operators remain responsible for device security, access control, de-identification, export review, approved transfer methods, and compliance with organizational policy.
11. Children and patients
CobbAngleApp is a professional measurement aid and is not directed to children as a consumer service. A patient's age does not by itself authorize processing. The operator must have an appropriate professional, institutional, and legal basis for every image and related item processed.
12. International and regulated use
Health, privacy, medical-device, professional-practice, records, research, and data-protection requirements differ by jurisdiction and intended use. The operator and deploying organization are responsible for determining whether and how the app may be used in their context.
13. Changes
Orthopractis may update this public Privacy Policy. The effective date should be changed when the published policy changes materially. In-app summary text may be updated with app releases and does not replace the authoritative policy published at https://www.orthopractis.com/privacy.
14. Contact
Questions about CobbAngleApp privacy may be sent to info@orthopractis.com. Do not include identifiable patient information or clinical images in ordinary support email.
DYNAMIC GONIOMETER AR PRIVACY POLICY
Effective date and last updated: 24 July 2026
1. WHO WE ARE
Dynamic Goniometer AR (the “App”) is published by ORTHOPRACTIS.COM SINGLE MEMBER P.C. (“Orthopractis”, “we”, “us” or “our”).
Website: https://www.orthopractis.com
Support: https://www.orthopractis.com/dynamic-goniometer-app
Privacy contact: info@orthopractis.com
This policy explains how information is handled when you use the Android or iOS version of the App, contact us for support, or visit the related Orthopractis web pages. It should be read together with the Terms of Use.
2. PURPOSE AND INTENDED USERS
The App is an augmented-reality measurement-support tool intended primarily for qualified healthcare, rehabilitation and related professionals. It recognises three supplied printed image markers, displays a live 3D model and calculates joint angle, complementary angle, minimum, maximum and range of motion. The App does not diagnose, prescribe treatment or replace clinical examination, professional judgment or applicable medical-device procedures.
3. INFORMATION PROCESSED BY THE APP
3.1 Camera and sensor information
The App requires camera access and uses device motion/tracking information to recognise the three printed markers and render the AR measurement. Camera frames, marker poses and calculated measurements are processed for the live session. Orthopractis does not operate an app server that receives the live camera view, marker positions or calculated measurements.
3.2 Saved screenshots and exported markers
SAVE creates an image of the visible App screen, which may include the camera view, a person, the AR model and measurement results. EXPORT writes the three printable marker images. These actions occur only when the user requests them and save files to the device media library. Orthopractis does not automatically receive those files. The user controls later access, deletion, backup and sharing through the device, operating system and any separately chosen cloud or messaging services.
3.3 No account, advertising or Orthopractis app analytics
The App does not require an Orthopractis account and does not include advertising, an Orthopractis analytics service, social features or a user-content upload function. It does not request contacts, microphone, location, calendar, call-log, SMS or financial permissions.
4. GOOGLE PLAY SERVICES FOR AR (ARCORE)
The Android App runs on Google Play Services for AR (ARCore), which is provided by Google and governed by the Google Privacy Policy. ARCore automatically collects certain required data, including Google account identifiers when a user is signed in or device/install identifiers otherwise, performance and diagnostic information, and information about ARCore API usage and app activity. Google states that it uses this information for analytics, service operation, diagnosis and improvement and encrypts ARCore-collected data in transit on supported devices. Google controls this collection and its retention under Google’s policies.
The current App does not enable ARCore Cloud Anchors or the Geospatial API and does not request location permission. Google’s practices and the ARCore service may change; consult Google’s current privacy materials at https://developers.google.com/ar/develop/play-safety-label and https://policies.google.com/privacy.
5. HEALTH-RELATED AND PATIENT INFORMATION
Angle measurements or screenshots associated with an identifiable person can be personal data and may be health-related or otherwise sensitive. The App does not transmit that content to Orthopractis, but the professional or organization using the App is responsible for determining its own legal role and obligations, obtaining the patient’s or subject’s valid authorization, limiting collection to what is necessary, securing the device and files, applying retention rules and preventing unauthorized disclosure.
Do not place patient names, record numbers or other identifiers in the camera view unless necessary and lawfully authorized. Prefer non-identifying capture. Do not send patient information to Orthopractis support unless specifically requested through a secure agreed channel and legally permitted.
6. SUPPORT COMMUNICATIONS AND WEBSITE DATA
When you contact us, we process the information you choose to provide, such as name, email address, device/app details, diagnostic descriptions and correspondence, to answer the request, maintain security, establish or defend legal claims and improve support. Please remove patient or other sensitive information from support messages and screenshots.
Our website may process ordinary web data such as IP address, browser/device information, cookie choices, page interactions and form submissions through our website host and service providers. Website cookie and tracking practices should be described in the website’s cookie notice and consent tool. Those website practices are separate from the core App measurement workflow.
7. PURPOSES AND LEGAL BASES
Depending on the context and applicable law, we process information to:
• provide support and respond to requests;
• operate, secure and improve the App and website;
• comply with legal and regulatory duties;
• protect users, Orthopractis and others; and
• establish, exercise or defend legal claims.
For persons in the EEA/UK, the applicable legal bases may include performance of a contract or steps requested before a contract, legitimate interests in support/security/product improvement, compliance with legal obligations and consent where consent is required. Google independently determines the legal bases for data it processes through ARCore.
8. DISCLOSURE AND SERVICE PROVIDERS
Orthopractis may disclose support or website information to service providers that host the website, provide email/communications, security, professional advice or other necessary business services, subject to appropriate obligations. We may also disclose information when required by law, to protect rights or safety, in connection with a corporate transaction, or with your direction.
Orthopractis does not sell the App’s camera view, measurements or saved screenshots and does not receive them automatically. Google processes ARCore telemetry as described above and under Google’s own policies. Device manufacturers, operating-system providers, app stores, backup providers and services chosen by the user may separately process information under their own terms.
9. RETENTION AND DELETION
The live AR session data and calculated values are not stored by Orthopractis. Saved images and exported markers remain on the device or in services chosen by the user until the user or responsible organization deletes them. Support correspondence is retained only as long as reasonably necessary for the request, security, legal, accounting or regulatory purposes. Website records are retained according to the applicable website/cookie notices and provider settings. Google determines retention for ARCore-collected data.
Because the App has no Orthopractis user account, there is no in-app account-deletion function. Delete local images through the device gallery/file manager. Contact info@orthopractis.com to request action regarding support or website information held by Orthopractis, subject to legal exceptions and identity verification.
10. SECURITY
We use reasonable organizational and technical measures appropriate to the information we control. No system is completely secure. Users and professional organizations must secure devices, screen locks, backups and exported files; restrict access; keep Android/iOS, Google Play Services for AR and the App updated; and use approved organizational storage/sharing procedures.
11. INTERNATIONAL TRANSFERS
Orthopractis, Google and website/service providers may process information in countries other than the user’s country. Where required, appropriate transfer mechanisms and safeguards should be used. Google’s international-transfer practices are explained in Google’s privacy materials.
12. YOUR RIGHTS
Depending on applicable law, you may have rights to access, correct, erase, restrict or object to processing, receive portable data, withdraw consent and complain to a supervisory authority. These rights are not absolute. Contact info@orthopractis.com for information controlled by Orthopractis. Requests concerning ARCore/Google data should be directed to Google using Google’s privacy controls and contact channels.
13. CHILDREN
The App is intended for adult professionals and is not directed to children. A child may be the subject of a professionally authorized measurement only when the responsible professional and parent/guardian have all permissions required by law and the organization’s procedures. Children should not independently use the App or submit information to Orthopractis.
14. CHANGES
We may update this policy to reflect product, legal or service changes. We will publish the revised text and update the date. Material changes may also be presented in the App. Because the App presents a consent notice on each fresh launch, users can review the current linked documents before continuing.
HIP BIOMECHANICS PRIVACY POLICY
Effective date: 19 July 2026
Last updated: 19 July 2026
App version covered: Hip Biomechanics 8.0, Build 1
1. INTRODUCTION
ORTHOPRACTIS.COM SINGLE MEMBER P.C. ("Orthopractis", "we", "us" or "our") respects privacy and is committed to explaining clearly how Hip Biomechanics handles information.
This Privacy Policy applies to the Hip Biomechanics application for iPhone, iPad and Apple Vision Pro, the Hip Biomechanics support page, the related pages at orthopractis.com, and support communications concerning the app.
Terms of Use: https://www.orthopractis.com/terms-of-use
3. INTENDED USERS AND PURPOSE
Hip Biomechanics is intended for appropriately qualified adult healthcare professionals, authorized clinical-team members, supervised trainees, educators and researchers. It is not directed to children as app users and is not intended for unsupervised patient self-diagnosis, emergency decisions, autonomous diagnosis, primary image interpretation or sole-reliance treatment decisions.
The app supports operator-directed placement of anatomical landmarks on a calibrated frontal pelvic radiograph and calculates geometric and biomechanical model outputs, including contact-surface, load and pressure-related values, graphs, overlays, reports and exports.
A radiograph processed by an authorized professional may relate to an adult or a child. The professional or institution using the app remains responsible for the lawful authority, confidentiality safeguards and clinical governance applicable to that image and data subject.
4. INFORMATION PROCESSED BY THE APP
Depending on the operator's choices, the app may process the following information locally on the device:
• A radiographic image selected from Photos or Files, or captured with the device camera where available.
• The source filename or source description. A filename can itself contain identifying information and should therefore be reviewed before use or export.
• Age in years and months.
• The selected female or male reference category used by the original calculation method.
• Height, weight and calibration-marker dimension.
• The coordinates of the 19 operator-selected anatomical and calibration points.
• Selector position, point-placement history, image zoom and pan, image lock state and relevant interface settings.
• Calculated geometry, contact surface, load and pressure model outputs, reference comparisons, graphs and statistics.
• Reports, tables and annotated images generated for user-controlled export.
The app does not ask for a patient name, account login or Orthopractis user profile. Nevertheless, an imported image or filename may contain identifying or health-related information, so it must be handled as confidential whenever it can be linked to a person.
5. LOCAL IMAGE PROCESSING
The current release is designed to process the selected image and measurement session locally on the Apple device.
The image loader creates an orientation-normalized working bitmap and limits the longest working dimension to support responsive pan, zoom and point placement. The original source image or file is not modified. Embedded source metadata is not intentionally copied into the normalized working bitmap, but visible information burned into the image pixels remains visible and may still identify a person.
6. ACTIVE-SESSION RECOVERY
To reduce accidental loss when the app is suspended, closed or terminated, the app automatically stores the active working session in its private Application Support area. The recovery session can include:
• The normalized working image.
• The image source description.
• Age, reference sex, height, weight and calibration values.
• Registered point coordinates and point-placement history.
• Selector, zoom, pan, image-lock and relevant interface settings.
• The date and time of the most recent save.
The app relies on the Apple platform's app sandbox, device passcode and operating-system data protection. The app does not provide a separate Orthopractis cloud vault or server-side backup for the measurement session.
Loading a different image replaces the active recovery session. Using the in-app Remove image control deletes the app-local recovery session. Deleting the app or its local data also removes app-local recovery data, subject to operating-system, device-management and backup behavior. The recovery folder is marked as excluded from device backup where the operating system supports that setting.
7. CONSENT AT EVERY FRESH APP LAUNCH
The app presents an authorization, privacy and professional-responsibility consent form after every fresh app launch. Acceptance applies only to the current running app session and is not stored as a permanent preference.
A brief background and foreground transition during the same running session does not interrupt an active measurement. After the app process is terminated and launched again, the consent form is required before the workspace and any locally recovered measurement can be accessed.
This in-app acknowledgement does not replace patient consent, professional confidentiality duties, institutional approval, a data-processing agreement, or another legal basis required for processing health information.
8. DEVICE PERMISSIONS
The app may request access only when the user chooses a related function:
• Photos access, to select an image for local measurement.
• Files access, through the system file picker, to open a user-selected image.
• Camera access on supported devices, to capture an image selected by the operator.
• System sharing, to export a report, table or annotated image to a destination chosen by the operator.
Permission decisions are controlled through Apple system settings. Denying a permission may disable the related import or export route without affecting unrelated functions.
9. INFORMATION NOT AUTOMATICALLY SENT TO ORTHOPRACTIS
The current release is designed so that normal measurement use:
• Does not require an Orthopractis account or login.
• Does not contain advertising.
• Does not use measurement data for cross-app or cross-site behavioural tracking.
• Does not include a developer-operated analytics endpoint for clinical images or measurement sessions.
• Does not automatically upload imported images, point coordinates, subject values, calculations, reports or active recovery sessions to Orthopractis servers.
• Does not automatically send identifiable patient information to Orthopractis.
These statements describe the current app release and must be reviewed again if networking, accounts, analytics, crash-reporting SDKs, cloud synchronization, remote processing or other third-party components are added.
10. EXPORTS AND THIRD-PARTY DESTINATIONS
Exports occur only when the operator requests them. The app can prepare a text report, data table or annotated image and hand it to the Apple system sharing interface or another destination selected by the operator.
A selected destination may include Files, iCloud Drive, AirDrop, email, messaging, cloud storage, a managed institutional application, printing or another installed service. Once data is sent to a selected destination, that provider and the operator's organization control the resulting copy under their own terms, privacy practices, security configuration and retention rules.
Review every export before sharing. Remove or avoid identifiers that are not necessary. Do not send identifiable clinical images or protected health information through ordinary support email.
11. SUPPORT COMMUNICATIONS
When a person contacts Orthopractis, we may receive information voluntarily provided in the message, such as:
• Name and email address.
• Organization or professional role.
• Device model, operating-system version and app version.
• A description of the problem or request.
• Screenshots, reports, logs or other attachments voluntarily supplied.
Do not include identifiable patient images, names, dates of birth, medical-record numbers or other confidential clinical information in ordinary support communications. If sensitive information is sent without being requested, we may restrict access, ask for a safer communication route, or delete the material when it is no longer needed, subject to legal obligations.
We use support information to respond to requests, troubleshoot defects, improve documentation and product quality, protect security, prevent abuse, establish or defend legal claims and meet legal obligations.
12. WEBSITE, WIX AND COOKIES
The Orthopractis website is created or hosted using Wix services. When a visitor uses the website, Wix and enabled site services may process technical information such as IP address, browser and device information, security events, cookie identifiers, page requests, language, approximate location derived from IP, consent choices and interaction data.
The exact data and cookies depend on the Wix applications, forms, analytics tools, social-media features, fonts, video players, maps, marketing integrations and other components enabled on the published site.
Essential cookies may be used for security, fraud prevention, network management, session operation, consent preferences and core website functionality. Where applicable law requires consent, non-essential analytics, personalization or marketing cookies should not be placed until the visitor has made the required choice through the Wix cookie banner or another valid consent mechanism.
Website visitors should use the site's Cookie Settings control, where available, to review or change non-essential cookie choices.
13. APPLE AND APP STORE DATA
Apple may process App Store purchase, download, device, diagnostics, crash, performance and usage information under Apple's own terms, privacy settings and policies. Orthopractis may receive information or aggregated reports made available by Apple through App Store Connect or related developer services.
Apple's processing is separate from the local clinical-image and measurement workflow described in this Policy. Users control available diagnostic-sharing settings through their Apple device and account settings.
14. LEGAL BASES FOR INFORMATION RECEIVED BY ORTHOPRACTIS
Where the GDPR, UK GDPR or similar law applies, Orthopractis may process website and support information on one or more of the following bases, depending on the context:
• Performance of a contract or steps requested before entering a contract, such as providing app support.
• Legitimate interests in operating the website, responding to users, improving documentation, maintaining security, preventing abuse and protecting legal rights, where those interests are not overridden by the individual's rights.
• Compliance with legal obligations.
• Consent, where consent is required, including for certain non-essential cookies or optional communications.
• Establishment, exercise or defence of legal claims where applicable.
The healthcare professional, clinic, hospital, university, research body or other organization that chooses to process a patient's radiograph and related values ordinarily determines the purpose and means of that clinical processing. That user or organization is responsible for identifying the applicable legal basis under Article 6 GDPR and, where health data are involved, an applicable Article 9 condition or other lawful authorization.
The launch acknowledgement in the app is a user-facing confirmation. It is not a substitute for the legal basis required by the user's institution or applicable law.
15. CONTROLLER AND PROCESSOR ROLES
For an image and measurement session that remain exclusively on the user's device and are never transmitted to Orthopractis, Orthopractis does not receive that clinical content.
The user and the user's organization remain responsible for the local clinical processing, including authority to access the image, patient information, device management, retention, deletion, confidentiality and any required notices or consent.
If a user voluntarily sends information to Orthopractis for support, Orthopractis acts as controller for the copy it receives for the support and related purposes described in this Policy. A separate written arrangement may be required before any planned processing of confidential clinical information on behalf of an institution.
16. SHARING AND SERVICE PROVIDERS
Orthopractis does not sell app measurement sessions or patient images.
We may disclose website or support information only as reasonably necessary to:
• Website, hosting, email, security, communications and technical service providers, including Wix, under applicable contractual and legal safeguards.
• Apple and other platforms when the user chooses their services or when platform operation requires it.
• Professional advisers such as lawyers, accountants, auditors or insurers.
• Public authorities, courts or regulators when disclosure is required by law or necessary to protect rights, safety or security.
• A lawful successor in a merger, reorganization, financing, asset transfer or similar transaction, subject to appropriate protection and notice where required.
Each third party processes information under its own legal duties and applicable agreements. The website configuration and this Policy must be updated if new providers or data flows are introduced.
17. INTERNATIONAL DATA TRANSFERS
Wix, Apple, email providers and other service providers may process website or support information in countries outside the visitor's country or the European Economic Area.
Where required, transfers should rely on an adequacy decision, standard contractual clauses, the EU-US Data Privacy Framework where applicable, or another lawful transfer mechanism, together with supplementary safeguards where necessary.
18. RETENTION
App-local measurement data remains on the user's device until it is replaced, removed through the app, removed by deleting app data, or otherwise deleted through operating-system or device-management controls.
Orthopractis retains website and support information only for as long as reasonably necessary for the purpose for which it was received, including responding to the request, maintaining security records, preventing abuse, satisfying accounting or legal obligations, and establishing or defending legal claims. Retention may therefore vary according to the nature of the communication and any applicable legal hold. Information that is no longer needed should be deleted or anonymized in accordance with operational procedures.
Wix and other providers apply their own retention periods to data they control or process under their terms and configuration.
19. SECURITY
We use reasonable technical and organizational measures appropriate to the nature of the information and service. The app uses Apple platform sandboxing and local device protections. The website and email depend in part on Wix, Apple, the user's organization and other service providers.
No device, email, website, network, storage system or transfer method is completely secure. Users must protect device passcodes, Apple accounts, managed-device credentials, file-provider accounts and exported files. Clinical users should use institutionally approved devices, storage and communication channels.
20. PRIVACY RIGHTS
Depending on the applicable law and circumstances, an individual may have rights to:
• Obtain information about processing.
• Request access to personal information held by Orthopractis.
• Request correction of inaccurate information.
• Request deletion in appropriate circumstances.
• Request restriction of processing.
• Object to processing based on legitimate interests.
• Receive portable information where the right applies.
• Withdraw consent for future processing where processing relies on consent.
• Lodge a complaint with a competent supervisory authority.
These rights apply to personal information held by Orthopractis. Orthopractis cannot provide a server copy of a radiograph or session that remained only on the user's device and was never received by us.
To exercise a right concerning website or support information, email info@orthopractis.com with the subject "Hip Biomechanics Privacy Request" and describe the request. We may need to verify identity, authority and the information concerned before responding.
Individuals in Greece may also contact the Hellenic Data Protection Authority at https://www.dpa.gr/. Individuals elsewhere may contact the supervisory authority for their place of residence, work or the alleged infringement.
21. DELETING LOCAL APP DATA
To delete the active app-local recovery session, use Remove image inside Hip Biomechanics. This removes the active normalized working image and session record from the app's recovery area.
Delete exported reports, tables or annotated images separately from every destination to which they were saved or shared. Deleting the app generally removes its app-local data, subject to operating-system backups, managed-device policies and third-party file locations.
22. CHILDREN
The app is not directed to children as users and does not provide a child account or social feature. Only qualified or appropriately supervised adults should operate the app.
An authorized professional may process a pediatric radiograph where clinically, educationally or scientifically appropriate. The professional and institution remain responsible for lawful authority, special protections for minors, confidentiality, data minimization and any required parental or guardian information or consent.
23. AUTOMATED DECISION-MAKING
The app performs deterministic mathematical calculations from operator-entered values and operator-selected anatomical points. It does not make an autonomous decision that produces legal effects or similarly significant effects for a person.
Load, pressure, reference comparisons and overlays are model outputs for professional review. They do not independently diagnose a condition, prescribe treatment, determine eligibility, or replace a qualified professional's decision.
24. THIRD-PARTY LINKS
The app and website may link to Apple, Wix, email, social-media, research or other third-party services. This Policy does not control those services. Review the privacy information of a third party before sending information to it.
25. CHANGES TO THIS POLICY
We may update this Policy to reflect app functionality, website configuration, legal requirements, security practices, support processes or business changes. The current version will be posted at https://www.orthopractis.com/privacy with a revised effective or last-updated date.
Because Hip Biomechanics requires consent at every fresh launch, revised in-app summaries or Terms can be presented again before access to the workspace.
PRIVACY POLICY FOR SIMPLE DICOM VIEWER
Effective date: 14 July 2026
Last updated: 14 July 2026
1. INTRODUCTION
ORTHOPRACTIS.COM SINGLE MEMBER P.C. (“Orthopractis,” “we,” “us,” or “our”) respects privacy and is committed to explaining how Simple DICOM Viewer handles information. This Privacy Policy applies to the Simple DICOM Viewer application, its support page, and related support communications.
2. CONTACT DETAILS
Controller/publisher: ORTHOPRACTIS.COM SINGLE MEMBER P.C.
Website: https://www.orthopractis.com
Product support: https://www.orthopractis.com/DicoViewer
Email: info@orthopractis.com
3. SCOPE
This policy covers the iPadOS and visionOS release of Simple DICOM Viewer. It does not automatically govern third-party websites, file-storage providers, hospital systems, DICOM archives, or other services used before or after data is opened in the app.
4. APP PURPOSE
The app allows users to select compatible DICOM files and visualize image series as three-dimensional volumes. It includes presets, window and level, opacity, transfer functions, clipping, cropping, and immersive presentation.
5. INFORMATION PROCESSED BY THE APP
The app may process information contained in files selected by the user, including pixel data and DICOM metadata. DICOM metadata can contain names, identifiers, dates, institution names, accession numbers, study descriptions, device information, and health-related information.
6. LOCAL FILE PROCESSING
In the current release, selected DICOM studies are intended to be processed locally on the user’s device whenever possible. The app does not automatically upload selected DICOM studies to Orthopractis servers.
7. INFORMATION WE COLLECT
Subject to confirmation of the final binary, the current release:
• Does not require an Orthopractis account.
• Does not include advertising.
• Does not use data for cross-app tracking.
• Does not intentionally collect selected DICOM studies on Orthopractis servers.
• Does not intentionally collect patient identifiers from selected files.
8. SYSTEM AND APP STORE DATA
Apple may process purchase, download, diagnostics, crash, performance, device, and App Store information under Apple’s own terms and privacy policies. Orthopractis may receive aggregated or Apple-provided reports through App Store Connect. Such reports are controlled by Apple’s settings and services.
9. SUPPORT COMMUNICATIONS
When you contact support, we may receive your email address, name, message, device and OS details, app version, screenshots, diagnostic information, and any other information you voluntarily provide. Do not send identifiable patient images or protected health information through ordinary email.
10. PURPOSES OF SUPPORT PROCESSING
We use support information to respond to requests, troubleshoot technical issues, improve documentation, investigate defects, protect security, and meet legal obligations.
11. LEGAL BASES — EEA/UK
Depending on the context, processing may rely on performance of a contract, legitimate interests in providing and improving support, compliance with legal obligations, protection of legal claims, or consent where required. Health data and other special-category data should not be sent to us without an appropriate lawful basis and agreed secure process.
12. DATA SHARING
We do not sell personal information. We may disclose support information to service providers that host our website or email, professional advisers, authorities when legally required, or a successor in a lawful corporate transaction. Service providers should be limited to the information necessary for their role.
13. WIX WEBSITE
Our website is hosted or built using Wix services. Wix may process technical, cookie, security, hosting, and usage information according to the site configuration and Wix’s policies. The exact cookie banner and disclosures must match the Wix apps, analytics, forms, fonts, embedded media, and integrations enabled on the published site.
14. COOKIES
The website may use essential cookies required for security, session management, language, consent preferences, forms, and site operation. Optional analytics or marketing cookies should not be enabled until the required consent mechanism is configured for applicable visitors.
15. INTERNATIONAL TRANSFERS
Website, email, and service providers may process data outside the visitor’s country. Where required, appropriate safeguards should be used, such as adequacy decisions, standard contractual clauses, or another lawful transfer mechanism.
16. RETENTION
Selected DICOM studies remain under the user’s control in the selected file location and any app-local cache. Support correspondence is retained only as long as reasonably necessary for support, security, legal, and recordkeeping purposes. Retention periods should be reviewed against actual business systems.
17. SECURITY
We use reasonable technical and organizational measures appropriate to the service. No device, email, website, network, or storage system is completely secure. Users must protect devices, file-provider accounts, passcodes, institutional credentials, and confidential studies.
18. USER RESPONSIBILITIES
Users must ensure lawful authority to access and process DICOM data, follow institutional policies, minimize identifiable data, and avoid using ordinary support email for confidential clinical files.
19. PRIVACY RIGHTS
Depending on location, individuals may have rights to access, correct, delete, restrict, object, receive a copy of data, or complain to a supervisory authority. These rights apply to data held by Orthopractis, not necessarily to files that remain exclusively on the user’s device and are never received by us.
20. PRIVACY REQUESTS
Send requests to info@orthopractis.com with the subject “Simple DICOM Viewer Privacy Request.” We may need to verify identity and authority before acting.
21. DELETION OF LOCAL DATA
Delete source DICOM files from the original file provider or storage location. Remove app-imported content using in-app controls where available. Deleting the app may remove app-local data, subject to operating-system backups and file-provider behavior.
22. CHILDREN
The app is designed for professional, educational, research, and technical audiences and is not directed to young children. Do not allow a child to import or process confidential patient information.
23. THIRD-PARTY SOFTWARE
The app uses Apple frameworks and may contain separately licensed open-source components. Third-party components remain subject to their own licenses. If a component transmits data, this policy and App Store disclosures must be updated before release.
24. CHANGES
We may update this policy to reflect product, legal, security, or operational changes. The “Last updated” date will be revised. Material changes may be communicated in the app or website when appropriate.
25. COMPLAINTS
EEA users may complain to their competent data-protection authority. Users are encouraged to contact us first so we can attempt to resolve the concern.
26. CONTACT
ORTHOPRACTIS.COM SINGLE MEMBER P.C.
Website: https://www.orthopractis.com
Support: https://www.orthopractis.com/DicoViewer
Email: info@orthopractis.com
CENTER EDGE ANGLE FOR ios and ANDROID — PRIVACY POLICY
Effective date: 17 July 2026
Last updated: 17 July 2026
1. SCOPE AND DEVELOPER
This Privacy Policy explains how Center Edge Angle for Android handles information when the app and its related Orthopractis support pages are used. The app is provided by ORTHOPRACTIS.COM SINGLE MEMBER P.C. (“Orthopractis,” “we,” “us,” or “our”).
App name: Center Edge Angle
Android package: com.orthopractis.centeredgeangle
Website: https://www.orthopractis.com
Support page: https://www.orthopractis.com/ce-angle
Privacy page: https://www.orthopractis.com/privacy
Terms page: https://www.orthopractis.com/terms-of-use
Support email: info@orthopractis.com
2. INTENDED USERS AND PURPOSE
Center Edge Angle is intended for appropriately trained adult healthcare professionals, authorized clinical-team members, supervised trainees, educators, and researchers. It supports user-directed placement of four landmarks on a hip radiograph and local calculation and display of lateral center-edge angles, optional age-banded reference information, overlays, and annotated output.
The app is not directed to children as app users. It is not intended for unsupervised patient self-diagnosis, emergency decisions, autonomous diagnosis, autonomous treatment selection, primary image interpretation, or sole-reliance clinical decisions.
3. SUMMARY OF THE REVIEWED ANDROID BUILD
The reviewed Android 6.3 build:
• does not require an Orthopractis account or login;
• does not contain developer-added advertising, analytics, tracking, attribution, or crash-reporting SDKs;
• does not request the Android INTERNET permission;
• does not automatically upload selected images, PDF pages, camera captures, landmarks, age, measurements, results, annotations, reports, or device identifiers to Orthopractis;
• processes the active measurement session locally on the Android device; and
• saves or shares an annotated image only after the user selects the relevant action.
This policy must be updated before releasing any version that changes these practices.
4. INFORMATION PROCESSED LOCALLY ON THE DEVICE
Depending on the user's actions, the app may locally access or process:
• a hip radiograph or other image selected through Android Photos or Files;
• the first page of a user-selected PDF;
• an image produced by an external camera app after the user starts capture;
• a file display name, MIME type, URI, and image dimensions needed to open or decode the selected item;
• four landmark coordinates, selector position, zoom and pan state, and measurement method;
• optional age in years and months entered by the user;
• calculated center-edge angles, construction lines, arcs, labels, reference-category text, and results;
• interface preferences such as panel, overlay, label, guide, result, selector, size, and opacity settings; and
• an annotated PNG and text summary when the user chooses Save or Share.
Health-related images and related measurements may be personal or sensitive information. Users must obtain every required patient, parent or guardian, institutional, ethical, professional, and legal authorization and should remove unnecessary identifiers whenever possible.
5. PHOTO, FILE, PDF, AND CAMERA ACCESS
Choose from Photos uses Android's system Photo Picker where available. Browse Files / PDF uses Android's system document picker and a compatible content provider. The app receives access only to the item selected by the user and may retain scoped read access when the provider permits it. The reviewed build does not request broad photo-library, media-library, all-files, or direct camera permission.
Use Camera launches a compatible external camera application. The app provides a temporary, grant-scoped cache destination for the camera result. After the capture is decoded, or if capture is canceled, the app attempts to revoke access and delete the temporary item. Camera software, device manufacturers, and any storage service used by that software may apply their own privacy and retention practices.
6. NO AUTOMATIC ORTHOPRACTIS UPLOAD
The reviewed app does not operate an Orthopractis server connection and does not automatically transmit the active source image, landmarks, age, measurements, results, or annotated output to Orthopractis. Core calculation and annotation are performed on the device.
Android, Google Play, the device manufacturer, an external camera app, browser, email provider, cloud-storage provider, messaging app, hospital system, or other destination may process information under its own terms and privacy policy. Orthopractis does not control those independent services.
7. SAVING AND SHARING
Save creates an annotated PNG in the user's Pictures/Center Edge Angle location through Android MediaStore. The saved file remains under the user or device administrator's control until it is deleted under device, backup, storage-provider, or institutional rules.
Share creates a temporary annotated PNG and text summary and opens Android's share chooser. No destination receives the file unless the user selects that destination. The selected destination's privacy, security, access, backup, and retention practices apply. Users are responsible for selecting an authorized destination and preventing unauthorized disclosure.
8. LOCAL STORAGE, RETENTION, AND DELETION
The active decoded image and measurement session are held for app operation and are not designed as an Orthopractis patient record. Interface preferences may remain in private app storage until the user changes them, clears app data, or uninstalls the app. App-private backup is disabled in the reviewed Android manifest.
Temporary annotated files created for sharing are eligible for app cleanup. Temporary camera-cache files are normally deleted after decoding or cancellation on a best-effort basis. A file explicitly saved to Pictures/Center Edge Angle remains under the user, device administrator, backup provider, or receiving service's control until it is deleted under their rules. Copies shared to another app may remain after Center Edge Angle is closed or uninstalled.
Users can reset the active measurement, delete saved images through Android or their storage provider, clear Center Edge Angle app data in Android Settings, and uninstall the app. Clearing or uninstalling the app does not delete copies already exported to another location.
9. SUPPORT COMMUNICATIONS
The support-email action opens an external email application. When a user voluntarily contacts Orthopractis, Orthopractis may receive the sender's email address, name, message, device or app information, screenshots, files, and any other material the sender chooses to provide. Orthopractis uses that information to respond, troubleshoot, maintain reasonable support and security records, protect legal rights, and comply with applicable law.
Do not send patient-identifying, confidential, or sensitive health information to support unless it is lawful, necessary, authorized, and appropriately protected. Prefer a de-identified description of the issue.
10. ORTHOPRACTIS WEBSITE AND WIX
The Orthopractis website and Center Edge Angle support page are separate from the Android app and are hosted using Wix. When a person visits the website, Wix and any services enabled by Orthopractis may process technical information such as IP address, device and browser information, requested pages, security events, and cookie or session identifiers needed to provide, secure, and operate the site.
If the website includes contact forms, newsletter tools, analytics, embedded media, advertising pixels, chat, payment services, or other integrations, those features may process additional information described by the form, consent notice, cookie banner, or provider policy. Orthopractis must keep this section and the cookie banner aligned with the website's actual configuration.
11. COOKIES AND SIMILAR TECHNOLOGIES
Wix uses essential cookies and similar technologies for security, stability, fraud prevention, rendering, and core site operation. Additional non-essential analytics, advertising, social, or integration cookies depend on the tools enabled by the site owner. Where required by law, the website should display a cookie banner that allows visitors to make applicable choices before non-essential technologies are used.
Visitors can also manage cookies through browser settings. Blocking essential cookies may affect website operation. The Android app's local measurement workflow does not depend on website cookies.
12. DATA SHARING AND SERVICE PROVIDERS
The reviewed Android app does not automatically share the active measurement content with Orthopractis or an advertising, analytics, or tracking provider. Website hosting, email delivery, form processing, security, and other services may involve Wix or another provider acting under its own terms and applicable data-processing arrangements.
Orthopractis may disclose information actually received through support or the website when reasonably necessary to provide the requested service, protect users or rights, investigate abuse or security incidents, comply with law or a lawful request, or complete a corporate transaction subject to appropriate safeguards. Orthopractis does not sell the app's active radiograph or measurement session.
13. SECURITY AND PROFESSIONAL RESPONSIBILITY
The app uses Android's scoped file-selection, MediaStore, and grant-scoped sharing mechanisms. No mobile device, website, storage method, email service, or transmission can be guaranteed absolutely secure. Users and organizations are responsible for device encryption, access controls, screen privacy, backups, approved sharing destinations, retention, incident response, and compliance with applicable medical-confidentiality, privacy, research, employment, and institutional requirements.
14. CHILDREN AND PEDIATRIC IMAGES
The app is not directed to children as users, and Orthopractis does not knowingly collect children's information through the reviewed app. Adult authorized users may process pediatric images only when they have the required authority, lawful basis, parent or guardian authorization where applicable, professional supervision, and safeguards.
15. INTERNATIONAL AND REGULATORY USE
Users are responsible for using the app only where its distribution, intended purpose, claims, and workflow are authorized. Medical-device status, professional-use restrictions, health-data obligations, and record-retention rules can differ by jurisdiction. Any market-specific approved labeling, Instructions for Use, or regulatory disclosure for a regulated version controls in that market.
Website, email, hosting, and support providers may process information in more than one country under their own infrastructure and contractual safeguards. Users should not submit sensitive information through support unless authorized and necessary.
16. PRIVACY RIGHTS
Where applicable law grants rights concerning information actually received by Orthopractis, a person may contact info@orthopractis.com to request access, correction, deletion, restriction, objection, portability, withdrawal of consent, or another available right. Orthopractis may need to verify identity and may retain information where required or permitted by law. This section does not imply that the reviewed app automatically collects data.
EEA users may lodge a complaint with their competent data-protection authority. Contacting Orthopractis first may allow the concern to be addressed more quickly.
17. CHANGES TO THIS POLICY
Orthopractis may update this Privacy Policy to reflect changes to the app, website, law, or practices. The published page will show the effective and last-updated dates. Material app changes that affect data handling must also be reflected in the in-app disclosure, Google Play Data Safety form, Health Apps declaration, and store description before release.
18. MEDICAL AND PROFESSIONAL NOTICE
Center Edge Angle provides measurement support and reference information. It does not replace clinical judgment, radiological interpretation, professional training, institutional procedures, or consultation with qualified healthcare professionals. All source images, landmark positions, calculations, labels, and exports must be independently reviewed before they may affect care or another important decision.
FMI HIP MEASUREMENT PRIVACY POLICY
Effective date: 12 July 2026
Last updated: 12 July 2026
1. Scope and developer
This Privacy Policy explains how FMI Hip Measurement for Android handles information. The app is provided by ORTHOPRACTIS.COM SINGLE MEMBER P.C. (“Orthopractis,” “we,” “us,” or “our”).
Website: https://www.orthopractis.com
Support page: https://www.orthopractis.com/femoroacetabular-impingement-fai
2. Intended users and purpose
FMI Hip Measurement is intended for appropriately qualified adult healthcare professionals, authorized clinical-team members, trainees under supervision, educators, and researchers. It supports user-directed placement of anatomical landmarks on a hip radiograph and local calculation and display of CE angle, alpha angle, AfOR, reference-category labels, and annotated output.
The app is not directed to children as app users and is not intended for unsupervised patient self-diagnosis, emergency decisions, autonomous diagnosis, or sole-reliance clinical decisions.
3. Summary of the current Android build
The current build:
• does not require an account or login;
• does not contain advertising, analytics, tracking, or crash-reporting SDKs;
• does not request the Android Internet permission;
• does not automatically upload selected images, camera captures, landmarks, measurements, results, or device identifiers to Orthopractis;
• processes the selected image and measurement session locally on the Android device; and
• saves or shares an annotated image only after a user chooses the relevant action.
4. Information processed locally on the device
Depending on the features selected by the user, the app may locally access or process:
• a hip radiograph or other image selected through Android’s document picker;
• an image produced by an external camera app after the user starts camera capture;
• image name and dimensions needed for display/decoding;
• landmark coordinates and concentric-target position;
• CE angle, alpha angle, AfOR, reference-category labels, lines, circles, overlays, and result cards;
• user-interface settings such as selector diameter, opacity, overlays, labels, guidance visibility, and panel visibility; and
• an annotated PNG created after the user chooses Save or Share.
This local processing may involve health-related or patient-related images selected by the user. Orthopractis does not automatically receive this core content through the current app build.
5. Image selection and camera capture
Image import uses Android’s system document picker. The app receives access only to the item the user selects.
Camera capture is optional. The app invokes an installed camera application and provides a user-created MediaStore destination. The capture may remain in the device’s Pictures/FMI/Captures folder until the user deletes it. The camera application and Android operating system may have their own privacy practices and permissions.
The app does not use the camera in the background and does not request a direct camera runtime permission in this build.
6. Saving, exporting, and sharing
When the user chooses Save, the app writes an annotated PNG to Android MediaStore. When the user chooses Share, the app invokes Android’s share sheet so that the user can select a destination application or service.
The user is responsible for reviewing the file, choosing the destination, and protecting any sensitive information. Once a file is shared or saved outside the app, the destination application, cloud service, healthcare system, email provider, messaging service, or recipient may process and retain it under their own terms and privacy practices. Orthopractis does not control those destinations.
7. Data collected by Orthopractis through the app
The current app does not automatically transmit core app data to Orthopractis. Orthopractis does not automatically collect selected images, camera captures, landmark coordinates, calculated values, annotated exports, device identifiers, advertising identifiers, contacts, location, or usage analytics through this build.
If a future version adds accounts, analytics, crash reporting, advertising, cloud storage, remote support upload, subscriptions, remote AI/API processing, or another network service, this Policy and the Google Play Data safety declaration must be updated before release.
8. Support communications and website interactions
The app can ask Android to open an external email app or browser. If a user voluntarily contacts info@orthopractis.com or submits information through the website, Orthopractis may receive the sender’s email address, name, message, device/app details, screenshots, files, or other material the user chooses to provide.
Do not send patient-identifiable information, confidential clinical images, or restricted records to support unless sending is lawful, authorized, necessary, and appropriately protected. Use de-identified material wherever possible.
Support information may be used to respond, troubleshoot, maintain records, improve documentation/reliability using appropriate information, protect legal rights, prevent misuse, and comply with legal obligations. Website hosting, email providers, and other communication services may process information according to their own policies.
9. Legal basis and user responsibility for patient data
Users are responsible for obtaining every required patient, subject, parent/guardian, legally authorized representative, institutional, ethical, professional, and legal authorization before loading, capturing, saving, exporting, sharing, emailing, uploading, or storing a health-related image or app output.
Users must comply with applicable privacy/data-protection law, medical-confidentiality duties, institutional security policy, research rules, retention requirements, and professional obligations. Where possible, crop, mask, or remove names, dates of birth, record numbers, accession numbers, facility identifiers, and other identifying information.
10. Retention and deletion
Core measurement-session information remains in memory for the current app session unless the user creates an output. Interface preferences remain in local app storage until the user clears app storage or uninstalls the app.
Camera captures and annotated images remain in Android device storage or another destination selected by the user until the user deletes them using Android, the receiving application, or the relevant storage service.
Orthopractis does not have access to delete data that remains only on the user’s device or in a third-party destination selected by the user.
Support emails, website messages, attachments, and related correspondence voluntarily sent to Orthopractis may be retained as reasonably necessary to respond, maintain business/support records, comply with law, resolve disputes, preserve safety information, and protect legitimate interests. A user may request access, correction, or deletion of support material by contacting info@orthopractis.com, subject to applicable legal, regulatory, security, accounting, dispute, or backup limitations.
11. Security
The app relies on Android application sandboxing, Android’s system picker and MediaStore, local processing, and user-controlled export/share actions. Users should protect devices and exported files with appropriate device passcodes, encryption, access control, institutional safeguards, secure transfer methods, and deletion practices. No device, local storage method, email, network, or external sharing destination can be guaranteed perfectly secure.
12. Children
The app is not directed to children as app users. It is designed for appropriately qualified or supervised adults. If an authorized professional uses the app with an image relating to a minor, that professional and their organization are responsible for all required parental/guardian, legal, ethical, institutional, privacy, and security safeguards.
13. International processing
Local core processing occurs on the user’s Android device. If a user contacts Orthopractis or uses the Orthopractis website, support information may be processed in Greece and in countries where Orthopractis service providers operate, subject to applicable safeguards and law.
14. Privacy rights
Depending on location and applicable law, a person may have rights regarding personal information actually received by Orthopractis, including access, correction, deletion, restriction, portability, objection, withdrawal of consent, or complaint to a supervisory authority. Contact info@orthopractis.com. Orthopractis may need to verify identity and cannot access information that remains only on a user-controlled device or third-party destination.
15. Changes to this Privacy Policy
Orthopractis may update this Policy to reflect changes to the app, data practices, Android/Google Play requirements, support processes, or law. The current version will be posted at a stable public Orthopractis privacy-policy URL with an updated effective date. Material app changes must be reflected in the in-app disclosure and Play Console declarations before release.
16. Contact
Website: https://www.orthopractis.com
ORTHOFACECOSMETIC PRIVACY POLICY
Last Updated: July 2026
Website
https://www.orthopractis.com
Privacy Policy
https://www.orthopractis.com/privacy
Terms of Use
https://www.orthopractis.com/terms-of-use
Support
info@orthopractis.com
1. Introduction
Thank you for using OrthoFaceCosmetic.
Your privacy is important to us.
This Privacy Policy explains how OrthoFaceCosmetic collects, processes, stores, uses, shares, and protects information generated while using the application, including information generated through Apple’s TrueDepth camera, ARKit Face Tracking, Apple Vision Pro local visualization, and user-generated exports.
OrthoFaceCosmetic has been designed as a local-first educational cosmetic visualization application.
The application is not intended for:
-
facial recognition
-
identity verification
-
biometric authentication
-
advertising
-
tracking
-
profiling
-
medical diagnosis
-
medical treatment
-
surgical planning
-
employment decisions
-
insurance decisions
2. Information We Process
Depending on the features you choose to use, the application may process:
Face Mesh Information
During an active AR session the application may process:
-
ARKit face mesh geometry
-
mesh vertices
-
triangle indices
-
vertex identifiers
-
facial surface regions
-
derived landmark positions
-
derived facial regions
-
cosmetic review surfaces
-
cosmetic colour overlays
-
cosmetic patch assignments
-
cosmetic overlay opacity
-
cosmetic overlay intensity
-
user-selected cosmetic regions
-
manual vertex selections
This information exists only to provide the educational visualization inside the application.
TrueDepth Information
On supported Apple devices the application uses Apple’s TrueDepth API through ARKit Face Tracking.
The application may temporarily process:
-
facial depth information supplied through ARKit
-
AR face geometry
-
ARKit-generated face mesh
-
ARKit tracking state
-
derived facial landmarks
The application does not store raw TrueDepth camera frames by default.
The application does not store infrared images.
The application does not store depth maps.
The application does not record the TrueDepth camera stream by default.
The application processes only the information required to display the live AR visualization.
Cosmetic Guidance Information
The application may create:
-
cosmetic colour plans
-
cosmetic review surfaces
-
cosmetic product suggestions
-
colour patch assignments
-
arrows
-
blend directions
-
correction reports
These are educational visualization results generated from the live AR session.
3. How We Use TrueDepth Information
The TrueDepth API is used exclusively to provide the application’s core functionality.
Specifically, it is used to:
-
generate a live AR face mesh
-
display cosmetic colour guidance
-
display cosmetic review surfaces
-
position colour patches
-
display optional vertex identifiers
-
display arrows pointing to cosmetic regions
-
create cosmetic correction summaries
-
generate educational cosmetic reports
-
support optional Apple Vision Pro visualization
The application does not use the TrueDepth API to:
-
identify individuals
-
authenticate users
-
unlock devices
-
access Apple Face ID
-
determine personal identity
-
perform surveillance
-
create biometric profiles
-
advertise
-
track users
-
analyze behavior for marketing
-
create advertising profiles
4. Face Data
For the purposes of this Privacy Policy, “Face Data” means information generated during the active AR visualization session, including:
-
AR face mesh
-
mesh vertices
-
triangle indices
-
derived facial regions
-
cosmetic review regions
-
cosmetic overlays
-
vertex identifiers
-
derived cosmetic measurements
-
optional exported cosmetic reports
The application does not collect:
-
Apple Face ID templates
-
Secure Enclave information
-
biometric authentication data
-
Apple authentication credentials
-
passwords
-
passcodes
5. Apple Vision Pro Local Visualization
OrthoFaceCosmetic supports an optional Apple Vision Pro companion workflow.
If the user chooses to activate this feature:
the iPhone or iPad generates the live AR face mesh,
then the application may transmit a temporary local visualization packet to the user’s paired Apple Vision Pro device.
This packet may contain:
-
mesh vertices
-
triangle indices
-
cosmetic overlays
-
cosmetic colour assignments
-
cosmetic patch definitions
-
vertex identifiers
-
overlay settings
-
QR alignment transforms
-
review information
This communication is:
-
local
-
user initiated
-
temporary
-
device-to-device
-
encrypted through Apple’s local networking framework where applicable
-
intended only for the user’s paired device
The application does not upload this information to an external cloud server.
The application does not share this information with third parties.
6. Storage
By default:
All AR processing occurs locally on the user’s device.
Face mesh information is retained only while the active session is running.
When:
-
the AR session ends
-
the application closes
-
the user exits live capture
-
the user stops Apple Vision Pro streaming
the temporary face mesh information is discarded.
The application does not maintain a server-side face mesh database.
7. User Exports
The application may allow the user to create:
-
TXT reports
-
screenshots
-
cosmetic summaries
These exports are created only after the user explicitly requests them.
The application never exports information automatically.
The user chooses:
-
whether to export
-
where to save
-
whether to share
-
whom to share with
Exported files remain only in the location selected by the user.
8. Sharing
The application does not sell face data.
The application does not rent face data.
The application does not share face data with advertising companies.
The application does not share face data with analytics providers.
The application does not share face data with marketing companies.
The application does not share face data with data brokers.
The only optional transfer occurs when the user explicitly enables local Apple Vision Pro visualization.
9. Retention
Temporary AR face information exists only during the active visualization session.
User-generated exports remain only where the user saves them.
Support files voluntarily sent to Orthopractis may be retained only for the time required to provide technical support.
Users may request deletion of support material by contacting:
10. Camera Permission
Camera permission is requested only to provide:
-
live AR face mesh visualization
-
cosmetic colour guidance
-
educational cosmetic review
-
Apple Vision Pro paired visualization
The application cannot provide live AR features without camera access.
Users may revoke camera permission at any time through iOS or iPadOS Settings.
If permission is revoked, TrueDepth processing immediately stops.
11. Security
All processing is designed to occur locally.
The application minimizes retained data.
No permanent face database is maintained.
No biometric authentication information is collected.
No Face ID templates are accessed.
12. Children’s Privacy
The application is not intended to collect personal information from children.
Users should not scan another person’s face without their permission.
If the user is a minor, appropriate parental or guardian supervision is recommended.
13. Changes to this Privacy Policy
We may update this Privacy Policy to reflect:
-
application improvements
-
privacy improvements
-
Apple platform requirements
-
legal requirements
The latest version will always be published at:
https://www.orthopractis.com/privacy
14. Contact
Orthopractis
Website
Privacy Policy
https://www.orthopractis.com/privacy
Terms of Use
https://www.orthopractis.com/terms-of-use
Support
Summary
OrthoFaceCosmetic is a local-first educational cosmetic visualization application.
The application uses the TrueDepth camera only to generate a temporary AR face mesh that supports cosmetic colour guidance and educational visualization.
The application:
-
does not collect Face ID authentication information
-
does not collect Secure Enclave data
-
does not identify users
-
does not create biometric profiles
-
does not upload face mesh information to cloud servers as part of its core workflow
-
does not sell or share face data with third parties
-
retains live face mesh information only during the active AR session unless the user explicitly exports a report
OrthoFaceCosmetic Privacy Policy
TrueDepth API, Face Data, Apple Vision Pro Local Streaming, Exports, and Retention
Last updated: June 29, 2026
Website: www.orthopractis.com
Privacy Policy: www.orthopractis.com/privacy
Terms of Use: www.orthopractis.com/terms-of-use
Contact: info@orthopractis.com
1. Face Data And AR Face Geometry
OrthoFaceCosmetic uses the Apple TrueDepth camera and ARKit face-tracking features, when supported by the device, only after the user grants camera permission and starts a live AR face session. The app creates a live AR face mesh for educational cosmetic colour guidance, facial surface review, optional vertex-ID display, and optional local Apple Vision Pro viewing.
For the purposes of this Privacy Policy, face data may include AR face mesh geometry, mesh vertices, triangle indices, fixed vertex identifiers, derived facial landmark positions, derived facial surface classifications, derived symmetry values, derived cosmetic proportion references, cosmetic review-surface definitions, cosmetic colour-plan overlays, cosmetic patch vertex IDs, overlay opacity and intensity values, user-selected manual vertex selections, retain/hide cosmetic states, optional correction reports if the user exports or shares them, and optional local Apple Vision Pro stream packets if the user starts local pairing and streaming.
OrthoFaceCosmetic does not collect or access Apple Face ID authentication templates, Secure Enclave biometric data, passcode data, authentication credentials, or biometric information used to unlock the device. The app does not use face data for identity verification, biometric authentication, advertising, tracking, third-party profiling, employment decisions, insurance decisions, credit decisions, law-enforcement identification, or automated decisions about a person’s rights or eligibility.
Live camera frames are used for AR tracking and visualization. OrthoFaceCosmetic does not save raw camera video or raw face photos by default.
2. TrueDepth API Usage
OrthoFaceCosmetic uses the TrueDepth API through ARKit face tracking to generate a live AR face mesh during the active session. This information is processed to support the cosmetic-planning interface and not to identify the user.
The TrueDepth API information may be used to create the live mesh, locate repeatable surface regions, display optional white vertex identifiers, place cosmetic colour patches, show arrows pointing to review surfaces, calculate educational cosmetic review references, and create a user-controlled cosmetic correction TXT when the user exports or shares a report.
The app does not use the TrueDepth API for Face ID, login, identity matching, surveillance, advertising, tracking, or profiling.
3. How We Use Face Data
Face data is used only to provide the app’s core educational and visualization features:
creating and displaying a live AR face mesh;
mapping repeatable mesh vertex IDs to facial surfaces;
showing optional white vertex ID labels on the live AR face mesh;
computing educational cosmetic surface-review values;
generating reversible cosmetic colour-guidance overlays;
displaying transparent colour patches on selected facial review surfaces;
displaying arrows pointing to selected review surfaces;
explaining why a surface was selected;
explaining what visual effect a cosmetic colour role may create;
suggesting generic cosmetic product categories;
supporting manual vertex paint when the user enters or selects mesh vertex IDs;
letting the user retain, hide, reject, or restore cosmetic suggestions;
letting the user export or share a correction TXT or other report file if they choose;
optionally displaying the same local visualization on the user’s paired Apple Vision Pro device.
The cosmetic colour map is educational and reversible. It does not physically change the face and does not diagnose a condition. Map colours are not literal makeup colours. The app may suggest generic cosmetic product categories such as lighter concealer, soft highlighter, matte contour, blush, lip tint, setting powder, anti-shine powder, or skin tint. OrthoFaceCosmetic does not recommend cosmetic brands or companies.
4. Face Data Sharing And Apple Vision Pro Local Streaming
OrthoFaceCosmetic does not share face data with third parties as part of the core app workflow. By default, face mesh data, vertex IDs, measurements, cosmetic plans, and colour maps are processed locally on the user’s device. The app does not upload live face mesh data, vertex IDs, measurement values, cosmetic colour maps, or AR face geometry to an external server as part of the core workflow.
The app may optionally support local Apple Vision Pro pairing. This feature is user-initiated and is intended only to display the same educational visualization on the user’s paired Apple Vision Pro device.
If the user starts Apple Vision Pro streaming, the iOS or iPadOS device may send a temporary local device-to-device packet to the paired Apple Vision Pro viewer. This packet may include timestamp, mesh vertices, triangle indices, selected vertex states, selected review values, cosmetic colour-plan data, patch vertex IDs, overlay opacity, colour intensity, arrow visibility state, focused patch ID, retained patch state, hidden or rejected patch state, and QR marker coordinate-alignment information when pairing is active.
This Apple Vision Pro stream is local, user-initiated, device-to-device, intended only for the user’s paired Apple Vision Pro visualization, not a cloud upload, not advertising tracking, not third-party profiling, not biometric authentication, and not identity verification. If Apple Vision Pro pairing is not started by the user, the local Vision stream is not started. If Apple Vision Pro pairing is stopped, the local stream stops.
5. Storage, Retention, And Deletion
Live face mesh data is session-only by default. Live AR face mesh data, vertex data, measurement states, and cosmetic patch states are retained in memory only while the AR session or local stream is active and while the app needs them for live visualization.
When the AR session is stopped, the local stream is stopped, the app is closed, or the user leaves the live capture workflow, live face mesh data is discarded from the active session. OrthoFaceCosmetic does not maintain a server-side face database and does not retain face data on an external backend as part of the core workflow.
Optional user-generated files may persist only if the user intentionally saves, exports, or shares them. If the user exports or shares a file, that file remains only where the user saves or shares it. The user controls that destination and may delete the file from the device, storage location, or recipient destination they selected.
If a user contacts us for support and voluntarily sends screenshots, files, exported reports, or other materials, we use those materials only to provide support, troubleshoot issues, or respond to the user’s request. Users may request deletion of support material they voluntarily sent by contacting info@orthopractis.com.
6. User Exports And Sharing
OrthoFaceCosmetic may allow the user to export or share educational files, including correction TXT files, cosmetic colour-plan summaries, selected vertex ID lists, screenshots or images if the user chooses to create/share them, and technical support materials.
Exports are user-initiated. The app does not automatically export face data. Exported files may include derived face-related information such as review surface names, colour roles, cosmetic product categories, application instructions, blend directions, expected visual effects, what to avoid, vertex IDs, review values, opacity or intensity settings, and retained/hidden suggestion states.
Users should review exported files before sharing them and should not export or share another person’s face, face measurements, vertex IDs, screenshots, or cosmetic correction plans without that person’s informed permission.
7. Contact
For privacy questions, support requests, data questions, or deletion requests concerning support material voluntarily sent to us, contact: info@orthopractis.com.
Website: www.orthopractis.com
Privacy Policy: www.orthopractis.com/privacy
Terms of Use: www.orthopractis.com/terms-of-use
WhereMyCup Privacy Policy -
Effective date: July 7, 2026
Last updated: July 7, 2026
Developer / publisher
ORTHOPRACTIS.COM SINGLE MEMBER P.C. / Orthopractis
Website: https://www.orthopractis.com
Support page: https://www.orthopractis.com/
Privacy Policy URL: https://www.orthopractis.com/privacy
Terms of Use URL: https://www.orthopractis.com/terms-of-use
Support email: info@orthopractis.com
1. Scope
This Privacy Policy explains how WhereMyCup handles information when the iOS or iPadOS app is installed, opened, used, saved from, exported from, or supported. It also explains how the Orthopractis website pages used for app support, privacy, terms, and contact may handle information when hosted on Wix or another website provider.
In this Policy, "WhereMyCup," "the app," "we," "us," and "our" refer to the app and to Orthopractis where Orthopractis receives information. "You" means the app user, website visitor, healthcare professional, researcher, educator, student, trainee, supervised operator, or other person using the app. "Patient data" means any image, radiograph, measurement, annotation, report, file, or other information that identifies a patient or relates to a patient's health.
WhereMyCup is intended for trained healthcare professionals, authorized clinical team members, educators, researchers, medical students, residents, and supervised operators. It is not intended for emergency use, unsupervised patient self-diagnosis, autonomous diagnosis, autonomous treatment selection, or sole-reliance clinical decision-making.
2. Professional consent and patient confidentiality
Before loading, scanning, photographing, measuring, saving, exporting, emailing, uploading, or sharing any X-ray, medical image, patient file, or health-related output, you must have all required patient, parent/guardian, legally authorized representative, institutional, ethical, legal, and professional authorization or consent.
You are responsible for removing, masking, cropping, or otherwise de-identifying patient identifiers whenever possible before using the app, sending support material, creating screenshots, preparing App Store or website screenshots, teaching, publication, research, or sharing. Identifiers may include names, dates of birth, patient numbers, hospital numbers, accession numbers, faces, dates, image labels, file names, QR codes, barcodes, metadata, or any other information that can identify a person.
The app shows a professional privacy, terms, and consent notice at launch. Continuing confirms that you accept responsibility for proper authorization, confidentiality, and lawful handling for that session.
3. Summary of current app data practice
WhereMyCup is designed as a local-first professional measurement aid.
The current app does not require an Orthopractis account for the measurement workflow.
The current app does not include Orthopractis cloud upload for radiographs, point coordinates, measurement outputs, reports, or graphics.
The current app does not include advertising.
The current app does not include third-party advertising tracking.
The current app does not sell or rent personal information.
The current app does not use HealthKit.
The current app does not access Contacts, Calendar, precise location, microphone, payment-card information, or device advertising identifiers.
The inspected project package does not include developer-added Firebase, AdMob, Crashlytics, RevenueCat, or another developer-added analytics, advertising, subscription, or crash-reporting SDK.
If the app is changed in the future to add analytics, crash reporting, advertising, cloud sync, server processing, user accounts, subscriptions, third-party SDKs, artificial intelligence services, remote logging, or any other data transmission, this Policy and the App Store privacy answers must be updated before or at the time of that release.
4. Information processed locally on your device
Depending on how you use the app, WhereMyCup may process the following information locally on your iPhone or iPad:
- Standing and sitting radiographic images or other medical images that you select from the photo library or capture with the camera.
- Anatomical point positions placed by the user, including standing points P1-P8 and sitting points P9/P10.
- Measurement overlays, lines, arcs, angle labels, point labels, and result text.
- Measurement outputs such as APP tilt, lumbar lordosis, standing sacral slope, sitting sacral slope, pelvic incidence, PI-LL mismatch, hip-spine classification text, and related normal-reference comparisons.
- Annotated images and text reports that you choose to create.
- Temporary files used for export and sharing.
Local processing means that these items are handled in the app on your device as part of the measurement workflow. Orthopractis does not automatically receive the image, points, measurements, reports, or exports merely because you use the app.
5. Camera, photo library, saving, and export
The app may request photo-library access so that you can load a selected radiographic image for measurement. The app may request camera access so that you can capture or scan an authorized image for measurement. The app may request permission to add to the photo library when you choose to save an annotated result image.
When you grant access, the app uses the permission for the purpose described in the system permission prompt and the in-app consent alert. You may deny or revoke permissions in device Settings. Some features may not work without the relevant permission.
Exported files may contain sensitive health-related information, including the original or loaded image, annotations, point locations, measurement values, normal-reference comparisons, diagnosis/classification text, and report text. You are responsible for reviewing, storing, protecting, deleting, and sharing those files.
If you save an image to Photos, export to Files, email, AirDrop, upload to a hospital system, share to cloud storage, send by messaging app, print, or use any other destination, that destination is controlled by you and by the receiving service. Those services may have their own terms, privacy notices, security practices, retention periods, and legal requirements. Orthopractis is not responsible for third-party destinations selected by you.
6. Data received by Orthopractis
Orthopractis does not automatically collect patient radiographs, patient identifiers, measurement coordinates, reports, or graphics from the current app workflow.
Orthopractis may receive information only when you choose to send it or when a platform provider separately provides it, for example:
- Support email: If you tap an email support link or otherwise contact Orthopractis, we may receive your email address, name, message, attachments, technical details you include, and any screenshots or files you choose to send.
- App Store or platform diagnostics: Apple may provide developers with crash, performance, or diagnostic information according to the user's Apple settings and Apple's own policies.
- Website contact form: If you submit a contact form on the Orthopractis website, we may receive the information you enter, such as name, email, phone number, and message.
- App Store purchases and downloads: Apple processes App Store downloads, purchases, refunds, ratings, and reviews under Apple's own policies. Orthopractis may receive limited developer reporting from Apple, such as aggregate sales, territories, proceeds, review text, or crash analytics, depending on Apple settings and developer dashboards.
Please do not send patient-identifiable information to Orthopractis support unless it is necessary, lawful, authorized, and appropriately de-identified where possible. If you do send patient information, you confirm that you have all required consent, authority, and legal basis to do so.
7. Website and Wix hosting
The Orthopractis website, including pages used for privacy, terms, app support, contact, and marketing, may be hosted by Wix or another website provider. Website providers may use essential cookies and similar technologies for site security, operation, fraud prevention, load balancing, language settings, and basic functionality.
If Orthopractis enables analytics, marketing tools, embedded media, social widgets, contact forms, mailing lists, chat widgets, appointment forms, payment tools, or other third-party website apps, those tools may collect additional information according to their own privacy practices. The website privacy text should be updated if those features are enabled, disabled, or changed.
If a Wix cookie banner or privacy controls are enabled, you can use those controls to manage non-essential cookies where available. You may also adjust your browser settings to block or delete cookies. Some website features may not work properly without essential cookies.
8. Purposes of processing
Where Orthopractis receives information, we may use it for the following purposes:
- To respond to support, privacy, legal, or business inquiries.
- To troubleshoot app problems that you voluntarily report.
- To maintain, improve, and document the app and website.
- To comply with App Store, legal, regulatory, tax, accounting, and security obligations.
- To protect users, patients, Orthopractis, Apple, website providers, and third parties from misuse, fraud, unlawful activity, or security incidents.
- To maintain business records related to app distribution, support, and compliance.
We do not use patient images, X-rays, health measurements, or other health-related support materials for advertising, behavioral marketing, sale, rental, or data-broker sharing.
9. Legal bases for EEA, UK, and similar privacy-law regions
When Orthopractis processes personal information that it receives, the legal basis may include one or more of the following, depending on the situation:
- Consent, where you voluntarily contact us, submit a form, send an email, or agree to receive communications.
- Performance of a contract or steps before a contract, where processing is needed to provide app support or administer app-related services.
- Legitimate interests, such as maintaining app security, responding to support requests, improving documentation, preventing misuse, and keeping business records, provided those interests are not overridden by your rights.
- Legal obligation, where processing is required for tax, accounting, consumer law, medical-device or app-store compliance, dispute handling, safety, or regulatory obligations.
For patient data that you process locally on your own device or export to your own destination, you or your institution are normally responsible for determining the lawful basis, consent, authorization, retention period, security measures, and disclosure rules. Orthopractis is not automatically the controller or processor of patient data merely because you use the local app, unless a separate written agreement says otherwise.
10. Healthcare privacy, HIPAA, GDPR, and institutional duties
WhereMyCup may be used with sensitive health-related images and adult or pediatric patient information. The professional user, healthcare provider, hospital, research institution, university, or other organization using the app is responsible for complying with applicable medical confidentiality rules, data-protection law, GDPR, HIPAA if applicable, research ethics rules, institutional review board requirements, consent requirements, record-retention duties, and local professional standards.
The app is not a hospital information system, PACS, certified electronic health record, or HIPAA business associate service by default. Orthopractis does not enter into a HIPAA business associate agreement or data-processing agreement through mere App Store download or ordinary app use. If your organization requires such an agreement or validation before using a software tool with patient data, do not use the app with identifiable patient data unless the required agreement, approval, or workflow is in place.
11. Sharing and disclosure
Orthopractis may share information it receives only as reasonably necessary for the purposes described in this Policy, for example:
- With service providers that help operate email, website hosting, domain services, security, business records, legal compliance, and support.
- With Apple or App Store systems as necessary for app distribution, purchases, reviews, diagnostics, and developer compliance.
- With professional advisors, auditors, insurers, legal representatives, or authorities where required or permitted by law.
- In connection with a business transfer, restructuring, merger, acquisition, or similar transaction, subject to appropriate safeguards.
- With your consent or at your direction.
We do not sell or rent personal information. We do not share health-related support material with advertisers or data brokers. We do not use app user data for third-party advertising tracking in the current app.
12. Retention
Local app data remains on your device, in the app sandbox, in Photos, in Files, in device backups, or in destinations you choose until you delete it or until the operating system or destination service deletes it according to its own rules. Deleting the app may remove app-sandbox data, but it may not remove files that you saved to Photos, Files, iCloud, hospital systems, email, cloud storage, or other external locations. You must delete those separately.
Support emails, website form submissions, attachments, and related correspondence may be retained as long as necessary to respond, maintain business records, comply with legal obligations, resolve disputes, preserve safety information, and protect legitimate interests. Where applicable, you may request deletion of support material that you voluntarily sent to Orthopractis, subject to legal, security, regulatory, accounting, dispute, or backup limitations.
13. Security
The app relies on Apple platform protections, app sandboxing, local device storage, system permission prompts, the system photo picker/share sheet, and user-controlled export actions. Orthopractis uses reasonable administrative and technical measures for support communications and website information it receives.
No app, device, website, email system, cloud storage, or export destination can be guaranteed completely secure. You are responsible for securing the device, screen lock, account passwords, backups, exported files, screenshots, printed materials, emails, AirDrop destinations, cloud folders, hospital uploads, and recipients. Do not store or share patient-identifiable information unless you have authorization and the destination is appropriate for that type of information.
14. Your choices and controls
You can choose not to use the app with patient-identifiable information.
You can choose to use de-identified, cropped, masked, or synthetic images where possible.
You can deny or revoke camera and photo-library permissions in device Settings.
You can choose whether to save, export, email, AirDrop, upload, print, or share files.
You can review exported files before sending them.
You can delete exported files from Photos, Files, email, cloud storage, and other destinations you control.
You can contact Orthopractis at info@orthopractis.com to request access, correction, deletion, or information about support material that you voluntarily sent to us.
You can manage website cookies through the Wix cookie banner where available, browser settings, or device settings.
15. Privacy rights
Depending on your location and applicable law, you may have rights to request access, correction, deletion, restriction, portability, objection, withdrawal of consent, and information about how personal information is processed. You may also have the right to lodge a complaint with a data protection authority or other regulator.
To make a request, contact info@orthopractis.com. We may need to verify your identity and may be unable to respond to requests about data that Orthopractis does not control, such as files stored only on your device or data held by your hospital, Apple, Wix, email provider, cloud provider, or another third party.
16. Children
WhereMyCup is not intended for unsupervised use by children. If the app is used with pediatric images, the professional user is responsible for all required parent/guardian consent, institutional approval, privacy safeguards, and professional supervision.
17. International use
You are responsible for complying with the laws and professional rules that apply in your country, region, institution, or clinical environment. If use of the app or a feature is not lawful or appropriate in your location, do not use that feature.
18. Changes to this Policy
Orthopractis may update this Policy to reflect app changes, website changes, App Store requirements, legal requirements, platform changes, privacy-practice changes, support-process changes, or business changes. The updated version should be posted at https://www.orthopractis.com/privacy or another stable Orthopractis privacy URL with an updated effective date.
19. Contact
Questions about this Policy, privacy choices, app support, or deletion requests concerning support material voluntarily sent to Orthopractis may be sent to:
ORTHOPRACTIS.COM SINGLE MEMBER P.C. / Orthopractis
Website: https://www.orthopractis.com
Support page: https://www.orthopractis.com/
Privacy Policy URL: https://www.orthopractis.com/privacy
Terms of Use URL: https://www.orthopractis.com/terms-of-use
Support email: info@orthopractis.com
Effective date: July 4, 2026
This Privacy Policy describes how Orthopractis handles information in connection with SonoHipAngles.
1. Purpose of the app
SonoHipAngles helps authorized users place reference lines on a hip ultrasound image and calculate α and β angle measurements. The app output is assistive only and must be reviewed by a qualified clinician.
2. Image handling
The app allows the user to select an image from the device photo library. The selected image is used inside the app so the user can place measurement points. The app is designed to process the selected image locally on the device and does not include a built-in account system, advertising network, analytics service, or automatic image upload feature.
3. Patient information
Users should select only images they are authorized to review. Users should avoid patient-identifying information in selected images unless appropriate consent, authorization, and clinical safeguards are in place. Responsibility for lawful image selection, patient consent, and clinical record handling remains with the user and the relevant healthcare organization.
4. Data collected by the app
SonoHipAngles is configured to collect no personal data for tracking and to declare no collected data in its privacy manifest. The app does not require account registration. Measurements, selected side, age in months, and line positions are used for on-screen calculation during the session.
5. Support communications
If a user contacts support by email at info@orthopractis.com, the user's email address and the information included in the message may be received and used to respond to the request. Users should not send patient-identifying information by email unless they are permitted to do so and the transmission method is appropriate for their organization.
6. Website links
The app links to Orthopractis webpages for support, privacy information, and terms. Website hosting, browser cookies, server logs, and website analytics, if enabled on the website, are separate from the app and should be managed according to the website configuration and published website policy.
7. Data sharing
The app does not include advertising tracking or sale of personal data. Information voluntarily sent to support may be handled for support, troubleshooting, administrative, or legal purposes.
8. Security
Users should use device-level protections such as passcodes, biometric unlock, system updates, and organization-approved storage practices. No app can guarantee absolute security.
9. Children and patients
The app may be used with pediatric ultrasound images only by authorized users and only with appropriate consent and safeguards. The app is not intended for unsupervised use by children.
10. User choices
Users can choose not to select an image. Users can remove images from the device photo library using system photo-management tools. Users can contact support about privacy questions at info@orthopractis.com.
11. Changes
Orthopractis may update this Privacy Policy. The updated version should be posted in the app or on the website.
Contact
Support URL: https://www.orthopractis.com
Privacy Policy URL: https://www.orthopractis.com/privacy
Support email: info@orthopractis.com
HipDysplasiaPro Privacy Policy
Effective date: July 3, 2026
Last updated: July 3, 2026
1. Scope
This Privacy Policy explains how HipDysplasiaPro, including the iOS, iPadOS, and native visionOS versions, handles information when the app is installed, opened, used, saved from, exported from, or supported. It also explains how the Orthopractis website pages used for app support, privacy, and terms may handle information when hosted on Wix or another website provider.
In this policy, "HipDysplasiaPro", "the app", "we", "us", and "our" refer to the app and to Orthopractis where Orthopractis receives information. "You" means the app user, website visitor, healthcare professional, researcher, educator, student, trainee, supervised operator, or other person using the app. "Patient data" means any image, X-ray, measurement, annotation, report, file, or other information that can identify a patient or relates to a patient's health.
HipDysplasiaPro is intended for trained healthcare professionals, authorized clinical team members, educators, researchers, medical students, residents, and supervised operators. It is not intended for unsupervised patient self-diagnosis, emergency use, or autonomous clinical decision-making.
2. Professional consent and patient confidentiality
Before loading, scanning, photographing, measuring, saving, exporting, emailing, uploading, or sharing any X-ray, medical image, patient file, or health-related output, you must have all required patient, parent/guardian, legally authorized representative, institutional, ethical, legal, and professional authorization or consent.
You are responsible for removing, masking, cropping, or otherwise de-identifying patient identifiers whenever possible before using the app, sending support material, creating screenshots, preparing App Store or website screenshots, teaching, publication, research, or sharing. Identifiers may include names, dates of birth, patient numbers, hospital numbers, accession numbers, faces, dates, labels printed on an image, file names, QR codes, barcodes, metadata, or any other information that can identify a person.
The app shows a professional privacy, terms, and consent notice at launch. Tapping "I Consent & Continue" confirms that you accept responsibility for proper authorization, confidentiality, and lawful handling for that session.
3. Summary of the current app data practice
As currently implemented, HipDysplasiaPro is designed as a local-first professional measurement and planning-support app.
The current app does not require an Orthopractis account.
The current app does not include Orthopractis cloud upload for X-rays, measurements, point coordinates, reports, or graphics.
The current app does not include advertising.
The current app does not include third-party advertising tracking.
The current app does not sell or rent personal information.
The current app does not use HealthKit.
The current app does not access Contacts, Calendar, precise location, microphone, or payment-card information.
The current app does not use Firebase, AdMob, Crashlytics, RevenueCat, or another developer-added analytics, advertising, subscription, or crash-reporting SDK in the inspected project package.
The current Apple privacy manifest declares no tracking and no app-collected data, and declares UserDefaults access for app functionality.
If the app is changed in the future to add analytics, crash reporting, advertising, cloud sync, server processing, user accounts, subscriptions, third-party SDKs, artificial intelligence services, remote logging, or any other data transmission, this policy and the App Store privacy answers must be updated before or at the time of that release.
4. Information processed locally on your device
Depending on how you use the app, the app may process the following information locally on your iPhone, iPad, or Apple Vision Pro:
- X-ray images or other medical images that you load from the photo library, select with a picker, open from Files, or capture with the camera.
- Landmark positions and point coordinates that you place on the image.
- Measurement overlays, lines, circles, angles, and labels.
- Patient-related calculation inputs that you enter, such as age, age in months, sex/gender selection, patient height, patient weight, calibration length, unit length, and other numeric values required by the measurement workflow.
- Radiographic and biomechanical outputs, including right and left hip measurements, CE angle, sigma, theta, phi, psi, d5/d6 values, t-prime/y values, acetabular and osteotomy-related measurements, load values, pressure values, and normal-reference comparisons.
- Graphic analysis outputs, including right and left hip chart data, R/G5 load graphs versus sigma, P/G5 pressure graphs versus sigma, P/G5 pressure graphs versus theta, printed normal reference values, X-ray thumbnails, decision tables, and report tables.
- Annotated images, exported text reports, graphic PNG images, and export packages that you choose to create.
- App settings and consent-related local state, such as whether point guidance is enabled and whether the privacy/terms consent notice was accepted for a session.
Local processing means that these items are handled in the app on your device as part of the measurement workflow. Orthopractis does not automatically receive the image, points, measurements, reports, graphs, or exports merely because you use the app.
5. Camera, photo library, Files, saving, and export
The iOS and iPadOS app may request camera access so that you can capture or scan an X-ray image for measurement. It may request photo-library access so that you can load an image and save an annotated result image. It may use Files, app Documents storage, or the system share sheet so that you can export reports and graphics.
When you grant access, the app uses the permission for the purpose described in the system permission prompt. You may deny or revoke permissions in device Settings. Some features may not work without the relevant permission.
The app may write exported files into the app Documents folder, for example under a HipDysplasiaPro export folder, so the system share sheet can read and share them. Exported files may contain sensitive health-related information, including the original or loaded X-ray image, annotations, point locations, measurement values, load and pressure values, normal-reference comparisons, right and left hip graphs, osteotomy planning graphics, and report text. You are responsible for reviewing, storing, protecting, deleting, and sharing those files.
If you save an image to Photos, export to Files, email, AirDrop, upload to a hospital system, share to cloud storage, send by messaging app, print, or use any other destination, that destination is controlled by you and by the receiving service. Those services may have their own terms, privacy notices, security practices, retention periods, and legal requirements. Orthopractis is not responsible for third-party destinations selected by you.
6. visionOS, world sensing, immersive board, and accessory tracking
The native visionOS version may request photo-library access so that you can select an X-ray image for measurement. It may request world-sensing permission so that the app can place the immersive measurement board, mesh, points, lines, and text in space in front of the user. It may request accessory-tracking permission when a supported Muse or spatial stylus accessory is connected so that distal/tip gestures can be used to select announced hip landmarks on the immersive board.
The visionOS world-sensing and accessory features are used for local spatial presentation and local point-selection interaction. The current app does not upload world-sensing scene information, environment meshes, accessory-tracking data, X-rays, point coordinates, measurements, reports, or graphics to an Orthopractis cloud service as part of the normal workflow.
7. Data collected by Orthopractis
Orthopractis does not automatically collect patient X-rays, patient identifiers, measurement coordinates, right/left hip measurements, reports, or graphics from the current app workflow.
Orthopractis may receive information only when you choose to send it or when a platform provider separately provides it, for example:
- Support email: If you tap an email support link or otherwise contact Orthopractis, we may receive your email address, name, message, attachments, technical details you include, and any screenshots or files you choose to send.
- App Store or platform diagnostics: Apple may provide developers with crash, performance, or diagnostic information according to the user's Apple settings and Apple's own policies. We do not intentionally collect patient images through developer-added analytics code in the current app.
- Website contact form: If you submit a contact form on the Orthopractis website, we may receive the information you enter, such as name, email, phone number, and message.
- App Store purchases and downloads: Apple processes App Store downloads, purchases, refunds, subscriptions, ratings, and reviews under Apple's own policies. Orthopractis may receive limited developer account reporting from Apple, such as aggregate sales, territories, proceeds, review text, or crash analytics, depending on Apple settings and developer dashboards.
Please do not send patient-identifiable information to Orthopractis support unless it is necessary, lawful, authorized, and appropriately de-identified where possible. If you do send patient information, you confirm that you have all required consent, authority, and legal basis to do so.
8. Website and Wix hosting
The Orthopractis website, including pages used for privacy, terms, app support, contact, and marketing, may be hosted by Wix or another website provider. Website providers may use essential cookies and similar technologies for site security, operation, fraud prevention, load balancing, language settings, and basic functionality. If Orthopractis enables analytics, marketing tools, embedded media, social widgets, contact forms, mailing lists, or other third-party website apps, those tools may collect additional information according to their own privacy practices.
If a Wix cookie banner or privacy controls are enabled, you can use those controls to manage non-essential cookies where available. You may also adjust your browser settings to block or delete cookies. Some website features may not work properly without essential cookies.
The website privacy content should be updated if Orthopractis changes the website tools, adds newsletters, online payments, appointment forms, chat widgets, advertising pixels, analytics services, or other data-collecting features.
9. Purposes of processing
Where Orthopractis receives information, we may use it for the following purposes:
- To respond to support, privacy, legal, or business inquiries.
- To troubleshoot app problems that you voluntarily report.
- To maintain, improve, and document the app and website.
- To comply with App Store, legal, regulatory, tax, accounting, and security obligations.
- To protect users, patients, Orthopractis, Apple, website providers, and third parties from misuse, fraud, unlawful activity, or security incidents.
- To maintain business records related to app distribution, support, and compliance.
We do not use patient images, X-rays, health measurements, face/body data, or other health-related support materials for advertising, behavioral marketing, sale, rental, or data-broker sharing.
10. Legal bases for users in the European Economic Area, United Kingdom, and similar regions
When Orthopractis processes personal information that it receives, the legal basis may include one or more of the following, depending on the situation:
- Consent, where you voluntarily contact us, submit a form, send an email, or agree to receive communications.
- Performance of a contract or steps prior to a contract, where processing is needed to provide app support, respond to requests, or administer app-related services.
- Legitimate interests, such as maintaining app security, responding to support requests, improving documentation, preventing misuse, and keeping business records, provided those interests are not overridden by your rights.
- Legal obligation, where processing is required for tax, accounting, consumer law, medical-device or app-store compliance, dispute handling, safety, or regulatory obligations.
- Vital interests or public interest, only in rare circumstances where applicable law permits or requires it.
For patient data that you process locally on your own device or export to your own destination, you or your institution are normally responsible for determining the lawful basis, consent, authorization, retention period, security measures, and disclosure rules. Orthopractis is not automatically the controller or processor of patient data merely because you use the local app, unless a separate written agreement says otherwise.
11. Healthcare privacy, HIPAA, GDPR, and institutional duties
HipDysplasiaPro may be used with sensitive health-related images and pediatric or adult patient information. The professional user, healthcare provider, hospital, research institution, university, or other organization using the app is responsible for complying with applicable medical confidentiality rules, data-protection law, GDPR, HIPAA if applicable, research ethics rules, institutional review board requirements, consent requirements, record-retention duties, and local professional standards.
The app is not a hospital information system, PACS, certified electronic health record, or HIPAA business associate service by default. Orthopractis does not enter into a HIPAA business associate agreement or data-processing agreement through mere App Store download or ordinary app use. If your organization requires such an agreement or validation before using a software tool with patient data, do not use the app with identifiable patient data unless the required agreement, approval, or workflow is in place.
12. Sharing and disclosure
Orthopractis may share information it receives only as reasonably necessary for the purposes described in this policy, for example:
- With service providers that help operate email, website hosting, domain services, security, business records, legal compliance, and support.
- With Apple or App Store systems as necessary for app distribution, purchases, reviews, diagnostics, and developer compliance.
- With professional advisors, auditors, insurers, legal representatives, or authorities where required or permitted by law.
- In connection with a business transfer, restructuring, merger, acquisition, or similar transaction, subject to appropriate safeguards.
- With your consent or at your direction.
We do not sell or rent personal information. We do not share health-related support material with advertisers or data brokers. We do not use app user data for third-party advertising tracking in the current app.
13. Retention
Local app data remains on your device, in the app sandbox, in Photos, in Files, in device backups, or in destinations you choose until you delete it or until the operating system or destination service deletes it according to its own rules. Deleting the app may remove app-sandbox data, but it may not remove files that you saved to Photos, Files, iCloud, hospital systems, email, cloud storage, or other external locations. You must delete those separately.
Support emails, website form submissions, attachments, and related correspondence may be retained as long as necessary to respond, maintain business records, comply with legal obligations, resolve disputes, preserve safety information, and protect legitimate interests. Where applicable, you may request deletion of support material that you voluntarily sent to Orthopractis, subject to legal, security, regulatory, accounting, dispute, or backup limitations.
14. Security
The app relies on Apple platform protections, app sandboxing, local device storage, system permission prompts, the system photo picker/share sheet, and user-controlled export actions. Orthopractis uses reasonable administrative and technical measures for support communications and website information it receives.
No app, device, website, email system, cloud storage, or export destination can be guaranteed completely secure. You are responsible for securing the device, screen lock, account passwords, backups, exported files, screenshots, printed materials, emails, AirDrop destinations, cloud folders, hospital uploads, and recipients. Do not store or share patient-identifiable information unless you have authorization and the destination is appropriate for that type of information.
15. Your choices and controls
You can choose not to use the app with patient-identifiable information.
You can choose to use de-identified, cropped, masked, or synthetic images where possible.
You can deny or revoke camera, photo library, world-sensing, and accessory-tracking permissions in device Settings.
You can choose whether to save, export, email, AirDrop, upload, print, or share files.
You can review exported files before sending them.
You can delete exported files from the app Documents folder, Files, Photos, email, cloud storage, and other destinations you control.
You can contact Orthopractis at info@orthopractis.com to request access, correction, deletion, or information about support material that you voluntarily sent to us.
You can manage website cookies through the Wix cookie banner where available, browser settings, or device settings.
16. Privacy rights
Depending on your location and applicable law, you may have rights to request access, correction, deletion, restriction, portability, objection, withdrawal of consent, and information about how personal information is processed. You may also have the right to lodge a complaint with a data protection authority or other regulator.
To exercise rights concerning information that Orthopractis actually received, contact info@orthopractis.com. We may need to verify your identity and the scope of your request. We may not be able to access or delete local data that remains only on your device or in destinations you selected. For patient records controlled by a healthcare provider or institution, contact that provider or institution.
17. Children and pediatric patient data
The app is not directed to children as app users. It is intended for professional or supervised adult use. Because hip dysplasia workflows may involve pediatric patients, the app may be used with images or data of children only by qualified or supervised users who have all required parent/guardian, legally authorized representative, institutional, ethical, and legal consent or authorization.
Do not allow a child or unsupervised patient to use the app for self-diagnosis, treatment decisions, emergency decisions, or unsupervised sharing of medical images.
18. International transfers
Orthopractis is based in Greece. Apple, Wix, email providers, website providers, and other service providers may process information in other countries according to their own operations and applicable safeguards. Where required, Orthopractis relies on appropriate legal mechanisms for international transfers, such as adequacy decisions, contractual safeguards, consent, necessity for support, or other mechanisms permitted by law.
19. Automated decision-making and profiling
The current app does not use Orthopractis cloud profiling, advertising profiling, or automated decisions that produce legal or similarly significant effects about app users. App outputs, measurements, graphs, normal-reference comparisons, decision tables, and labels are calculation and visualization tools. They must be independently reviewed by qualified professionals and must not be used as autonomous diagnosis or treatment decisions.
20. Changes to this Privacy Policy
Orthopractis may update this Privacy Policy to reflect app changes, website changes, App Store requirements, legal requirements, platform changes, privacy-practice changes, or support-process changes. The updated version should be posted at https://www.orthopractis.com/privacy or another stable Orthopractis privacy-policy URL with an updated effective date. Continued use after an update means the updated policy applies to later use.
21. Contact
For privacy questions, support requests, access requests, deletion requests concerning support material voluntarily sent to Orthopractis, or questions about this policy, contact:
ORTHOPRACTIS.COM SINGLE MEMBER P.C.
Orthopractis / Orthopractis.com
Email: info@orthopractis.com
Website: https://www.orthopractis.com
Privacy Policy URL: https://www.orthopractis.com/privacy
Terms of Use URL: https://www.orthopractis.com/terms-of-use
AcetabularIndexApp Android ios Privacy Policy
Effective date: 30 June 2026
Developer: Orthopractis / Orthopractis.com Single Member P.C.
Website: https://www.orthopractis.com
App page: https://www.orthopractis.com/acetabular-index-app
Privacy Policy: https://www.orthopractis.com/privacy
Terms of Use: https://www.orthopractis.com/terms-of-use
Support email: info@orthopractis.com
1. Scope
This Privacy Policy section explains how AcetabularIndexApp for Android handles information when the app is used on an Android device. The app is intended for trained healthcare professionals, authorized clinical team members, educators, researchers, medical students, residents, and supervised operators. It is not intended for unsupervised patient self-diagnosis, treatment decisions, emergency use, or use by children as app users.
2. Local image processing
The app allows the user to load an image from the Android image picker or capture an image using the device camera. The selected or captured image may be used locally on the device for acetabular-index landmark placement, right and left angle measurement, drawing overlays, reference comparison, result display, access to the included osteotomy planning-support workflow, and optional user-controlled saving/export.
In this Android build, image processing is performed locally on the device. The app does not automatically upload user-selected images, camera-captured images, measurements, landmark positions, drawings, saved result images, screenshots, or reports to an Orthopractis server.
3. Information processed by the app
When the user chooses to use related features, the app may process on the device:
- images selected by the user through the Android image picker;
- images captured by the user through the camera;
- X-rays or other health-related images chosen by the user;
- age, gender, side, and reference-comparison inputs entered or selected by the user;
- landmark positions, circular/crosshair target positions, lines, overlays, drawings, and angle values;
- acetabular-index results and labels;
- osteotomy planning-support values, if the user opens the included Osteotomy module;
- user-created result images saved by the user.
4. Data collected by the developer
Based on this Android build, the app does not include account creation, login, advertising SDKs, analytics SDKs, tracking SDKs, or developer-operated cloud upload functionality. Orthopractis does not automatically collect user-selected images, camera-captured images, measurement outputs, landmark positions, saved result images, device identifiers, location data, contacts, or usage analytics through this build.
If the app is modified later to include analytics, crash reporting, advertising, cloud storage, remote support upload, user accounts, subscriptions, AI APIs, or any other network service, this Privacy Policy and the Google Play Data safety form must be updated before release.
5. Patient and sensitive health information
Images selected or captured by users may include X-rays or other health-related files. These files may contain personal information, patient-identifiable information, or sensitive health data. Users are responsible for obtaining all necessary patient, subject, parent/guardian, institutional, legal, ethical, and professional consent or authorization before loading, scanning, saving, exporting, sharing, emailing, uploading, or storing any health-related file or app output.
Users should remove or obscure patient identifiers whenever possible before using images for screenshots, testing, support requests, teaching, publication, consultation, or sharing. Users must comply with applicable privacy law, professional duties, institutional policy, and local law.
6. Camera and image permissions
Camera access is used only when the user chooses the Scan/camera feature to capture an image for local measurement or planning-support review. The camera is not used in the background.
Image-picker access is initiated by the user when the user chooses to load an image. The inspected Android build does not request broad all-files access or broad Android 13+ READ_MEDIA_IMAGES/READ_MEDIA_VIDEO permissions.
On Android 9 and below, legacy write-storage permission may be used only to save user-created result images. On modern Android versions, saving uses Android media storage behavior.
7. Saving, exporting, and sharing
When the user taps Save, the app may create an annotated result image on the device, for example in the device gallery or Pictures/AcetabularIndexApp folder depending on Android version and device settings. Saved images remain under the user's control and may be visible to other apps that have access to the user's gallery or files.
The app does not automatically share saved files. If the user chooses to save, export, share, email, upload, back up, or store files outside the app, that action is controlled by the user and by the external destination selected by the user, such as the device gallery, file manager, email app, messaging app, cloud storage provider, institutional system, or backup service. Those external services have their own privacy and security practices.
8. Support communications
If a user voluntarily contacts Orthopractis by email or sends attachments, screenshots, exported files, device information, comments, or other materials, Orthopractis may use those materials to respond to the request, provide support, investigate issues, improve documentation, maintain security, protect legal rights, or comply with legal obligations.
Users should not send patient-identifiable or sensitive health information to support unless they have the required authorization and the information is necessary for support. Users should de-identify screenshots and files before sending them whenever possible.
9. Data sharing
This Android build does not automatically share user images, measurements, landmarks, drawings, or saved result files with Orthopractis or third parties. Orthopractis does not sell app data. User-controlled actions, such as saving, exporting, emailing, uploading, or sharing files through another app or service, are initiated by the user and may be governed by the privacy terms of the selected third-party service.
Orthopractis may disclose support communications if required by law, to protect legal rights, to prevent abuse or security harm, or to service providers that process information on Orthopractis's behalf under appropriate obligations.
10. Retention and deletion
The app does not maintain an Orthopractis cloud account or server-side image archive in this build. Images and result files saved by the user remain on the user's device or selected destination until the user deletes them using Android gallery, files, device-management, cloud-storage, or other relevant tools.
Deleting the app may remove app-local data but may not remove images previously saved to the gallery, external storage, email, cloud storage, institutional systems, backups, or other destinations selected by the user.
Support emails and attachments voluntarily sent to Orthopractis may be retained as necessary to respond to the request, maintain business records, comply with legal duties, resolve disputes, enforce terms, and protect legitimate interests. Users may contact info@orthopractis.com to request deletion of support communications where applicable, subject to legal or legitimate retention requirements.
11. Security
The app is designed to process images locally and to avoid automatic server upload in this build. Users remain responsible for securing their device, controlling access to saved images, using device passcodes or encryption where appropriate, limiting access to screenshots and galleries, and following institutional confidentiality requirements.
No method of electronic storage or transmission is completely secure. Users should apply appropriate professional, technical, and organizational safeguards when handling health-related images or outputs.
12. Children and minors
AcetabularIndexApp is not directed to children as app users. The app may be used by adult professionals with pediatric patient images only when appropriate consent, parent/guardian or legally authorized representative authorization, institutional approval, and local-law compliance are in place. The app should not be used by minors for self-diagnosis or treatment decisions.
13. Professional-use and medical disclaimer
AcetabularIndexApp is a planning-support, education, research, reference, and workflow-validation tool. It does not provide medical advice, diagnose, treat, prescribe, make autonomous clinical decisions, replace professional judgment, replace formal training, replace institutional protocols, or guarantee measurement accuracy, clinical suitability, regulatory status, or outcomes. Users remain responsible for image quality, calibration/landmark placement, calculations, patient consent, privacy compliance, independent review, and final decisions.
14. International use
Users are responsible for ensuring that their use of the app, patient images, saved outputs, exports, support communications, and any international transfer of information complies with the laws, professional rules, institutional policies, and patient-consent requirements that apply to them.
15. Changes to this Privacy Policy
Orthopractis may update this Privacy Policy section from time to time. The current version should be posted at https://www.orthopractis.com/privacy or another stable public privacy-policy page with an updated effective date.
16. Contact
For privacy questions, access requests, deletion requests concerning support material voluntarily sent to Orthopractis, or other support questions, contact: info@orthopractis.com.
PlaneAncor Policy
Effective date: 2026-06-27
Contact: info@orthopractis.com
Support: https://www.orthopractis.com/PlaneAncor
Privacy URL: https://www.orthopractis.com/privacy
Overview
PlaneAncor is an augmented reality and spatial computing application for iPhone, iPad, and Apple Vision Pro. It helps users detect physical planes, create a Matching Coordinate System, load user-selected 3D assets, and optionally synchronize selected session state with trusted nearby devices.
Data processed on device
PlaneAncor may process camera/world-sensing information used by ARKit, RealityKit, and visionOS to detect planes, track the device, and render spatial content. PlaneAncor may also process imported 3D files selected by the user, Matching Coordinate System transforms, asset transforms, measurements, selection state, edit events, delete events, and export/share state.
User-selected files
Users choose which USDZ, USD, USDC, OBJ, STL, FBX, or related files to import. Imported files may be copied into the app container so the operating system can load them reliably and so the user can export/share the original asset or a transform manifest.
Connected sessions
When users intentionally connect nearby devices, PlaneAncor may share selected session data with connected trusted participants. Shared data can include Matching CS transforms, group-origin proposals and acceptances, loaded asset state or asset payloads, asset transform edits, measurements, delete events, export/share state, and basic connection status.
Cross visibility and shared origin
Cross visibility is achieved by sharing the accepted Matching CS origin and asset transforms. Each device keeps its own local tracking, but renders shared assets relative to the agreed origin. This allows iPhone, iPad, and Apple Vision Pro participants to review the same intended physical placement without requiring raw camera streaming.
Camera and world sensing
Camera and spatial tracking are used to detect planes and place content. The default PlaneAncor workflow does not send raw camera images to a developer server. Users should not scan restricted, confidential, private, or sensitive environments unless authorized.
Local network / nearby discovery
PlaneAncor may use local network or nearby-device discovery so trusted participants can connect for collaboration. Users control when to connect and should connect only with trusted participants in authorized spaces.
Apple Vision Pro / visionOS
On Apple Vision Pro, PlaneAncor may use spatial tracking, surroundings-related data, and system gesture input as needed to display and manipulate content in a spatial computing experience. The final App Store privacy answers must match the final submitted build, including any surroundings, hands, head, or body data categories if the app directly collects or shares them.
No advertising tracking
The default PlaneAncor project does not include advertising tracking, third-party analytics tracking, cross-app tracking, or an App Tracking Transparency request. If analytics, accounts, cloud services, or tracking SDKs are added later, this policy and App Store privacy answers must be updated before release.
Storage
Imported files and session manifests may be stored in the app container. Deleting the app removes files stored only in that container. Files exported to other apps, shared with nearby participants, or saved by the user may remain outside PlaneAncor.
User control
Users control when to scan, import files, connect devices, share/export, accept a proposed group origin, and delete loaded assets from a session.
Children and professional environments
PlaneAncor is intended for professional, educational, engineering, design, and spatial planning workflows. It is not directed to children. Users should follow workplace, school, and client confidentiality rules.
Changes to this policy
The policy may be updated when app features, data handling, platforms, or legal requirements change. The current policy should remain available at the privacy URL.
Contact
For privacy questions, access requests, deletion requests, or support, contact info@orthopractis.com.
Privacy Policy for CupAnteversionInclinationApp Android
Effective date: June 24, 2026
Developer: Orthopractis
Support email: info@orthopractis.com
App/support page: https://www.orthopractis.com/cup-anteversion-inclination-app
General privacy page: https://www.orthopractis.com/privacy
1. Scope
This Privacy Policy section explains how CupAnteversionInclinationApp Android handles information when the app is used on an Android device.
The app is intended for trained healthcare professionals, authorized clinical team members, educators, researchers, and supervised operators. It is not intended for unsupervised patient self-diagnosis or emergency use.
2. Local image processing
The app allows the user to load an image from the Android image picker or capture an image using the camera. The selected or captured image may be used locally on the device for landmark placement, drawing overlays, measurement calculation, result display, and optional user-controlled saving/export.
In this Android build, image processing is performed locally on the device. The app does not automatically upload images, measurements, landmarks, saved result images, or screenshots to an Orthopractis server.
3. Data collected by the developer
The Android app does not include account creation, login, advertising SDKs, analytics SDKs, tracking SDKs, or app-server upload code.
Based on this build, Orthopractis does not automatically collect user-selected images, camera-captured images, measurement outputs, saved result images, device identifiers, location data, contacts, or usage analytics through the app.
If the app is modified later to include analytics, crash reporting, cloud storage, user accounts, advertising, remote support upload, or other network services, this policy and the Google Play Data Safety form must be updated before release.
4. User-selected health images
Images used in the app may include X-rays or other health-related files. These files may contain personal, sensitive, or patient-identifiable information.
Users are responsible for obtaining all necessary patient, subject, institutional, legal, and ethical consent or authorization before loading, scanning, saving, exporting, storing, or sharing health-related files.
Users should remove or obscure patient identifiers where required and must comply with applicable confidentiality duties, professional rules, institutional policies, and data-protection laws.
5. Camera and image permissions
Camera access is used only when the user chooses the Scan function to capture an image for local measurement. The camera is not used in the background.
Image-picker access is used only when the user chooses to load an image. The app does not request broad all-files access in this build.
On older Android versions, storage permission may be used only when needed for user-controlled saving of captured or annotated images. On modern Android versions, the app uses Android media storage behavior for saving/export.
6. Saving and sharing
When the user taps Save, the app may create an annotated result image on the device. Saved images remain under the user’s control and may be visible in the device gallery or Pictures folder depending on Android version and device settings.
The app does not automatically share saved files. If the user shares a saved image by email, messaging, cloud storage, or another app, that sharing is controlled by the user and by the third-party service selected by the user.
7. Support communications
If a user voluntarily contacts Orthopractis by email or sends attachments, screenshots, device information, comments, or other materials, those materials are handled as support communications outside automatic app collection.
Users should not send patient-identifiable or sensitive health information to support unless they have the required authorization and the information is necessary for support. Orthopractis may use support communications to respond to the request, investigate issues, improve documentation, and maintain records as required.
8. Data sharing
This Android build does not automatically share user data with Orthopractis or third parties.
User-controlled actions, such as saving, exporting, emailing, or sharing files through another app, are initiated by the user and may be governed by the privacy terms of the selected third-party service.
9. Security and confidentiality
The app is designed to process images locally and to avoid automatic server upload in this build. Users remain responsible for securing their device, controlling access to saved images, using device passcodes or encryption where appropriate, and following institutional confidentiality requirements.
No method of electronic storage or transmission is completely secure. Users should apply appropriate professional, technical, and organizational safeguards when handling health-related images.
10. Retention and deletion
The app does not maintain an Orthopractis cloud account or server-side image archive in this build.
Images saved by the user remain on the user’s device until the user deletes them using Android gallery, file manager, app storage, or device-management tools.
Support emails and attachments voluntarily sent to Orthopractis may be retained as necessary to respond to the request, maintain business records, comply with legal duties, and protect legitimate interests. Users may contact info@orthopractis.com to request deletion of support communications where applicable.
11. Children and patients
The app is intended for professional or supervised use by adults and is not directed to children. It is not designed for patients to use independently for self-diagnosis, treatment decisions, or emergency decisions.
12. Changes to this policy
Orthopractis may update this Privacy Policy section from time to time. The current version should be posted at https://www.orthopractis.com/privacy or an equivalent public privacy-policy page.
13. Contact
Questions about this Privacy Policy section or the app’s privacy practices can be sent to: info@orthopractis.com.
OsteotomyApp Android Privacy Notice
Effective date: 23/6/2026
Developer: Orthopractis.com Smpc
Contact: info@orthopractis.com
Website: https://www.orthopractis.com
App: OsteotomyApp Android
OsteotomyApp is a professional-use osteotomy planning-support application for trained healthcare professionals, supervised clinical team members, educators, and researchers.
Data accessed by the app
When the user chooses to use related features, the app may access or process:
• camera images captured by the user;
• images selected by the user through the Android image picker, including X-ray or medical images;
• calibration values entered by the user;
• landmark positions, lines, drawings, measurement values, and osteotomy-planning visualizations;
• result images saved by the user to the device gallery or other user-selected storage location.
Local processing
The Android app processes selected/captured images, calibration, landmarks, drawings, and measurement outputs locally on the device. The app does not include advertising SDKs, analytics SDKs, third-party tracking SDKs, user accounts, or developer-operated cloud upload functionality in this build.
Camera and image permissions
Camera permission is requested only when the user chooses the Scan/camera feature. Image selection is initiated by the user through the Android system image picker. Legacy storage write access may be used on older Android versions only to save user-created result images.
Sharing and exports
The app does not automatically upload images, measurements, reports, or result files to Orthopractis or a third-party server. If the user chooses to save, export, share, email, upload, back up, or store files outside the app, that action is controlled by the user and by the external destination, such as the device gallery, file manager, email app, cloud storage provider, institution system, or messaging service.
Patient and sensitive health information
Images selected or captured by users may contain health information or patient-identifying information. Users are responsible for obtaining all required patient/subject consent, authorization, institutional approval, and local-law compliance before using, saving, exporting, sharing, emailing, uploading, or storing any image or output. Users should remove patient-identifying information whenever possible before saving or sharing screenshots or support materials.
Support emails
If a user voluntarily emails Orthopractis support and includes personal information, screenshots, exported files, or attachments, Orthopractis will use that message only for support, safety, security, legal, or dispute-resolution purposes. Support materials can be deleted on request unless retention is required by law or legitimate security, accounting, or dispute needs.
Retention and deletion
The app does not maintain a developer server-side account or cloud database for app images or measurements. User-created saved images remain where the user saved them, such as the device gallery or another destination selected by the user. Users can delete locally saved images from their device gallery, files app, or chosen storage destination. Support email deletion requests may be sent to info@orthopractis.com.
Children
OsteotomyApp is not directed to children. Do not use the app with minors or sensitive health-related data unless appropriate parent/guardian or legally authorized consent, institutional approval, and local-law compliance are in place.
Professional-use and medical disclaimer
OsteotomyApp is a planning-support, education, research, and workflow-validation tool. It does not provide medical advice, diagnose, treat, prescribe, make autonomous clinical decisions, replace professional judgment, or guarantee measurement accuracy or clinical suitability. Users remain responsible for image quality, calibration, landmark placement, calculations, patient consent, privacy compliance, independent review, and final clinical decisions.
OrthoSpine Privacy Policy
Last updated: 21 June 2026
Contact: info@orthopractis.com
Website: https://www.orthopractis.com/privacy
1. Purpose
OrthoSpine is an iOS-only professional/research support app for posterior spine surface capture, local mesh export, scoliosis-related surface measurement suggestions, including proposed OSAI-R/dOSAI research-support outputs, and measurement review. It is intended for appropriately trained healthcare professionals, researchers, or supervised operators.
2. Camera, ARKit, LiDAR and body information
The app uses the device camera, ARKit, LiDAR/depth, Vision body-pose detection, and local SceneKit/ModelIO processing to recognize a posterior spine corridor, place left/right rail capture points, build a local surface mesh, and calculate support measurements. These workflows may involve environment scanning, body-pose landmarks, surface mesh data, reports, exported USDZ/STL/PLY/XYZ files, and scoliosis/asymmetry support values, including proposed OSAI-R/dOSAI values when calculated.
3. Local processing by default
The current build processes capture data on device. OrthoSpine does not include an account system, advertising SDK, third-party analytics SDK, tracking SDK, or remote server upload workflow. Generated files are stored locally in the app container, mainly in Documents/OrthoSpine_Exports, unless the user intentionally exports or shares them using iOS sharing or Files.
4. User-controlled exports
Users can export USDZ, STL, PLY, XYZ and text reports. Once the user exports or shares a file outside the app, the selected destination controls its own privacy and security practices. Users must ensure patient/subject permission and institutional authorization before exporting, sharing, storing, or transmitting any health-related file.
5. Health, minors, and sensitive contexts
Surface scans, posture measurements, body-pose landmarks, reports and mesh exports may be sensitive health-related information. OrthoSpine is not directed to children. Do not scan a minor unless a parent/guardian or legally authorized representative has given permission and the scan is allowed under local law, clinical governance, institutional policy, and research ethics requirements.
6. Retention and deletion
Local files remain on the device until the user deletes them, deletes the app, or removes exported files from Files/iOS storage. Orthopractis does not receive or retain local files unless the user separately sends them to Orthopractis by email or another external channel for support.
7. Tracking and advertising
The app does not use captured data for advertising, marketing, third-party tracking, or data brokerage. Captured data should not be used by users for advertising, profiling, or non-authorized secondary purposes.
8. App Store privacy label note
For App Store Connect, review Apple’s current app privacy definition of “collect,” including that Apple treats data processed only on device and not sent off device as not collected by the developer. If future versions add server upload, accounts, analytics, cloud storage, or support attachments, update the privacy label before submission.
Official reference: https://developer.apple.com/app-store/app-privacy-details/
9. Security
The app relies on iOS sandboxing, local permissions, camera permission prompts, and user-controlled export actions. No system can guarantee absolute security. Users must protect devices, exported files, passwords, backups, and any downstream storage location.
10. Contact and privacy requests
For questions, contact info@orthopractis.com. If the user has sent data to Orthopractis separately, they may request support-file deletion by email.
Hip Dysplasia App Privacy Policy
Last updated: 22 June 2026
This Privacy Policy explains how Orthopractis handles information in connection with the Hip Dysplasia App for Android and ios .
Developer: Orthopractis
Website: https://www.orthopractis.com
App page: https://www.orthopractis.com/hip-dysplasia-app
Support email: info@orthopractis.com
Terms of Use: https://www.orthopractis.com/terms-of-use
1. Purpose of the App
The Hip Dysplasia App is intended to assist trained healthcare professionals, orthopaedic surgeons, clinicians, researchers, or supervised professional users with radiographic hip dysplasia measurement review.
The app allows the user to import or capture an X-ray or medical image, place measurement points, calculate hip dysplasia-related radiographic indexes, review results, and save annotated images or text reports for later review.
The app is not intended for emergency use, self-diagnosis, automated diagnosis, or treatment decisions without qualified professional review.
2. Information Processed by the App
Depending on how the user uses the app, the app may process the following information locally on the user’s device:
- X-ray images, radiographs, or medical photos selected by the user from the photo library, file picker, or camera.
- Points, lines, angles, indexes, measurements, annotations, and calculated values created by the user.
- User-entered or app-generated measurement reports.
- Annotated images and saved report files created by the user.
- Basic app settings required for app functionality.
The app may process patient-related medical images if the user chooses to load or capture such images. Users are responsible for ensuring they have proper permission, consent, and legal authority to process any patient image or medical information.
3. Local Processing
The Hip Dysplasia App is designed to perform its measurement workflow locally on the user’s Android device.
Orthopractis does not require an Orthopractis account for the core measurement workflow.
Orthopractis does not intentionally upload X-rays, photos, measurements, reports, or patient information to an Orthopractis server as part of the core app workflow.
Orthopractis does not sell patient images, medical images, measurement results, or personal data.
Orthopractis does not use selected X-rays or medical images for advertising, tracking, profiling, data mining, or machine learning model training.
4. Camera, Photo Library, and File Access
The app may request access to the camera, photo picker, or file picker only when needed for app functionality.
Camera access is used when the user chooses to capture an image.
Photo library or file picker access is used when the user chooses to load an existing X-ray, radiograph, or image.
The app accesses only the image selected or captured by the user, subject to Android system permissions and user choices.
5. Saved Images, Reports, and Exports
The app may allow the user to save annotated images, measurement results, or text reports on the device.
The user controls whether to save, export, or share any result.
If the user chooses to share a file using Android share options, cloud storage, email, messaging, gallery apps, file managers, or other third-party apps, those third-party services may process the shared file under their own terms and privacy policies.
Orthopractis is not responsible for third-party apps, cloud services, email providers, hospital systems, storage destinations, or recipients selected by the user.
6. Health and Medical Data
X-rays, radiographs, medical photos, measurements, and reports may contain health-related or patient-related information.
Users must handle such information according to applicable laws, professional duties, hospital policies, institutional policies, patient-consent requirements, and confidentiality obligations.
Users should avoid including unnecessary identifying information in images, reports, filenames, or shared exports.
If the user processes images of children or minors, the user is responsible for obtaining appropriate parent, guardian, institutional, or legally authorized consent where required.
7. Data Collection and Sharing
The current app workflow is designed for local device processing.
Orthopractis does not collect or share user-selected X-rays, patient images, measurement results, or reports through the core app workflow.
If a future version adds cloud sync, analytics, crash reporting, accounts, subscriptions, server storage, AI processing, or other online services, this Privacy Policy and the Google Play Data Safety declaration must be updated before release.
8. Support Communications
If a user contacts Orthopractis for support at info@orthopractis.com, the user may voluntarily provide information such as name, email address, device details, screenshots, error descriptions, or example files.
Orthopractis will use support communications only to respond to the request, troubleshoot the app, improve support, and maintain records reasonably necessary for legal, security, or business purposes.
Users should not send patient-identifiable medical images or confidential patient information to Orthopractis unless they have proper authorization and use an appropriate secure method.
9. Data Retention and Deletion
Images, annotations, and reports saved locally by the user remain under the user’s control on the device or in the destination chosen by the user.
Users can delete saved images and reports using the device gallery, file manager, app storage controls, or the destination app where the file was saved.
Uninstalling the app may remove app-local data, depending on Android system behavior and where the user saved exported files.
Support emails and voluntary support materials may be retained as reasonably necessary to respond to support requests, maintain business records, comply with legal obligations, and protect rights and security.
10. Security
Orthopractis designs the app to minimize data transmission by processing the core measurement workflow locally on the device.
Users are responsible for securing their own device, screen lock, backups, cloud sync settings, shared folders, email accounts, hospital systems, and exported files.
No mobile app, device, or storage method can be guaranteed to be completely secure.
11. Children
The app is not directed to children as end users.
The app may be used by qualified professionals to review medical images of children or minors only where appropriate consent, authorization, and professional safeguards are in place.
12. Third-Party Services
The app may rely on Android operating-system features such as camera access, photo picker, file picker, media storage, and system sharing.
Google Play, Android, device manufacturers, gallery apps, cloud apps, email apps, hospital systems, and other third-party services may process information according to their own privacy policies and terms.
13. International Use
Users are responsible for complying with all applicable privacy, medical, professional, data-protection, and patient-confidentiality laws in their country, region, institution, and clinical setting.
14. Medical Disclaimer
The Hip Dysplasia App is not a medical device and does not diagnose, treat, cure, or prevent any medical condition.
The app provides measurement-support tools only. It does not replace professional medical judgment, radiological interpretation, clinical examination, diagnosis, treatment planning, or consultation with a qualified healthcare professional.
All app outputs must be clinically reviewed by a qualified healthcare professional before any medical, diagnostic, surgical, or treatment-related decision is made.
15. Changes to This Privacy Policy
Orthopractis may update this Privacy Policy from time to time to reflect app changes, legal requirements, Google Play requirements, or privacy-practice updates.
The updated Privacy Policy will be posted on this page with a revised “Last updated” date.
16. Contact
For privacy questions, support requests, or data-related inquiries, contact:
Orthopractis
Website: https://www.orthopractis.com
Support email: info@orthopractis.com
App page: https://www.orthopractis.com/hip-dysplasia-app
PlaneAncor Privacy Policy
Support: info@orthopractis.com
App support: https://www.orthopractis.com/PlaneAncor
Privacy: https://www.orthopractis.com/privacy
Terms: https://www.orthopractis.com/termsof use
Effective date: June 21, 2026
Contact: info@orthopractis.com
Support: https://www.orthopractis.com/PlaneAncor
Privacy Policy URL: https://www.orthopractis.com/privacy
Overview
PlaneAncor is an augmented reality and spatial computing application for iPhone, iPad, and Apple Vision Pro. It detects physical planes, creates a Matching Coordinate System, loads user-selected 3D assets, and supports nearby connected sessions for collaborative review.
Information processed on device
PlaneAncor may process the following information locally on the device:
- Camera and world-sensing information used by ARKit/RealityKit to detect floors/walls, track the device, and render AR/spatial content.
- Spatial transforms for the Matching Coordinate System, group origin, loaded assets, measurements, and edit events.
- Imported 3D files selected by the user, including USDZ, USD, USDC, OBJ, STL, and FBX files.
- Local network discovery/session status needed for nearby fallback synchronization.
- Export/share manifests generated by the user.
Information shared with connected participants
When the user intentionally connects devices, PlaneAncor may share selected session data with connected nearby participants:
- Matching Coordinate System transforms.
- Group-origin proposals and group-origin acceptances.
- Loaded asset data or asset-state payloads.
- Asset transform edits, including move, rotate, yaw, pitch, scale, reset, and delete.
- Measurements and distance from 0,0,0.
- Connection/session status.
- Export/share state and manifests.
This sharing is necessary for multiple users to see and edit the same 3D content relative to the same origin. Users should connect only with trusted participants in authorized spaces.
Apple Vision Pro / visionOS
On Apple Vision Pro, PlaneAncor may use spatial/world-tracking and surroundings-related data to place content in immersive space. If the final submitted build uses environment scanning, plane detection, hand tracking, head tracking, or shared world anchors, the App Store privacy answers must accurately describe those practices for the final shipped build.
No advertising tracking
The default PlaneAncor project does not include advertising tracking, third-party analytics tracking, cross-app tracking, or an App Tracking Transparency request. If analytics, accounts, cloud services, or tracking SDKs are added later, this privacy policy and App Store privacy answers must be updated before release.
Storage
Imported 3D files may be copied into the app container to allow reliable loading, export, and transform-manifest generation. Deleting the app removes files stored only in the app container. Files exported to other apps, saved by the user, or shared with connected participants may remain outside PlaneAncor.
User control
Users choose when to scan, when to import files, when to connect devices, when to share/export, and whether to accept a proposed shared origin. Users can delete loaded assets from the active session.
Sensitive environments
Do not scan restricted, confidential, private, or sensitive environments unless you are authorized to do so. Do not share confidential 3D files with participants unless you have permission.
Children
PlaneAncor is intended for professional, educational, and engineering visualization workflows. It is not directed to young children.
Access, deletion, and privacy contact
For privacy questions, access requests, deletion requests, or support requests, contact info@orthopractis.com.
Privacy Policy - OrthoSpine
Last updated: 20 June 2026
Contact: info@orthopractis.com
Privacy URL: https://www.orthopractis.com/privacy
Purpose and scope
OrthoSpine is an iOS-only professional/research support app for posterior spine surface capture, local mesh export, scoliosis-related surface measurement suggestions, and measurement review. It is intended for appropriately trained healthcare professionals, researchers, educators, or supervised operators.
This policy explains how the current build handles camera, ARKit, LiDAR/depth, body-pose, mesh, measurement, report and export data.
Camera, ARKit, LiDAR and body-pose processing
The app uses the device camera, ARKit, LiDAR/depth where available, Vision body-pose detection, and local SceneKit/ModelIO processing to recognize a posterior spine corridor, place left/right rail capture points, build a local posterior surface mesh, and calculate support measurements.
This processing may temporarily involve camera frames, scene depth, environment-scanning information, body-pose landmarks, surface mesh data, measurement rows, reports, and exported USDZ/STL/PLY/XYZ files.
Local processing by default
The current build processes capture data on the device. OrthoSpine does not include an account system, advertising SDK, third-party analytics SDK, tracking SDK, or remote server upload workflow.
Generated files are stored locally in the app container, mainly in Documents/OrthoSpine_Exports, unless the user intentionally exports or shares them using iOS, Files, AirDrop, Mail, Messages, cloud storage or another destination selected by the user.
User-controlled exports and sharing
Users can export USDZ, STL, PLY, XYZ and text reports. Once the user exports or shares a file outside the app, the selected destination controls its own privacy and security practices.
Users must ensure subject/patient permission, professional authorization, institutional approval and secure handling before exporting, sharing, storing or transmitting any health-related file.
What Orthopractis does not collect in the current build
No name, email, account ID, location, contacts, advertising identifier, third-party analytics record, or tracking profile is collected by the current build.
Raw camera video, AR frames, local mesh files and local reports are not automatically transmitted to Orthopractis servers by the current build.
Sensitive health-related context
Surface scans, body-pose landmarks, posture measurements, mesh exports and reports may be sensitive health-related information. Operators must manage them under applicable privacy law, professional duties, institutional policy and research governance.
OrthoSpine is a support tool. It does not provide treatment, prescribe care, replace radiographs, replace clinical examination, or replace qualified professional review.
Minors and supervised use
OrthoSpine is not directed to children. Do not scan a minor unless a parent, guardian or legally authorized representative has given permission and the scan is allowed under local law, clinical governance, institutional policy and research ethics requirements.
Where the app is used in education, training or research, the supervising organization is responsible for appropriate notices, consent/assent procedures, records and access controls.
Retention and deletion
Local files remain on the device until the user deletes them, deletes the app, or removes exported files from Files/iOS storage or another destination chosen by the user.
Orthopractis does not receive or retain local files unless the user separately sends them to Orthopractis by email or another external channel for support. Users may request deletion of voluntarily submitted support materials by contacting support.
Tracking, advertising and secondary use
The app does not use captured data for advertising, marketing, third-party tracking, profiling, data brokerage or training external machine-learning models in the current build.
Users must not use captured health-related files for unauthorized profiling, marketing, advertising, or non-consented secondary purposes.
Security
The app relies on iOS sandboxing, user-granted permissions, local app storage, Apple system frameworks and user-controlled export actions. No system can guarantee absolute security.
Users are responsible for device access control, passwords, backups, secure export destinations, patient/subject consent records, and deletion/retention practices.
Changes and contact
If future versions add accounts, server uploads, analytics, cloud sync, support attachments or third-party SDKs, this policy and App Store privacy answers must be updated before release.
For privacy questions, contact info@orthopractis.com.
FaceCamouflage Privacy Policy
Effective date: June 10, 2026
Last updated: June 12, 2026
Product page:
https://www.orthopractis.com/FaceCamouflage
Privacy page:
https://www.orthopractis.com/privacy
Contact:
info@orthopractis.com
1. Overview
FaceCamouflage is a local field-colour planning, face camouflage guidance, and AR visualization app. The app can take a rear environment photo, import an environment photo chosen by the user from the Photo Library, analyse environment colours, process a live ARKit face mesh on supported iOS devices, display camouflage colour zones on the face mesh, allow manual vertex painting, calculate blend capability, export user-selected files, and optionally mirror the local visualization to the user’s own nearby FaceCamouflage Vision app.
FaceCamouflage is designed as a local-first app. The core workflow does not require an Orthopractis account, Orthopractis cloud processing, third-party analytics, advertising SDKs, third-party AI services, or a server-side face database.
FaceCamouflage uses Apple system frameworks such as Camera, ARKit, RealityKit, Multipeer Connectivity, Local Network, Bluetooth, Photo Library picker, Files, Share Sheet, world sensing on Vision, AR rendering, permission prompts, and App Store platform services only to provide the app features requested by the user.
FaceCamouflage does not use face data, environment photos, imported photos, exported mesh data, or camouflage colour plans for advertising, tracking, third-party profiling, biometric identity verification, or third-party AI training.
2. Data Processed by the App
FaceCamouflage may process the following data when the user chooses to use the related features:
- environment photos captured by the user with the rear camera;
- environment photos selected or imported by the user from the Photo Library;
- live camera frames needed to create an AR preview;
- ARKit face mesh vertices;
- ARKit face mesh triangle indices and triangle topology;
- fixed vertex IDs;
- face-zone data;
- ARFaceAnchor transform and head pose;
- derived landmark positions;
- face-zone measurements;
- symmetry metrics;
- blend metrics;
- camouflage colour assignments attached to vertex IDs or zone IDs;
- calculated terrain palette values;
- RGB and HEX colours;
- Lab colour values;
- colour clusters;
- brightness values;
- shadow values;
- highlight values;
- contrast metrics;
- texture indicators;
- blend-score components;
- paint instructions;
- user-selected slider settings and overlay settings;
- QR or marker coordinate information used for local Apple Vision alignment;
- local pairing packets when the user starts Apple Vision pairing;
- exported files such as TXT, CSV, PLY, USDZ, screenshots, preview images, or other user-created files;
- enterprise license status and local MDM configuration values, if the app is deployed by an organization.
FaceCamouflage does not collect Face ID authentication templates, Secure Enclave biometric data, biometric identifiers used to unlock the device, names linked to face geometry, advertising identifiers for face use, or data intended to identify who the user is.
3. TrueDepth API, ARKit Face Tracking, and Face Data
When the user starts the supported front AR face-mesh workflow and grants Camera permission, FaceCamouflage may use Apple’s TrueDepth / ARKit face-tracking workflow on supported devices.
Using this workflow, FaceCamouflage may temporarily process the following face-related ARKit data:
- ARKit face-geometry vertices;
- triangle indices and triangle topology;
- fixed vertex IDs;
- face-zone data;
- ARFaceAnchor transform and head pose;
- derived landmark positions;
- face-zone measurements;
- symmetry metrics;
- blend metrics;
- camouflage colour assignments attached to vertex IDs or zone IDs;
- live front-camera frames needed by Apple camera and AR frameworks to create the live AR preview.
This face data is processed only to provide FaceCamouflage’s core local visual planning and AR visualization features.
FaceCamouflage does not collect, access, store, or process:
- Face ID authentication templates;
- Secure Enclave biometric data;
- biometric identifiers used to unlock the device;
- faceprints;
- identity profiles;
- names linked to face geometry;
- advertising identifiers for face use;
- data intended to identify who the user is.
FaceCamouflage does not create a faceprint. It does not identify the user. It does not recognize individuals across sessions. It does not authenticate the user with face data.
FaceCamouflage checks device support before using the AR face-mesh workflow. If AR face tracking is not supported on a device, the app does not collect ARKit face mesh data on that device and the face-mesh feature is unavailable or falls back to supported non-face workflows.
4. Camera, Environment Photos, and Photo Library Import
The rear camera may be used to capture an environment reference photo. The rear environment photo is used to sample and calculate field colours for camouflage planning, including background colours, shadows, highlights, brightness, contrast, texture indicators, RGB/HEX colours, Lab values, and colour clusters.
The user may also choose to import an environment reference photo from the Photo Library. Imported photos are processed through the same local colour-analysis and blend-planning workflow as rear-camera environment photos.
Environment photos captured by the camera or imported from the Photo Library may be used to calculate:
- field-colour palettes;
- RGB and HEX colour values;
- Lab colour values;
- colour clusters;
- terrain colour suggestions;
- background colour averages;
- shadow and highlight information;
- brightness and contrast information;
- texture indicators;
- blend-score components;
- paint-zone instructions;
- camouflage colour plans for face-zone visualization.
Environment photos are not used for face recognition, user identification, biometric authentication, advertising, tracking, or third-party profiling.
The front camera / TrueDepth workflow may be used on supported devices to visualize the colour plan on a live ARKit face mesh. FaceCamouflage does not access Face ID authentication templates, Secure Enclave biometric data, or biometric data used to unlock the device.
5. How Face Data Is Used
Face data is used only to provide the app’s core local features, including:
- live AR face visualization;
- displaying the ARKit face mesh on the user’s face;
- fixed vertex-ID display;
- face-zone geometry;
- field-zone geometry;
- mapping environment-derived colours onto face zones;
- environment-colour matching;
- reversible camouflage colour guidance;
- manual vertex painting;
- blend capability calculation;
- RGB / HEX / Lab colour planning;
- local preview of paint-zone instructions;
- user-initiated TXT, CSV, PLY, USDZ, screenshot, or preview export;
- optional local visualization on the user’s own nearby FaceCamouflage Vision app using Multipeer Connectivity.
FaceCamouflage’s purpose is visual planning, education, and spatial AR visualization. The app helps a user study how colours from a photographed or imported environment can be mapped onto a live AR face mesh as an environment-based camouflage colour plan.
FaceCamouflage does not use face data for:
- identity verification;
- biometric authentication;
- Face ID;
- recognizing a person;
- recognizing individuals across sessions;
- advertising;
- tracking;
- third-party profiling;
- employment decisions;
- insurance decisions;
- marketing data mining;
- user behaviour advertising;
- training third-party AI systems;
- building identity profiles;
- building advertising profiles.
6. Local Processing
The main workflow is processed locally on the device. FaceCamouflage does not require a cloud server to calculate the environment palette, face mesh overlay, paint zones, camouflage colour plan, blend score, imported-photo palette, or exported visual plan.
Live face mesh data is processed during the active app session to provide the requested visualization and camouflage planning features. FaceCamouflage does not maintain a server-side face database.
Environment photo analysis, imported Photo Library image analysis, colour extraction, face mesh visualization, paint-zone mapping, and blend-score calculation are processed locally on the user’s device as part of the core workflow.
Orthopractis does not receive the user’s live face mesh data during the normal app workflow.
7. Face Data Sharing and Third Parties
Face data is not sold, not used for advertising or tracking, not sent to Orthopractis servers, and not shared with third-party analytics providers, advertising networks, third-party AI services, data brokers, or marketing platforms.
The core workflow does not require third-party analytics, advertising, cloud processing, or a server-side face database.
Apple system frameworks such as Camera, ARKit, RealityKit, Multipeer Connectivity, Local Network, Bluetooth, world sensing, file sharing, permission prompts, AR rendering, App Store services, and related operating-system services may be used to provide the requested local app features. FaceCamouflage does not use those frameworks to build identity profiles, advertising profiles, or tracking profiles.
Apple system frameworks operate according to Apple’s own terms and privacy policies.
FaceCamouflage does not sell face data, environment photo data, imported photo data, exported mesh data, camouflage colour plans, RGB/HEX plans, or local pairing data.
8. Optional Local Apple Vision Pairing
If the user enables nearby Apple Vision viewing after consent, FaceCamouflage can send a local device-to-device Multipeer packet to the user’s own FaceCamouflage Vision device.
That local packet may include:
- mesh vertices;
- triangle indices;
- selected field metrics;
- vertex states;
- vertex IDs;
- paint-zone colours;
- exact RGB/HEX camouflage colour plans;
- Lab colour values;
- blend metrics;
- overlay settings;
- coordinate alignment data;
- QR or marker coordinate information;
- local status information needed to display the visualization.
This local sharing is used only to display the same visualization on the user’s paired Vision device. It is not uploaded to an Orthopractis cloud server.
Nearby Vision sharing begins only after the user accepts the consent dialog and grants the required permissions. Pairing may be automatic by default when the user’s iOS and Vision devices are nearby and permissions allow it. QR pairing is an optional fallback for coordinate alignment when exact shared marker-space placement is needed.
If pairing is not feasible, the app may display a status message explaining the likely failure, such as Vision not connected, Local Network or Bluetooth permission missing, no live face frame, or QR marker not visible.
Optional Vision pairing is local device-to-device communication between the user’s own nearby devices. FaceCamouflage does not use optional Vision pairing to send face data to Orthopractis servers, analytics providers, advertising networks, third-party AI services, or data brokers.
9. User Exports and Sharing
Exports occur only after the user presses an export or share button.
Exported TXT, CSV, PLY, USDZ, screenshot, preview image, or other user-created files may include the current session’s:
- environment colour palette;
- imported-photo colour palette;
- face mesh vertices;
- triangle indices;
- vertex IDs;
- face-zone colour assignments;
- paint-zone IDs;
- RGB and HEX colour values;
- Lab values;
- blend scores;
- blend metrics;
- paint instructions;
- coordinate alignment data;
- QR or marker coordinate information;
- mesh geometry;
- local status text;
- optional preview information;
- visual face-mesh representations.
The user controls whether to export, what to export, and where exported files are saved or shared.
Exported files remain wherever the user saves, sends, or shares them, such as the device, Files app, Photos app, cloud storage, another app, AirDrop, Mail, Messages, or a contact selected by the user.
Once the user shares a file with another app, service, cloud provider, contact, or recipient, that destination may process the file under its own terms and privacy practices.
10. Storage, Retention, and Deletion
Live face mesh data is retained in memory only during the active app session. It is discarded when the AR session stops, consent is revoked, or the app closes.
FaceCamouflage does not maintain a server-side face database.
Live session data is temporary unless the user intentionally saves, exports, or shares it.
Environment photos captured by the rear camera or imported from the Photo Library are used for the local workflow selected by the user. User-created exports are stored only where the user chooses to save or share them.
Exported TXT, CSV, PLY, USDZ, screenshots, preview images, or other files remain under the user’s control and can be deleted by the user from the location where the user saved or shared them.
Deleting the app removes local app data subject to normal iOS, iPadOS, and visionOS storage behaviour. Files shared to other apps, cloud storage, contacts, Photos, Files, AirDrop recipients, Messages, Mail, or other destinations must be deleted by the user from those locations.
If a user voluntarily emails Orthopractis support and includes an exported file, screenshot, preview image, imported photo, environment photo, or other attachment, Orthopractis will use that message only for support communication. Orthopractis will delete such support materials on request unless retention is required by law or legitimate dispute, accounting, or security needs.
11. Permissions
FaceCamouflage may request the following permissions when needed for user-selected features:
Camera:
Used after consent for rear environment colour capture and supported front ARKit face-geometry visualization.
Local Network and Bluetooth:
Used after consent for local device-to-device iOS-to-Vision pairing.
World Sensing on Vision:
Used after consent for SharedQR marker detection and immersive placement.
Photo Library:
Used only when the user chooses to import an environment photo or save/share user-created images through Apple’s system interfaces.
Files and Share Sheet:
Used only when the user chooses to save, export, or share files.
FaceCamouflage does not use these permissions for advertising tracking, third-party profiling, biometric identity verification, or unrelated data collection.
12. Data Not Used for Tracking
FaceCamouflage does not use the core workflow for advertising tracking, third-party profiling, biometric identity verification, employment decisions, insurance decisions, marketing data mining, or user behaviour advertising.
FaceCamouflage does not sell face data, environment photo data, imported photo data, exported mesh data, RGB/HEX data, or camouflage colour plans.
FaceCamouflage does not use face data to identify a person, verify identity, recognize individuals across sessions, build identity profiles, create advertising profiles, train third-party AI systems, or perform analytics for advertising or tracking.
13. Children and Other People
FaceCamouflage is not directed to children. Children should use the app only with appropriate adult supervision and only with skin-safe removable materials.
Do not scan, display, stream, export, or share another person’s face without that person’s informed permission. The app is not intended for covert face capture, covert face streaming, identity recognition, or biometric identification.
Users are responsible for making sure they have permission to capture, process, stream, export, or share any person, environment, private location, property, or photo included in their camera view, imported photo, exported file, or shared visualization.
14. Safety and Material Responsibility
FaceCamouflage provides visual, technical, and educational information only. It does not provide medical advice, military advice, security advice, legal advice, safety certification, operational guidance, or a guarantee of concealment.
If the user applies real paint, cosmetic material, camouflage material, or any physical product based on colours shown by FaceCamouflage, the user is responsible for selecting safe, lawful, skin-safe, and appropriate materials.
Do not apply unsafe substances to skin. Do not use paints or chemicals that are not intended for skin contact. Follow product instructions and warnings. Stop using any material if irritation or discomfort occurs.
15. Contact and Deletion Requests
For privacy questions or deletion requests related to data you intentionally sent to Orthopractis, contact:
If data was never sent to Orthopractis and remains only on your device or in your own exports, delete it from the device, Files app, Photos app, cloud storage, shared destination, or any other location where you saved or shared it.
If you voluntarily sent Orthopractis an email with exported files, screenshots, preview images, imported photos, environment photos, or other attachments, you may request deletion by contacting:
Orthopractis will delete such support materials on request unless retention is required by law or legitimate dispute, accounting, or security needs.
Product page:
https://www.orthopractis.com/FaceCamouflage
Privacy page:
https://www.orthopractis.com/privacy
16. App Store Review / TrueDepth API Summary
For App Store review and user clarity, FaceCamouflage’s TrueDepth / ARKit face-tracking use can be summarized as follows:
FaceCamouflage uses Apple’s TrueDepth / ARKit face-tracking workflow only when the user starts the supported front AR face-mesh feature and grants Camera permission.
The app may temporarily process ARKit face-geometry vertices, triangle indices, fixed vertex IDs, face-zone data, ARFaceAnchor transform/head pose, derived landmark positions, face-zone measurements, symmetry metrics, blend metrics, camouflage colour assignments attached to vertex IDs or zone IDs, and live front-camera frames needed by Apple camera and AR frameworks to create the live AR preview.
This information is used only for live AR face visualization, displaying the ARKit face mesh, fixed vertex-ID display, face-zone geometry, mapping environment-derived colours onto face zones, reversible camouflage colour guidance, manual vertex painting, blend capability calculation, RGB/HEX/Lab colour planning, local preview of paint-zone instructions, user-initiated export, and optional local visualization on the user’s own nearby FaceCamouflage Vision app.
FaceCamouflage does not collect Face ID authentication templates, Secure Enclave biometric data, biometric identifiers used to unlock the device, faceprints, data intended to identify who the user is, or data used for biometric authentication.
FaceCamouflage does not use face data to identify a person, verify identity, recognize individuals across sessions, build identity profiles, create advertising profiles, train third-party AI systems, or perform analytics for advertising or tracking.
Face data is processed locally on the device during the active app session. Live face mesh data is retained in memory only during the active session and is discarded when the AR session stops, consent is revoked, or the app closes.
Face data is not sold, not used for advertising or tracking, not sent to Orthopractis servers, and not shared with third-party analytics providers, advertising networks, third-party AI services, data brokers, or marketing platforms.
Optional Apple Vision sharing is local device-to-device communication only, between the user’s own nearby iOS/iPadOS device and the user’s own FaceCamouflage Vision device. It is used only to display the same visualization on the paired Vision device and is not uploaded to an Orthopractis cloud server.
Exports are optional and occur only when the user presses an export or share button. Exported files remain wherever the user chooses to save or share them.
17. Changes to This Policy
This Privacy Policy may be updated from time to time. The current policy will be posted at:
https://www.orthopractis.com/privacy
The “Last updated” date will be changed when the policy is revised.
OrthoOsteotomy Privacy Policy
Last updated: 2026-06-05
App: OrthoOsteotomy
Provider: ORTHOPRACTIS.COM SINGLE MEMBER P.C.
Contact: info@orthopractis.com
Privacy Policy URL: https://www.orthopractis.com/privacy
Support URL: https://www.orthopractis.com/orthoosteotomy
Terms of Use: https://www.orthopractis.com/terms-of-use
1. Summary
OrthoOsteotomy is a local-first osteotomy planning-support and educational application for trained healthcare professionals, researchers, educators, and authorized institutional users. The app lets a user select an X-ray image, calibrate the image, place ordered landmarks, display geometric measurements and overlays, review osteotomy planning suggestions, optionally use immersive board visualization, optionally use Muse spatial-stylus input, and optionally export results through user-controlled Apple system sharing.
The current project is designed without advertising SDKs, third-party tracking SDKs, third-party analytics SDKs, user accounts, subscriptions, app-operated cloud sync, or automatic upload of X-ray images or measurement files to Orthopractis.
2. Scope of this policy
This policy explains how OrthoOsteotomy handles information in the app and how support communications are handled if a user voluntarily contacts us. It applies to the OrthoOsteotomy app and the OrthoOsteotomy support, privacy, and terms pages hosted by Orthopractis.
This policy does not replace the privacy policies of Apple, an institution, a hospital, a picture archiving system, an email provider, or any third-party service chosen by the user when exporting, saving, emailing, or otherwise sharing files.
3. Information processed locally by the app
Depending on how the user operates the app, OrthoOsteotomy may process the following information locally on the user's device:
-
A user-selected X-ray image or training image.
-
Calibration points C1/R2 and the entered calibration value.
-
Ordered anatomical landmarks P1-P9, hinge point H, and wedge/base point D.
-
Derived geometric outputs such as MAD, mLDFA, JLCA, mMPTA, HKA, MJL, Fujisawa target percentage, alpha, beta, delta, omega, DD', and delta DD'.
-
Display overlays, construction lines, angle arcs, labels, and help-window state.
-
Optional local export files in JSON, CSV, image, or other app-supported formats.
-
Optional spatial placement data used to position the immersive board or panel.
-
Optional Muse spatial-stylus aim, projected pointer, button state, and haptic-event state.
-
Local settings such as panel size, distance, height, sliders, selected workflow mode, and help preferences.
This information is processed to provide the app's user-facing functions. The app does not need an Orthopractis account to perform the local workflow.
4. Patient and clinical information warning
X-ray images and exported measurement files may contain protected health information or other sensitive clinical information if the user imports or exports such material. Users are responsible for using only images and files they are authorized to use and for following institutional policy, patient consent requirements, professional obligations, and applicable privacy law.
Users should remove or obscure patient identifiers whenever possible for training, support, demonstrations, and App Review materials.
5. Information collected by Orthopractis through the app
For the current local-first build described by this policy, Orthopractis does not collect app images, measurement coordinates, measurement outputs, identifiers, advertising data, tracking data, analytics data, account data, or location data from the core app workflow.
If future versions add analytics, crash reporting, cloud sync, accounts, subscriptions, telemetry, collaboration, or any third-party SDK that collects data, this policy and the App Store privacy answers must be updated before release.
6. User-controlled export and sharing
When the user chooses to export or share data, the app may use Apple system components such as Files, Share Sheet, Photos, Mail, Messages, AirDrop, or another destination selected by the user. The user controls the destination and is responsible for ensuring that export is authorized.
After export, the receiving app, service, file location, institution, email provider, cloud provider, or recipient is responsible for its own handling of the file according to its own terms and privacy policy.
7. Support communications
If a user contacts info@orthopractis.com, the email address, message, attachments, screenshots, logs, and any other information voluntarily provided will be received by Orthopractis for support, troubleshooting, safety review, privacy response, or product-improvement follow-up.
Users should not send protected health information, patient-identifiable X-rays, patient names, dates of birth, hospital IDs, or other identifiers to support unless they are authorized to do so by their institution, patient consent, and applicable law. For support screenshots, use training images or de-identified images whenever possible.
8. Legal bases and purposes where applicable
Where privacy law requires a legal basis, processing is limited to purposes such as:
-
Providing the local app functionality requested by the user.
-
Responding to voluntary support communications.
-
Maintaining security and troubleshooting.
-
Complying with legal obligations.
-
Improving documentation and reliability using de-identified or non-patient support information where permitted.
9. Tracking, advertising, and analytics
The current build does not track users across apps or websites, does not include advertising, does not use the IDFA, and does not include third-party analytics SDKs.
10. Third-party services and Apple platform services
The app may use Apple platform features selected or authorized by the user, such as PhotosPicker or file import, Share Sheet, Files, and device permission prompts. Apple platform features are governed by Apple's operating-system behavior and the user's device settings.
The current project does not integrate a third-party analytics service, advertising network, third-party tracking network, or Orthopractis-operated cloud backend.
11. Retention
Core app data remains on the user's device, in the current session, or in files saved or exported by the user. The app does not automatically upload these materials to Orthopractis.
Support emails and voluntary attachments may be retained as needed to respond to the request, troubleshoot the issue, protect legal rights, satisfy legal obligations, and maintain support history. Users may request deletion of voluntarily sent support material by contacting info@orthopractis.com, subject to legal, regulatory, safety, or dispute-retention obligations.
12. Deletion and access requests
Users can delete local app files and exported files from their own device or storage destination. For deletion or access requests concerning materials voluntarily sent to Orthopractis support, contact info@orthopractis.com and describe the request with enough detail to identify the material.
13. Security
Users should protect their devices, app exports, and clinical images according to institutional security policy. Orthopractis uses reasonable administrative and technical safeguards for support communications, but no email or network transmission can be guaranteed to be completely secure.
14. Children
OrthoOsteotomy is intended for trained healthcare professionals, researchers, educators, and authorized institutional users. It is not directed to children.
15. International use
Users are responsible for ensuring that their use of the app, imported images, exported files, and support communications complies with applicable laws and institutional requirements in their jurisdiction.
16. Changes to this policy
This policy may be updated to reflect changes in the app, laws, Apple requirements, or support practices. The updated policy will be posted at https://www.orthopractis.com/privacy with a revised date.
17. All information received from the software output must be clinically reviewed regarding its plausibility before patient
treatment. The app is indicated for assisting healthcare professionals. Clinical judgment and experience are required to
properly use the software. These instructions alone do not replace in-depth training in planning for osteotomies. It only
serves as a general guideline. Any influence on operator decision-making remains the surgeon's own responsibility and
experience. A surgeon must always rely on professional clinical judgement when deciding whether to use a particular
technique for a particular patient. The app does not dispense medical advice. The software is not for primary image
interpretation.
Contact
Privacy questions, deletion requests for voluntarily sent support materials, and support requests may be sent to:
Support URL: https://www.orthopractis.com/orthoosteotomy
.
CamouflageMesh Privacy Policy
Effective date: 7 June 2026
Developer: Orthopractis.com Single Member P.C. / Orthopractis
Support email: info@orthopractis.com
Support page: https://www.orthopractis.com/camouflagemesh
Privacy page: https://www.orthopractis.com/privacy
Terms page: https://www.orthopractis.com/terms-of-use
1. Introduction
This Privacy Policy explains how CamouflageMesh and CamouflageMesh Vision handle information when you use the app on iPhone, iPad, or Apple Vision Pro. The policy covers surface capture, AR and spatial workflows, camera or photo palette sampling, mesh processing, colour analysis, preview, export, nearby transfer, support contact, and related Orthopractis support pages.
CamouflageMesh is designed as a local-first surface mesh and colour-planning app. It helps you capture or import a physical-scale surface, sample colours from the surrounding environment, build a camouflaged vertex-colour mesh, inspect the colour table, preview the result, and export files that you choose to save or share.
2. Provider and contact
The app is provided by Orthopractis.com Single Member P.C. / Orthopractis. Public contact details are available through the Orthopractis website. For privacy questions, support requests, or policy questions, contact info@orthopractis.com. The intended support page is https://www.orthopractis.com/camouflagemesh. The intended privacy page is https://www.orthopractis.com/privacy.
3. Summary of the current privacy position
Based on the current local-first implementation package, CamouflageMesh does not require a user account, does not include advertising, does not use tracking for advertising, does not declare a developer-operated analytics endpoint, and does not upload core mesh, photo, AR, colour, or export data to an Orthopractis cloud service as part of the normal packaged workflow. Core processing is designed to take place locally on the device.
Data can still leave your device if you choose to save, export, share, AirDrop, email, send files to a paired or nearby device, place files in cloud storage through the operating-system share sheet, or contact support outside the app. Those actions are controlled by you and may involve Apple services, email providers, cloud storage providers, messaging apps, nearby devices, or other third-party destinations that are not operated by Orthopractis.
4. Information processed locally by the app
Depending on the features you use, CamouflageMesh may process AR frames, world-sensing information, scene reconstruction data, surface mesh vertices, triangle indices, vertex colours, normals, classifications, imported 3D files, selected or captured photos, environment colour samples, colour palette statistics, colour comparisons, generated camouflage roles, colour tables, paint instructions, USDZ or mesh resources, manifests, ZIP files, local session state, and export files.
This information is used to provide the features you request. Surface mesh data is used to build and preview physical-scale geometry. Photos or enterprise camera frames, when available and authorised, are used to derive environment colours. Colour analysis is used to create swatches and match surface colours to the environment. Export data is used to produce the files you choose to save or share.
5. Camera, AR, photo, local network, and enterprise permissions
CamouflageMesh may ask for camera permission when you choose a feature that needs camera capture, such as surface capture or environment photo capture. It may ask for AR, world-sensing, plane detection, or scene reconstruction access when you choose to build or review a physical-scale surface mesh. It may ask for photo library access when you choose an existing image or choose to save generated output. It may ask for local network, peer discovery, or Bonjour-related access when you start a nearby sharing or paired-device workflow.
CamouflageMesh Vision may include an enterprise main-camera workflow for Apple Vision Pro only when the required enterprise licence, provisioning, signed entitlement, supported device configuration, and active app state are present. If those conditions are not present, the app uses fallback workflows such as selected photos, imported files, or existing mesh colours. Enterprise camera frames, when used, are intended to be processed locally for palette sampling and are not uploaded by the app as part of the described workflow.
6. Photos, meshes, spatial data, and sensitive places
Surface meshes, photos, world-sensing data, and exported files can reveal sensitive information. They may show private rooms, bystanders, confidential objects, screens, documents, restricted areas, prototypes, worksites, addresses, or other details that you or another person may not want to share. You are responsible for scanning and exporting only surfaces, spaces, objects, and files that you are authorised to capture, process, store, and share.
Before exporting or sharing, inspect the files and previews. A mesh export may contain geometry even if a photograph looks harmless. A colour table may reveal the palette of a private or restricted space. A ZIP package may include manifests or metadata that describe source files, scale, names, settings, or workflow choices.
7. Exports and user-controlled sharing
When you create an export package, the app may generate files such as a camouflaged mesh, USDZ files where supported, colour table CSV, colour table HTML, colour table JSON, text summaries, paint shopping or instruction lists, palette summaries, manifests, and ZIP archives. These files remain local unless you choose to save or share them through available system tools.
If you use Share, AirDrop, Files, Photos, Messages, Mail, cloud storage, or another destination, the chosen destination may process the file under its own privacy policy and terms. Orthopractis does not control third-party apps, operating-system sharing destinations, cloud folders, email services, or receiving devices selected by you.
8. Nearby device transfer and paired-device workflows
The app package describes optional nearby sharing, QR sync, local peer transport, and paired-device workflows. These features are intended for user-initiated transfer between nearby devices. Transfer availability, reliability, and privacy can depend on device configuration, local network, Bluetooth, Wi-Fi, operating-system state, and the destination device. Use these features only with devices and users you trust.
9. Support requests and voluntary contact
The app does not require an account for the packaged workflow. If you contact Orthopractis by email or through a website form, you may voluntarily provide your name, email address, device model, operating-system version, app build number, screenshots, exported files, logs, or other support details. Orthopractis may use that information to respond to your request, troubleshoot the issue, maintain records of the support interaction, and improve documentation or app quality.
Do not send private photos, confidential meshes, restricted worksite files, patient information, personal data, or third-party content to support unless you have permission and the information is necessary for the request. If you send files to support, you may ask Orthopractis to delete them when they are no longer needed, subject to legal, security, and record-keeping needs.
10. Tracking, advertising, analytics, and third-party SDKs
The current package states that the normal app workflow does not include advertising, tracking, Orthopractis analytics, cloud upload, or an account requirement. The app should not track users across apps or websites, should not use an advertising identifier, and should not profile users for advertising purposes.
If a future version adds analytics, crash reporting, accounts, cloud upload, subscriptions, server-side support upload, advertising, tracking, or third-party SDKs that collect data, Orthopractis must update this Privacy Policy, the App Store privacy answers, and any required privacy manifests before release.
11. Apple and third-party services
The app runs on Apple platforms and may use Apple frameworks, operating-system permission prompts, local file storage, system share sheets, AirDrop, Files, Photos, Mail, and App Store distribution. Apple and any third-party destination selected by you may process information under their own policies. Orthopractis is not responsible for data handling by Apple, email providers, cloud providers, messaging apps, local network devices, or other services you choose outside the app.
12. Children
CamouflageMesh is not directed to children. The app is intended for users who can understand the permission, privacy, export, and responsible-use requirements. Use in schools, training environments, research demonstrations, or supervised settings should follow all applicable consent, safety, and privacy requirements.
13. Retention and deletion
Core scans, photos, meshes, colour tables, exports, and local session files are stored locally only when the app or operating system saves them as part of your workflow. You can delete local files through the app, the Files app, device storage management, the destination app, or by deleting the app. Deleting the app generally removes the app container from the device, subject to normal operating-system backups and destination services selected by you.
Orthopractis does not receive or retain core app content in the current local-first workflow unless you intentionally send it to support or another Orthopractis contact channel. Support emails and website messages may be retained as long as reasonably needed to respond, maintain records, protect legal rights, prevent misuse, or comply with obligations. You may request deletion of support communications by contacting info@orthopractis.com.
14. Security
CamouflageMesh relies on Apple platform sandboxing, operating-system permissions, local processing, and user-controlled export workflows. No software, local storage method, network transfer, or sharing destination can be guaranteed to be perfectly secure. Avoid scanning, storing, or exporting sensitive materials unless you trust the device, destination, network, and receiving user.
15. International users
If you contact Orthopractis by email or through the support website, your support information may be processed in the country where Orthopractis, its email provider, website provider, or support tools operate. Use the support channels only if you agree to that handling. Local app processing on your device does not require an Orthopractis account or cloud upload in the current build.
16. Your choices and rights
You control whether to grant camera, photo, world-sensing, local network, enterprise camera, and other system permissions. You can change permissions in device Settings. You control whether to save, export, share, AirDrop, email, or transfer files. You may request access, correction, or deletion of support information you have sent to Orthopractis by contacting info@orthopractis.com. Some requests may be limited by legal, security, or record-keeping requirements.
17. Changes to this Privacy Policy
Orthopractis may update this Privacy Policy when the app, platform requirements, data practices, support process, or legal requirements change. The updated policy should be posted at https://www.orthopractis.com/privacy or another stable Orthopractis URL. The app should also update in-app consent text when the policy materially changes.
18. Contact
Privacy and support questions can be sent to info@orthopractis.com. Support page: https://www.orthopractis.com/camouflagemesh. Privacy page: https://www.orthopractis.com/privacy. Terms page: https://www.orthopractis.com/terms-of-use.
Privacy Policy
Last updated: [25/5/2026
VisionMeshCapture is a visionOS app for Apple Vision Pro. It allows users to capture selected reconstructed environment mesh, optionally use approved enterprise main-camera access for local color sampling, load 3D models, align point clouds, and export mesh packages.
Data processed by the app
Depending on how the user operates the app, VisionMeshCapture may process the following data locally on the device:
world-sensing and scene-reconstruction geometry;
selected mesh vertices, faces, normals, classifications, and point-cloud data;
optional enterprise main-camera frames for local color sampling when approved access is available;
imported 3D files such as USDZ, USD, PLY, GLB, GLTF, FBX, OBJ, MTL, and textures;
vertex colors, texture/material summaries, and color analytics;
captured and imported model transforms;
export files including PLY, USDZ, CSV, JSON, and ZIP packages;
local session logs shown in the app UI.
Local processing
VisionMeshCapture is designed to process core capture, color, alignment, and export data locally on device. The app does not require sign-in, an account, or server upload for core functionality.
Generated files remain in the app container unless the user explicitly saves or shares them.
User-controlled export and sharing
When the user prepares an export package, the app may create files such as:
captured_environment.ply;
captured_environment.usdz;
imported USDZ files;
captured_vertices.csv;
captured_faces.csv;
pick/color analytics CSV;
import summaries;
manifest.json;
a ZIP export package.
The user controls whether these files are saved or shared.
Enterprise main-camera access
If approved enterprise main-camera access is available, VisionMeshCapture may use camera frames locally to improve color sampling of selected mesh surfaces. Camera frames are processed locally for the capture/color workflow and are not uploaded by the app.
If enterprise access is unavailable, the app uses a fallback mesh/classification capture path.
No tracking
VisionMeshCapture does not track users across apps or websites.
No advertising
VisionMeshCapture does not include advertising.
No account requirement
VisionMeshCapture does not require a user account or sign-in.
Third-party services
The current app build should not include analytics, advertising, or cloud-upload SDKs. If any third-party services are added later, this Privacy Policy and App Store privacy answers must be updated before distribution.
Sensitive spaces and user responsibility
Spatial mesh data, camera-derived color samples, imported files, and exported packages can reveal private rooms, objects, screens, documents, bystanders, or restricted locations. Users should capture and share only spaces they are authorized to scan and should inspect export files before sharing.
Children
VisionMeshCapture is not designed to knowingly collect personal information from children. Use in schools, training environments, or supervised settings should follow applicable consent and privacy requirements.
Contact
For privacy questions, contact:
info@orthopractis.com
PRIVACY POLICY for
Last updated: June 2, 2026
OrthoFaceCosmetic App and companion OrthoFaceCosmeticVision App
This section explains how OrthoFaceCosmetic handles face data, AR face geometry, face-mesh measurements, cosmetic colour-guidance overlays, Apple Vision Pro local streaming, user exports, sharing, storage, retention, and deletion.
Website:
www.orthopractis.com
Privacy Policy:
www.orthopractis.com/privacy
Terms of Use:
www.orthopractis.com/terms-of-use
Contact:
info@orthopractis.com
1. FACE DATA AND AR FACE GEOMETRY
OrthoFaceCosmetic uses the device camera and Apple ARKit face-tracking features, when supported by the device, to create a live AR face mesh for educational visualization, facial proportion review, and reversible cosmetic colour-guidance overlays.
For the purposes of this Privacy Policy, “face data” may include the following information when the user starts live AR capture or uses related features:
- AR face mesh geometry produced during the active AR session.
- Mesh vertices.
- Triangle indices.
- Fixed vertex ID references.
- Derived facial landmark positions.
- Derived facial zone classifications.
- Symmetry measurements.
- Facial proportion measurements.
- φ / golden-ratio reference measurements.
- Inverse φ, φ², and φ³ relationship values.
- Cosmetic AutoCorrect plan data.
- Cosmetic colour patch definitions.
- Selected facial review surfaces.
- Patch vertex IDs.
- Overlay opacity and intensity settings.
- Retained, hidden, or rejected cosmetic suggestion states.
- Manual vertex-paint selections entered or selected by the user.
- Optional correction TXT, image, 3D, or report files if the user intentionally exports or shares them.
- Optional local Apple Vision Pro stream packets if the user intentionally starts local Apple Vision Pro pairing and streaming.
OrthoFaceCosmetic does not collect or access Apple Face ID authentication templates, Secure Enclave biometric data, passcode data, or any biometric information used to unlock the device.
OrthoFaceCosmetic does not use face data for identity verification, user identification, biometric authentication, advertising, tracking, third-party profiling, employment decisions, insurance decisions, credit decisions, law-enforcement identification, or any automated decision about a person’s rights or eligibility.
The app’s face-related features are designed for educational visualization, facial proportion review, reversible cosmetic planning, AR teaching, and local user-controlled review only.
Live camera frames are used for AR tracking and visualization. OrthoFaceCosmetic does not save raw camera video or raw face photos by default.
2. HOW WE USE FACE DATA
OrthoFaceCosmetic uses face data only to provide the app’s core educational and visualization features.
The planned uses of face data are:
- To create and display a live AR face mesh.
- To map repeatable mesh vertex IDs to facial surfaces.
- To show optional white vertex ID labels on the live AR face mesh.
- To compute symmetry and proportion-review values.
- To compute φ / golden-ratio reference relationships.
- To compute inverse φ, φ², and φ³ reference relationships.
- To identify facial review zones for educational analysis.
- To generate reversible cosmetic colour-guidance overlays.
- To display transparent colour patches on selected facial review surfaces.
- To display arrows pointing to selected review surfaces.
- To explain why a surface was selected.
- To explain what visual effect a cosmetic colour role may create.
- To suggest generic cosmetic product categories.
- To support manual vertex paint when the user enters or selects mesh vertex IDs.
- To let the user retain, hide, reject, or restore cosmetic suggestions.
- To let the user export or share a correction TXT or other report file if they choose.
- To optionally display the same local visualization on the user’s paired Apple Vision Pro device.
The cosmetic colour map is educational and reversible. It does not physically change the face and does not diagnose a condition.
The app uses the following map colours:
Gold = highlight / visual advance.
Blue = matte contour / visual recession.
Rose = blush / lift / soft transition.
Warm red = lip warmth / definition.
Mint = neutral review / keep natural.
Violet = soft matte shadow / anti-shine / lower-value recession.
Cyan = manual technical vertex-ID selection.
These colours are map colours only. They do not mean that the user should paint literal gold, blue, mint, violet, or cyan makeup on the face.
The app may suggest generic cosmetic product categories such as:
- lighter concealer;
- soft highlighter;
- satin cream highlight;
- illuminating balm;
- matte contour;
- neutral deeper shade;
- contour powder;
- contour stick;
- cream blush;
- powder blush;
- lip tint;
- lip liner;
- lipstick;
- lip stain;
- tinted balm;
- gloss;
- skin tint;
- light foundation;
- setting powder;
- anti-shine powder;
- soft contour powder.
OrthoFaceCosmetic does not recommend cosmetic brands or companies.
OrthoFaceCosmetic does not tell users that their face is defective, ugly, wrong, bad, or must be fixed. The app uses non-judgmental language such as:
- review surface;
- visual weight;
- reversible preview;
- cosmetic suggestion;
- optional correction;
- keep natural;
- retain;
- hide;
- reject.
The app is not a medical device, diagnosis tool, orthodontic treatment planner, surgical planning tool, aesthetic-medical prescription system, beauty score, attractiveness score, identity-verification system, or emergency tool.
3. FACE DATA SHARING AND APPLE VISION PRO LOCAL STREAMING
OrthoFaceCosmetic does not share face data with third parties as part of the core app workflow.
By default, face mesh data, vertex IDs, measurements, cosmetic plans, and colour maps are processed locally on the user’s device.
OrthoFaceCosmetic does not upload live face mesh data, vertex IDs, measurement values, cosmetic colour maps, or AR face geometry to an external server as part of the core workflow.
OrthoFaceCosmetic does not use third-party advertising, third-party face profiling, third-party biometric processing, or third-party tracking for face data.
The app may optionally support local Apple Vision Pro pairing. This feature is user-initiated and is intended only to display the same educational visualization on the user’s paired Apple Vision Pro device.
If the user starts Apple Vision Pro streaming, the iOS or iPadOS device may send a local device-to-device packet to the paired Apple Vision Pro viewer. This local packet may include:
- timestamp;
- mesh vertices;
- triangle indices;
- selected vertex states;
- selected measurements;
- cosmetic colour-plan data;
- patch vertex IDs;
- overlay opacity;
- colour intensity;
- arrow visibility state;
- focused patch ID;
- retained patch state;
- hidden or rejected patch state;
- QR marker coordinate-alignment information when pairing is active.
This Apple Vision Pro stream is:
- local;
- user-initiated;
- device-to-device;
- intended only for the user’s paired Apple Vision Pro visualization;
- not a cloud upload;
- not advertising tracking;
- not third-party profiling;
- not biometric authentication;
- not identity verification.
The app may use a SharedQR marker to help the iOS device and Apple Vision Pro viewer share a coordinate reference. The SharedQR marker is used only for spatial alignment between the two local devices.
If Apple Vision Pro pairing is not started by the user, the local Vision stream is not started.
If Apple Vision Pro pairing is stopped, the local stream stops.
If the user exports or shares a correction TXT, image, 3D file, report, or other file, that file is shared only according to the user’s explicit action through the operating system’s share/export interface.
Users should not scan, stream, export, or share another person’s face without that person’s informed permission.
4. STORAGE, RETENTION, AND DELETION
Live face mesh data is session-only by default.
Live AR face mesh data, vertex data, measurement states, and cosmetic patch states are retained in memory only while the AR session is active and while the app needs them for live visualization.
When the AR session is stopped, the app is closed, or the user leaves the live capture workflow, live face mesh data is discarded from the active session.
OrthoFaceCosmetic does not maintain a server-side face database.
OrthoFaceCosmetic does not retain face data on an external backend as part of the core workflow.
OrthoFaceCosmetic does not store Apple Face ID templates, Secure Enclave biometric data, or device-unlock biometric data.
Optional Apple Vision Pro stream data is transient and is used only during the active local paired session.
Optional user-generated files may persist only if the user intentionally saves, exports, or shares them. These files may include correction TXT files, reports, images, 3D visualization files, or other educational exports.
If the user exports or shares a file, the exported file remains only where the user saves or shares it. The user controls that destination and may delete the file from the device, storage location, or recipient destination they selected.
If a user contacts us for support and voluntarily sends screenshots, files, exported reports, or other materials, we use those materials only to provide support, troubleshoot issues, or respond to the user’s request. Support materials are not used for advertising or biometric identification.
Users may request deletion of any support material they have voluntarily sent to us by contacting:
Because the app’s core face-mesh processing is local and session-based, there may be no server-stored face data for us to delete unless the user has voluntarily sent us support material or uploaded/sent files outside the core local workflow.
5. USER EXPORTS AND SHARING
OrthoFaceCosmetic may allow the user to export or share educational files.
These may include:
- correction TXT files;
- measurement reports;
- cosmetic colour-plan summaries;
- selected vertex ID lists;
- screenshots or images if the user chooses to create/share them;
- 3D review or visualization files if the user activates export features;
- technical appendix or teaching documents.
Exports are user-initiated.
The app does not automatically export face data.
Exported correction files may include derived face-related information, such as:
- selected review surface names;
- colour roles;
- cosmetic product categories;
- application instructions;
- blend directions;
- expected visual effects;
- what to avoid;
- vertex IDs;
- measurements;
- opacity or intensity settings;
- retained or hidden suggestion states.
The purpose of these exports is educational review, cosmetic communication, technical documentation, or user-controlled sharing.
Users should review exported files before sharing them.
Users should not export or share another person’s face, face measurements, vertex IDs, screenshots, or cosmetic correction plans without that person’s informed permission.
When the user shares an exported file, the file becomes subject to the privacy practices of the destination selected by the user, such as email, messages, cloud storage, AirDrop, or another app.
6. CONTACT
For privacy questions, support requests, data questions, or deletion requests concerning any support material voluntarily sent to us, contact:
Website:
Privacy Policy:
Terms of Use:
www.orthopractis.com/terms-of-use
If you have questions about how OrthoFaceCosmetic uses face data, AR face geometry, Apple Vision Pro local streaming, exports, or retention, please contact us before using those features.
Users may choose not to start live AR capture, not to show vertex IDs, not to start Apple Vision Pro streaming, not to export files, and not to share any correction report.
Use OrthoFaceCosmetic only for educational visualization, reversible cosmetic review, and user-controlled communication. The app is not a medical device, not a diagnosis, not a treatment plan, not an identity-verification tool, not a beauty score, and not a surgical instruction system.
Orthoface Privacy Policy
Effective date: 2026-05-16
Orthoface is an educational facial measurement and visualization app. It uses camera/ARKit/depth data to generate local 3D face mesh measurements, symmetry indicators, Marquardt-style overlay visualization, Golden Dodeca fit, φ-ratio calculations, 2D unwraps, perfect/corrected USDZ previews, and optional export ZIP files.
Orthoface is not a medical device. It does not diagnose, treat, prescribe, or recommend surgery. Beauty and φ scores are mathematical indicators only and include disclaimers.
Orthoface Data, TrueDepth, and ARKit Face Mesh
Orthoface uses the device camera, TrueDepth camera where available, ARKit face tracking, and depth/mesh information to generate a local 3D surface model of the face. This face model may include numbered mesh vertices, face pose information, reference planes, symmetry-pair measurements, distance values, ratio values, mask overlays, 2D unwrap diagrams, and exportable measurement summaries.
Orthoface does not use TrueDepth or ARKit face data to identify, authenticate, verify, or recognize a person. Orthoface does not access or store Face ID biometric templates. Orthoface does not use face data for advertising, tracking, profiling, or marketing.
How Orthoface Uses Face Data
Orthoface uses face mesh and depth information only for educational facial measurement and visualization. The app may use this data to display a live face mesh, vertex IDs, anatomical labels, reference planes, symmetry indicators, Marquardt-style masks, Blue Guide overlays, Golden Dodeca fitting, phi-ratio lines, curve/spline masks, 2D unwrap diagrams, corrected USDZ previews, and local export files.
Orthoface does not diagnose, treat, prescribe, screen for disease, or recommend surgery.Face mesh data is processed locally on device. It is not automatically transmitted to a developer server. The only off-device transfer is user-controlled local-network transfer to the user’s paired Apple Vision Pro after QR pairing, and user-initiated export/share files.
Local Processing and Storage
By default, face mesh data and measurements are processed locally on the device. The developer does not automatically receive, upload, sell, or share face mesh data. Face data used during a live session is processed in memory. Local export files are stored only in the app sandbox or user-selected destination when the user chooses export/share.
Sharing, Export, and Apple Vision Pro Pairing
If the user pairs an iPhone/iPad with Apple Vision Pro, compact measurement packets may be transmitted over the local network between the user’s own paired devices after QR pairing for immersive visualization. This local device-to-device communication is used only to display the selected overlays in Apple Vision Pro.
If the user chooses export or share, Orthoface may create local files such as TXT, JSON, PLY, STL, OBJ, USDZ, SVG, PNG, or ZIP packages. These files may contain facial geometry, vertex IDs, measurement values, and visualization data. Export and sharing occur only when the user intentionally selects an export/share action. The user controls where exported files are saved or sent.
No Third-Party AI, Advertising, or Tracking
Orthoface does not transmit face data to developer-operated cloud storage by default. Orthoface does not include external AI consultation, ChatGPT, OpenAI, GPT, advertising, or third-party tracking functionality. Orthoface does not sell face data and does not use face data for advertising or tracking.
Retention and Deletion
Live face data is processed during the active session. Export files are retained only where the user saves or shares them. Users may delete exported files from their device or chosen storage location. The developer does not retain server-side face data by default because the app does not automatically upload face data to a developer server.
Educational and Non-Medical Disclaimer
Orthoface is an educational facial measurement and visualization app. It is not a medical device. It does not diagnose, treat, prescribe, screen for disease, or recommend surgery. Measurements, symmetry indicators, mask overlays, phi-ratio guides, and the Overall Concordance Score are mathematical visualization indicators only and should not be used as the sole basis for medical, surgical, aesthetic, or personal decisions.
Face Data We Process
OrthofaceCapture uses ARKit and the TrueDepth camera only after user consent to create a live face mesh for local educational measurement and visualization. The app may process ARKit face-geometry vertices, triangle topology, face transforms, QR alignment transforms, fixed anatomical vertex IDs, symmetry/asymmetry values, calculated measurements, overlays, masks, and export files that the user chooses to create. OrthofaceCapture does not record raw camera video for developer collection, does not identify the user, and does not collect Face ID authentication or biometric identity data.
How Face Data Is Used
Face data is used only to provide local live mesh display, measurement calculations, QR alignment, visualization overlays, optional encrypted local-network streaming to the user's own paired Apple Vision Pro, and optional user-initiated export/share files. OrthofaceCapture does not use face data for advertising, tracking, profiling, user identification, or third-party AI processing.
No Third-Party AI Service or Developer Collection
OrthofaceCapture does not send face data to developer servers, cloud processing services, analytics SDKs, advertising SDKs, tracking SDKs, or any third-party AI service. Face data remains on the user's device unless the user explicitly streams it to the user's own paired Apple Vision Pro over encrypted local Multipeer Connectivity or chooses a system export/share action.
Storage and Retention
Live face data is processed in memory during the app session. The developer does not receive or retain face data. User-created exports, screenshots, share packages, or saved files remain on the user's device, in the app temporary directory, Photos, Files, AirDrop destination, or another user-selected destination until the user, destination app, or operating system deletes them.
User-Initiated Export and Sharing
Export and sharing are optional and are started only by the user. The user is responsible for choosing the destination and should share face mesh, image, or measurement files only with consent from the subject.
Data processed locally
The app may process camera frames, ARKit face geometry, depth/mesh data, fixed anatomical vertex IDs, PCA planes, measurements, symmetry scores, ratio results, Marquardt/Golden Dodeca overlays, 2D unwrap previews, and export files. Processing is local by default.
Local network streaming
If the user pairs iPhone with Apple Vision Pro, Orthoface may stream face-mesh measurement packets over the local network for immersive visualization. This is controlled by the user and is intended for the user's own devices.
Exports
When the user presses export/share ZIP, Orthoface creates user-controlled files such as TXT, JSON, PLY, USDZ, USDA, OBJ, STL, SVG, PNG, 2D unwrap images, QR marker, and README. Exported face geometry and measurements can be sensitive. Share only with trusted recipients.
Local measurement workflow
Orthoface does not include an external relay. Measurement and visualization features are local by default unless the user chooses local-network streaming or export/share.
Product improvement
Do not collect product-improvement, analytics, or exported geometry from users unless you add a separate opt-in consent and update this policy before collection.
Orthoface processes camera, ARKit, depth, and local 3D mesh data to generate measurements and visual overlays. Data is processed locally by default. Users may export ZIP reports manually.
Orthoface is not a medical device and does not diagnose, treat, prescribe, or recommend surgery.
Contact and deletion requests
Contact: info@orthopractis.com.
PlaceMesh Privacy Policy
Effective date: May 26, 2026
PlaceMesh and PlaceMesh Viewer are local spatial capture, visualization, USDZ review, mesh export, and Apple Vision Pro companion applications published by Orthopractis. This Privacy Policy explains what the apps process, what the developer does not collect in this build, and how users control sharing.
1. Short privacy summary
PlaceMesh processes camera-backed AR data, spatial tracking data, QR marker observations, point clouds, mesh vertices, vertex colors, local measurements, USDZ assets, and export files on the user's device to provide capture, visualization, alignment, measurement, local peer sharing, and export features. In the current build, the apps do not require a user account, login, advertising identifier, analytics SDK, cloud project, or developer-operated backend.
2. Data processed by the apps
Depending on which features the user chooses, the apps may process the following on device:
-
Camera and AR tracking data for surface capture, raycasting, QR marker recognition, USDZ placement, and visual alignment.
-
visionOS world-sensing data for QR marker alignment, scene reconstruction, and bounded Vision Capture inside immersive space.
-
Vision body-pose/skeleton observations on iPhone/iPad when the user chooses skeleton-guided capture assistance. This is used to guide point collection and is not a medical or biometric identity feature.
-
Point clouds, mesh vertices, mesh triangle indices, vertex colors, local origin markers, ruler measurements, QR transforms, placement transforms, and capture-box settings.
-
Imported and loaded files such as USDZ, USD, USDA, OBJ, PLY, GLB, GLTF, FBX, JSON, CSV, ZIP, images, and generated export packages.
-
Local network session state needed to pair nearby user-controlled devices.
3. What the developer collects
In this build, Orthopractis does not collect camera frames, world-sensing data, location data, contacts, advertising identifiers, analytics events, mesh files, USDZ files, exported files, or peer-transfer contents through a developer-operated server. The developer receives information only when a user intentionally sends it, such as by emailing support at info@orthopractis.com.
4. Device permissions and purpose
The apps request permissions only for app features:
-
Camera / AR access: local surface capture, QR recognition, raycasting, mesh preview, USDZ placement, and skeleton-guided point collection on supported devices.
-
World sensing on Apple Vision Pro: QR alignment, scene reconstruction, and boxed immersive mesh capture.
-
Local network / Bonjour: peer-to-peer transfer between nearby user-controlled devices running PlaceMesh and PlaceMesh Viewer.
-
Photo/file export permissions where applicable: saving or sharing files only when the user selects an export or share action.
-
Motion where applicable: stabilizing immersive placement, capture guidance, and local measurements.
5. User-controlled sharing and export
Data leaves the device only when the user chooses an explicit action such as Export, Share, AirDrop, Save to Files, ShareLink, Send to AR, USDZ to AR, or paired-device transfer. The user controls the destination and is responsible for choosing whether to share generated files or imported assets.
6. Local network sharing
Peer-to-peer sharing uses Apple's local networking frameworks to exchange processed scene data between nearby devices controlled by the user. Typical transferred data may include mesh vertices, vertex colors, triangle lists, point clouds, QR alignment transforms, USDZ file data or references, and placement transforms. Orthopractis does not receive this peer-transfer content.
7. Imported models and third-party content
Users are responsible for the rights, permissions, and content of imported USDZ or other 3D files. PlaceMesh does not grant rights to third-party assets and does not verify whether a user has permission to scan, import, export, or share a particular object, person, space, model, brand asset, or file.
8. Retention and deletion
Files saved by the app remain on the device or in user-selected storage until the user deletes them. Users may delete exports, imported assets, project files, and app data through the app where available, through Files, through device storage settings, or by deleting the app.
9. Children and sensitive spaces
The apps are not directed to children. Users should not scan people, private spaces, confidential sites, copyrighted objects, or sensitive environments unless they have the required permission and a lawful basis to do so.
10. Security
The apps use platform file storage, system permission prompts, local sandboxing, and user-controlled export workflows. No software can guarantee absolute security. Users should avoid exporting or sharing sensitive scans unless they trust the destination.
11. Changes
This policy may be updated as app features evolve. The in-app consent screen and website copy identify the current policy date.
12. Contact
Privacy and support contact: info@orthopractis.com
Privacy URL: https://www.orthopractis.com/privacy
Support URL: https://www.orthopractis.com/placemesh
Terms URL: https://www.orthopractis.com/terms-of-use
PlaceEasy Privacy Policy
Effective date: 2026-05-30
Developer: Orthopractis Contact: info@orthopractis.com Support: info@orthopractis.com Privacy Policy URL: https://www.orthopractis.com/privacy
Summary
PlaceEasy is designed as a local file-import and AR/spatial placement tool for iOS and visionOS. The current build does not include analytics, advertising, user tracking, account registration, cloud sync, server uploads, subscriptions, or third-party SDKs.
All controls, help, privacy text, and terms remain in the normal app window or the transparent iOS AR overlay. The visionOS immersive space contains only RealityKit scene content: imported files plus their Cube A and Sphere B rigs.
Every-load consent before app use
PlaceEasy shows a Privacy Policy and Terms of Use consent dialog every time the app or app window is loaded, before the normal iOS AR or visionOS app content opens. The user must tap Yes — agree and open PlaceEasy for that launch. If the user taps No — decline and close, PlaceEasy keeps the normal app content closed, clears the current acceptance state, and requests the current app/window scene to close.
The app may store a local consent version and acceptance date on the device as a reference record, but this does not bypass the consent dialog on the next launch. Consent is requested again every time the app loads.
Data collection by the app
PlaceEasy does not collect personal data in the current build. Imported 3D files stay local to the device unless you manually share, export, back up, or delete them outside the app through Apple system tools.
If we later add accounts, analytics, crash reporting, cloud storage, support uploads, server-side processing, subscriptions, advertising, or third-party SDKs, we will update this policy, our App Store privacy answers, and the app privacy manifest before release.
Imported files
When you choose USDZ, USD, USDA, USDC, Reality, or FBX files from the system Files picker, PlaceEasy copies valid selected files into the app’s local Documents/ImportedAssets folder.
USDZ, USD, USDA, USDC, and Reality files are used for local AR/spatial display and manipulation. FBX files are copied only as conversion/reference files and are not rendered directly by RealityKit in this build.
The in-app Unload active file control removes the active file from the live AR/immersive scene, but it does not delete the copied local file. The Clean copied files action deletes PlaceEasy local import copies from the app container. You can also delete copied files through the Files app, device storage management, or by deleting the app.
Camera and AR use on iOS
On iOS, PlaceEasy uses the camera only for ARKit tracking and the live AR camera background. Camera frames are processed locally by Apple’s ARKit/RealityKit frameworks for AR placement. PlaceEasy does not store, upload, sell, or analyze camera frames.
World-sensing and spatial placement on visionOS
On visionOS, PlaceEasy uses local spatial/world placement only to position imported files and their cube/sphere handles in the room. The immersive space contains no HUD, ornaments, file picker, popover, sheet, or SwiftUI control surface. File import, workflow, cleanup, help, privacy, terms, and settings remain in the normal PlaceEasy window.
PlaceEasy does not upload world-sensing data, room data, imported files, or placement settings in this build.
Tracking and advertising
PlaceEasy does not track users across apps or websites. PlaceEasy does not use advertising identifiers, third-party advertising SDKs, analytics SDKs, data brokers, or cross-app tracking.
Support communications and Wix website
If you contact us by email or through the Wix support site, we may receive the information you choose to provide, such as your name, email address, device model, app version, message, screenshots, and troubleshooting details. This information is used only to respond to support requests, improve support documentation, and maintain the app.
Do not send confidential, restricted, construction-sensitive, medical, personal, or client-owned files unless you have permission and we have agreed to receive them.
Our Wix website may process visitor information according to Wix’s own privacy practices and any Wix features enabled on the site. Review Wix’s privacy policy and cookie tools when configuring the site.
Children
PlaceEasy is not directed to children. The app does not knowingly collect personal information from children.
Data retention and deletion
Imported files remain in the app’s local Documents storage until you tap Clean copied files, delete them through system file management, or delete the app. Deleting the app removes its local app container from the device. Device backups may include app documents depending on the user’s system backup settings.
Support emails and Wix support messages are retained only as long as reasonably needed to respond, maintain records, protect legal rights, or comply with obligations. You may request deletion of support communications by contacting info@orthopractis.com, subject to legal or security retention needs.
Security
PlaceEasy relies on Apple platform sandboxing and the system document picker for local file access. No storage or processing method can be guaranteed to be perfect, so avoid importing files that you are not permitted to use or store on the device.
International users
If you contact us through the support website or email, your support information may be processed in the country where the developer or website provider operates. Use the app only if you agree to this handling of support communications.
Changes
This policy may be updated when PlaceEasy changes. The updated policy will be posted at https://www.orthopractis.com/privacy. Continued use after an update means the current version of the policy applies to the current app behavior.
Contact
Questions about privacy or support can be sent to info@orthopractis.com.
Privacy Policy VisionMeshCapture
Last updated: 6.5.2026
VisionMeshCapture is a visionOS app for Apple Vision Pro. It allows users to capture selected reconstructed environment mesh, optionally use approved enterprise main-camera access for local color sampling, load 3D models, align point clouds, and export mesh packages.
Data processed by the app
Depending on how the user operates the app, VisionMeshCapture may process the following data locally on the device:
-
world-sensing and scene-reconstruction geometry;
-
selected mesh vertices, faces, normals, classifications, and point-cloud data;
-
optional enterprise main-camera frames for local color sampling when approved access is available;
-
imported 3D files such as USDZ, USD, PLY, GLB, GLTF, FBX, OBJ, MTL, and textures;
-
vertex colors, texture/material summaries, and color analytics;
-
captured and imported model transforms;
-
export files including PLY, USDZ, CSV, JSON, and ZIP packages;
-
local session logs shown in the app UI.
Local processing
VisionMeshCapture is designed to process core capture, color, alignment, and export data locally on device. The app does not require sign-in, an account, or server upload for core functionality.
Generated files remain in the app container unless the user explicitly saves or shares them.
User-controlled export and sharing
When the user prepares an export package, the app may create files such as:
-
captured_environment.ply;
-
captured_environment.usdz;
-
imported USDZ files;
-
captured_vertices.csv;
-
captured_faces.csv;
-
pick/color analytics CSV;
-
import summaries;
-
manifest.json;
-
a ZIP export package.
The user controls whether these files are saved or shared.
Enterprise main-camera access
If approved enterprise main-camera access is available, VisionMeshCapture may use camera frames locally to improve color sampling of selected mesh surfaces. Camera frames are processed locally for the capture/color workflow and are not uploaded by the app.
If enterprise access is unavailable, the app uses a fallback mesh/classification capture path.
No tracking
VisionMeshCapture does not track users across apps or websites.
No advertising
VisionMeshCapture does not include advertising.
No account requirement
VisionMeshCapture does not require a user account or sign-in.
Third-party services
The current app build should not include analytics, advertising, or cloud-upload SDKs. If any third-party services are added later, this Privacy Policy and App Store privacy answers must be updated before distribution.
Sensitive spaces and user responsibility
Spatial mesh data, camera-derived color samples, imported files, and exported packages can reveal private rooms, objects, screens, documents, bystanders, or restricted locations. Users should capture and share only spaces they are authorized to scan and should inspect export files before sharing.
Children
VisionMeshCapture is not designed to knowingly collect personal information from children. Use in schools, training environments, or supervised settings should follow applicable consent and privacy requirements.
Contact
For privacy questions, contact:
Privacy Policy OrthoGaitApp
Privacy Policy for OrthoGait App and OrthoGaitViewer App
Effective date: April 18, 2026
Orthopractis respects user privacy. This Privacy Policy explains how OrthoGaitApp for iPhone and iPad and OrthoGaitViewer for Apple Vision Pro handle information, permissions, local processing, optional paired-device communication, exports, and user controls.
This policy applies to:
- OrthoGait App
- OrthoGaitViewer App
If these apps are updated to add new data flows, cloud services, analytics, advertising, account systems, or other collection features, this policy must be updated before release.
1. Summary
OrthoGait App and OrthoGaitViewer app are designed around on-device processing and user control.
In the core packaged workflow:
- no account sign-in is required
- no advertising is included
- no third-party tracking is used
- no developer-hosted cloud account is required
- exports are created only after explicit user action
- paired-device communication is optional and occurs only over the same local network
2. OrthoGait App
OrthoGaitApp is the iPhone and iPad capture application.
It uses the device camera to estimate gait, posture, and related movement metrics on device. It can show live measurements, support Static Calibration, review session quality, and create exports when the user explicitly chooses to do so.
When the optional paired-device workflow is enabled, OrthoGaitApp can broadcast abstract pose, metric, and shared-marker state packets from the iPhone or iPad to a paired OrthoGaitViewer device on the same local network. In the normal live viewer workflow, images and video are not transmitted to the viewer.
3. OrthoGaitViewer App
OrthoGaitViewer is the native Apple Vision Pro companion application.
It receives abstract posture, joint, gait, quality, and optional supplemental metric packets from OrthoGaitApp over the same local network after user consent. It can display the session in a viewer window and, when enabled, in an immersive environment.
OrthoGaitViewer can also use Apple Vision Pro spatial sensing and printed-marker recognition to help align the mirrored session in the room. This workflow is optional and is used for local alignment and visualization.
In the normal viewer workflow, OrthoGaitViewer is not intended to receive a live image or video feed from OrthoGaitApp.
4. Permissions Used
OrthoGait App
OrthoGaitApp may request:
- Camera access, to perform on-device pose and movement estimation
- Local Network access, to optionally mirror abstract pose and metric packets to the paired OrthoGaitViewer device on the same local network
OrthoGaitViewer App
OrthoGaitViewer may request:
- Local Network access, to receive the paired session stream from OrthoGaitApp
- Spatial or world-sensing related permissions, to support local room alignment and immersive visualization on Apple Vision Pro
If a user does not grant a required permission, related features may be unavailable.
5. Data Handling Approach
On-device processing
The core movement-estimation workflow is designed to run on the user’s device.
Optional local-network pairing
If the user enables the paired workflow, the apps exchange live abstract pose, metric, and marker-state packets over the same local network so the Vision Pro viewer can mirror the current session.
No required account system
The packaged workflow does not require account creation or sign-in for core use.
No advertising or third-party tracking
The packaged workflow is not intended to use advertising SDKs or third-party tracking technologies.
6. What OrthoGait App does not do in the core packaged workflow
In the core packaged workflow, OrthoGaitApp is not intended to:
- require the user to create an account to begin capture
- upload normal live capture sessions to an Orthopractis-operated cloud service
- use third-party advertising identifiers for tracking
- send normal live camera video to OrthoGaitViewer during ordinary paired viewing
7. What OrthoGaitViewer App does not do in the core packaged workflow
In the core packaged workflow, OrthoGaitViewer is not intended to:
- require a user account for core viewing
- use third-party advertising identifiers for tracking
- operate as a public cloud viewer service
- require the transfer of the iPhone or iPad camera feed during ordinary paired viewing
- perform personal identity recognition
8. Exports
Both apps can create local export files only after explicit user action.
OrthoGait App exports
OrthoGait App may create local session exports containing movement-related measurements, summaries, timestamps, and related session information chosen by the user.
OrthoGaitViewer exports
OrthoGaitViewer may create a local export of the recent viewer measurement window after explicit user action.
Exported files are controlled by the user. If the user chooses to save, share, or send an export using Apple platform features or a third-party destination selected by the user, that user action controls where the file goes after export.
9. Retention
Orthopractis does not operate a required user account database for the core packaged workflow described here.
For the core packaged workflow:
- live processing occurs on device
- local paired communication occurs within the user’s local network environment when enabled
- exported files remain where the user saves them, until the user deletes or moves them
If a future version adds remote storage, cloud sync, online collaboration, or account-based history, this policy must be updated.
10. Third Parties
The core packaged workflow is not intended to include third-party advertising or third-party tracking SDKs.
However, the apps run on Apple platforms and may use Apple-provided operating-system functionality such as permissions, local networking frameworks, file storage locations, or the share sheet. Those platform-level services are governed by Apple’s own terms and privacy practices.
11. Security and User Control
The apps are designed to support user control over privacy-sensitive functions by:
- requesting permissions through Apple system dialogs
- keeping core movement processing on device
- making paired-device communication optional
- making export user-initiated
- not requiring account sign-in for the core packaged workflow
Users can manage permissions in device Settings and can stop using optional paired-device features at any time.
12. Intended Use and Important Limitations
OrthoGait App and OrthoGaitViewer App are intended for movement review, biomechanics, wellness, education, training, informational, and research-oriented workflows.
They are not intended to provide diagnosis, emergency triage, or treatment decisions. Measurements and supportive summaries are algorithm-derived estimates and may contain errors or inaccuracies.
13. Children’s Privacy
These apps are not directed to children as a Kids Category product. If you believe personal information has been provided to Orthopractis in a way that conflicts with applicable law, contact the address below.
14. Changes to this Policy
Orthopractis may update this Privacy Policy when the apps, features, or data practices change. The effective date at the top of this page should also be updated.
15. Contact
Orthopractis
Email: info@orthopractis.com
Website: https://www.orthopractis.com
Privacy page: https://www.orthopractis.com/privacy
Privacy Policy – Ergonomics
Last updated: 20/4/2026
Ergonomic ("the App") is developed by Orthopractis. This Privacy Policy explains how the App handles information.
1. Overview
Ergonomic is designed to provide posture awareness and ergonomic assessment using on-device camera processing. The App does not require user accounts and does not collect personal identity information.
2. Camera Usage
The App uses the device camera to:
-
detect body landmarks
-
estimate posture and alignment
-
calculate ergonomic metrics such as eye-to-screen distance and joint angles
Camera data is processed in real time on the device.
The App does not record, store, or transmit raw video or images to external servers.
3. Data Processing
All core processing is performed locally on the device.
When multi-device functionality is used (e.g., spatial visualization):
-
only processed posture data (such as joint positions and orientation values) is transmitted
-
transmission occurs over a local network connection
-
no raw camera data is shared
-
4. Data Collection
The App does not collect personal data such as:
-
name
-
email
-
location
-
identifiers
The App does not create user profiles.
QR Marker Usage
The App may use printed QR markers as spatial references for alignment purposes with apple vision pro. These markers are used only to establish coordinate positioning and do not contain personal data.
No information from QR markers is stored or transmitted externally.
5. Data Storage
The App does not store personal data on external servers.
Any temporary data used for real-time processing remains on the device and is not retained beyond app usage.
6. Third-Party Services
The App does not use third-party analytics, advertising networks, or tracking systems.
7. Data Sharing
No personal data is shared with third parties.
8. Security
The App relies on Apple’s secure system frameworks and on-device processing to protect user data.
9. Children’s Privacy
The App does not knowingly collect personal information from children.
10. Intended Use
The App is intended for:
-
posture awareness
-
ergonomic self-assessment
-
education and visualization
The App is not intended for medical diagnosis, treatment, or clinical decision-making.
11. Changes
This Privacy Policy may be updated. Changes will be reflected on this page.
12. CONTACT
Support:info@orthopractis.com
Website: https://www.orthopractis.com
Ergonomic & ErgonomicViewer_visionOS
Last Updated: April 2026
1. Overview
Ergonomic and ErgonomicViewer_visionOS (collectively, “the App”) are designed with privacy as a core principle. The App enables real-time posture visualization using on-device processing and spatial computing technologies, including Apple Vision Pro.
We are committed to ensuring that your data remains secure, private, and under your control.
2. Data Collection
The App does not collect personal data in the traditional sense.
During use, the App processes:
-
Body landmark positions (e.g., joint coordinates)
-
Posture-related measurements (e.g., angles, distances)
-
Device spatial positioning (for alignment in immersive space)
These data are used solely for real-time posture visualization and analysis.ll posture processing occurs locally on device. Only abstracted posture data are transmitted over a local network. No images, video, or personal data are collected, stored, or shared
3. Camera Usage
The App uses the device camera to detect body landmarks and estimate posture.
-
No photos or videos are recorded
-
No images are stored
-
No camera data is transmitted externally
Camera data is processed locally and temporarily on your device.
4. Data Processing
All processing is performed on-device:
-
Posture detection and analysis occur on iPhone or iPad
-
Spatial visualization occurs on Apple Vision Pro
-
No cloud processing is used
This ensures maximum privacy and minimal data exposure.
5. Data Transmission (Local Network Only)
When using Ergonomic with ErgonomicViewer_visionOS:
-
Devices communicate over a local network connection (Wi-Fi or peer-to-peer)
-
Only processed posture data are transmitted (e.g., joint positions and orientations)
-
No images, video, or raw camera data are transmitted.all posture processing occurs locally on device. Only abstracted posture data are transmitted over a local network. No images, video, or personal data are collected, stored, or shared
This communication is used exclusively for real-time visualization.
6. No Personal Identification
The App does not:
-
Perform facial recognition
-
Identify users
-
Track identity across sessions
-
Collect biometric identifiers
All posture data are anonymous and non-identifiable.
7. Data Storage
By default:
-
No data are stored
-
No session data are retained
If optional features enable saving data:
-
Storage remains local to the device
-
Users have full control over saved content
8. No Third-Party Sharing
We do not:
-
Share data with third parties
-
Sell user data
-
Use analytics services that collect personal information
No data leave your device.
9. Network Scope
The App operates under a local-only communication model:
-
No external servers
-
No cloud infrastructure
-
No remote data transmission
All device communication occurs within the user’s local environment.
10. Data Minimization
The App follows a strict data minimization principle:
Only the minimum required data for posture visualization are processed and transmitted.
This ensures:
-
Efficient performance
-
Reduced data exposure
-
Enhanced privacy protection
11. Security
We implement safeguards to protect data integrity:
-
Local processing reduces exposure risk
-
No persistent transmission channels
-
Temporary in-memory data handling
Users maintain full control over their environment and data.
12. Intended Use
The App is intended for:
-
Posture awareness
-
Educational use
-
Ergonomic observation
It is not intended for medical diagnosis or treatment.
13. Children’s Privacy
The App does not knowingly collect personal data from children.
Since no personal data are collected or stored, risks are minimized.
14. User Control
Users can:
-
Start or stop posture capture at any time
-
Disconnect devices
-
Control any optional data storage features
15. Changes to This Policy
We may update this Privacy Policy periodically.
Updates will be reflected with a revised “Last Updated” date.
16. Contact
For questions or support:
🌐 Orthopractis.com
ORTHOHAND MOTION – PRIVACY POLICY
Effective date: 2026-03-30
OrthoHand Motion processes motion session data for visualization, wellness tracking, education, and research workflows. The app is not intended to diagnose, treat, cure, or prevent disease.
1. DATA PROCESSED
The app may process motion session data such as timestamps, tracked joint positions, orientations, derived metrics, device metadata, calibration state, app version, and consent choices.
2. ON-DEVICE BY DEFAULT
Motion session data is processed and stored locally on device by default. Optional exports are created only when initiated by the user.
3. RESEARCH MODE
Research Mode may create structured CSV and JSON exports and stage anonymized local contribution folders. In this build, cloud upload is disabled by default and any future upload flow must be explicitly enabled by the user.
4. OPTIONAL AI FEATURES
If AI-generated summaries are added in a future build, selected session summary data may be transmitted to a third-party AI service only after explicit user consent.
5. DATA NOT COLLECTED IN THIS BUILD
This build does not intentionally collect name, email, Apple ID, face imagery, raw camera video, voice audio, diagnosis, treatment recommendation, or advertising identifiers as part of Research Mode staging.
6. RETENTION
Local files remain on device until deleted by the user or removed when the app is uninstalled.
7. EXPORTS
Exported files are controlled by the active subscription tier and by user action. Users are responsible for handling exported files in accordance with their own privacy, ethics, and legal obligations.
8. CONTACT
Support:info@orthopractis.com
Website: https://www.orthopractis.com
