privacy | Orthopractis.com

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.

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

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:

info@orthopractis.com

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:

info@orthopractis.com

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.

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.

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

Support URL: https://www.orthopractis.com/orthoosteotomy

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:

info@orthopractis.com

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

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

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.

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:

info@orthopractis.com

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:

info@orthopractis.com

Website:

www.orthopractis.com

www.orthopractis.com/privacy

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.

Links

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.

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:

info@orthopractis.com

Privacy Policy OrthoGaitApp

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:

📧 info@orthopractis.com

🌐 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