

OrthoOsteotomy Privacy Policy
Last updated: 2026-06-05
App: OrthoOsteotomy
Provider: ORTHOPRACTIS.COM SINGLE MEMBER P.C.
Contact: info@orthopractis.com
Privacy Policy URL: https://www.orthopractis.com/privacy
Support URL: https://www.orthopractis.com/orthoosteotomy
Terms of Use: https://www.orthopractis.com/terms-of-use
1. Summary
OrthoOsteotomy is a local-first osteotomy planning-support and educational application for trained healthcare professionals, researchers, educators, and authorized institutional users. The app lets a user select an X-ray image, calibrate the image, place ordered landmarks, display geometric measurements and overlays, review osteotomy planning suggestions, optionally use immersive board visualization, optionally use Muse spatial-stylus input, and optionally export results through user-controlled Apple system sharing.
The current project is designed without advertising SDKs, third-party tracking SDKs, third-party analytics SDKs, user accounts, subscriptions, app-operated cloud sync, or automatic upload of X-ray images or measurement files to Orthopractis.
2. Scope of this policy
This policy explains how OrthoOsteotomy handles information in the app and how support communications are handled if a user voluntarily contacts us. It applies to the OrthoOsteotomy app and the OrthoOsteotomy support, privacy, and terms pages hosted by Orthopractis.
This policy does not replace the privacy policies of Apple, an institution, a hospital, a picture archiving system, an email provider, or any third-party service chosen by the user when exporting, saving, emailing, or otherwise sharing files.
3. Information processed locally by the app
Depending on how the user operates the app, OrthoOsteotomy may process the following information locally on the user's device:
-
A user-selected X-ray image or training image.
-
Calibration points C1/R2 and the entered calibration value.
-
Ordered anatomical landmarks P1-P9, hinge point H, and wedge/base point D.
-
Derived geometric outputs such as MAD, mLDFA, JLCA, mMPTA, HKA, MJL, Fujisawa target percentage, alpha, beta, delta, omega, DD', and delta DD'.
-
Display overlays, construction lines, angle arcs, labels, and help-window state.
-
Optional local export files in JSON, CSV, image, or other app-supported formats.
-
Optional spatial placement data used to position the immersive board or panel.
-
Optional Muse spatial-stylus aim, projected pointer, button state, and haptic-event state.
-
Local settings such as panel size, distance, height, sliders, selected workflow mode, and help preferences.
This information is processed to provide the app's user-facing functions. The app does not need an Orthopractis account to perform the local workflow.
4. Patient and clinical information warning
X-ray images and exported measurement files may contain protected health information or other sensitive clinical information if the user imports or exports such material. Users are responsible for using only images and files they are authorized to use and for following institutional policy, patient consent requirements, professional obligations, and applicable privacy law.
Users should remove or obscure patient identifiers whenever possible for training, support, demonstrations, and App Review materials.
5. Information collected by Orthopractis through the app
For the current local-first build described by this policy, Orthopractis does not collect app images, measurement coordinates, measurement outputs, identifiers, advertising data, tracking data, analytics data, account data, or location data from the core app workflow.
If future versions add analytics, crash reporting, cloud sync, accounts, subscriptions, telemetry, collaboration, or any third-party SDK that collects data, this policy and the App Store privacy answers must be updated before release.
6. User-controlled export and sharing
When the user chooses to export or share data, the app may use Apple system components such as Files, Share Sheet, Photos, Mail, Messages, AirDrop, or another destination selected by the user. The user controls the destination and is responsible for ensuring that export is authorized.
After export, the receiving app, service, file location, institution, email provider, cloud provider, or recipient is responsible for its own handling of the file according to its own terms and privacy policy.
7. Support communications
If a user contacts info@orthopractis.com, the email address, message, attachments, screenshots, logs, and any other information voluntarily provided will be received by Orthopractis for support, troubleshooting, safety review, privacy response, or product-improvement follow-up.
Users should not send protected health information, patient-identifiable X-rays, patient names, dates of birth, hospital IDs, or other identifiers to support unless they are authorized to do so by their institution, patient consent, and applicable law. For support screenshots, use training images or de-identified images whenever possible.
8. Legal bases and purposes where applicable
Where privacy law requires a legal basis, processing is limited to purposes such as:
-
Providing the local app functionality requested by the user.
-
Responding to voluntary support communications.
-
Maintaining security and troubleshooting.
-
Complying with legal obligations.
-
Improving documentation and reliability using de-identified or non-patient support information where permitted.
9. Tracking, advertising, and analytics
The current build does not track users across apps or websites, does not include advertising, does not use the IDFA, and does not include third-party analytics SDKs.
10. Third-party services and Apple platform services
The app may use Apple platform features selected or authorized by the user, such as PhotosPicker or file import, Share Sheet, Files, and device permission prompts. Apple platform features are governed by Apple's operating-system behavior and the user's device settings.
The current project does not integrate a third-party analytics service, advertising network, third-party tracking network, or Orthopractis-operated cloud backend.
11. Retention
Core app data remains on the user's device, in the current session, or in files saved or exported by the user. The app does not automatically upload these materials to Orthopractis.
Support emails and voluntary attachments may be retained as needed to respond to the request, troubleshoot the issue, protect legal rights, satisfy legal obligations, and maintain support history. Users may request deletion of voluntarily sent support material by contacting info@orthopractis.com, subject to legal, regulatory, safety, or dispute-retention obligations.
12. Deletion and access requests
Users can delete local app files and exported files from their own device or storage destination. For deletion or access requests concerning materials voluntarily sent to Orthopractis support, contact info@orthopractis.com and describe the request with enough detail to identify the material.
13. Security
Users should protect their devices, app exports, and clinical images according to institutional security policy. Orthopractis uses reasonable administrative and technical safeguards for support communications, but no email or network transmission can be guaranteed to be completely secure.
14. Children
OrthoOsteotomy is intended for trained healthcare professionals, researchers, educators, and authorized institutional users. It is not directed to children.
15. International use
Users are responsible for ensuring that their use of the app, imported images, exported files, and support communications complies with applicable laws and institutional requirements in their jurisdiction.
16. Changes to this policy
This policy may be updated to reflect changes in the app, laws, Apple requirements, or support practices. The updated policy will be posted at https://www.orthopractis.com/privacy with a revised date.
17. All information received from the software output must be clinically reviewed regarding its plausibility before patient
treatment. The app is indicated for assisting healthcare professionals. Clinical judgment and experience are required to
properly use the software. These instructions alone do not replace in-depth training in planning for osteotomies. It only
serves as a general guideline. Any influence on operator decision-making remains the surgeon's own responsibility and
experience. A surgeon must always rely on professional clinical judgement when deciding whether to use a particular
technique for a particular patient. The app does not dispense medical advice. The software is not for primary image
interpretation.
Contact
Privacy questions, deletion requests for voluntarily sent support materials, and support requests may be sent to:
Support URL: https://www.orthopractis.com/orthoosteotomy
.
CamouflageMesh Privacy Policy
Effective date: 7 June 2026
Developer: Orthopractis.com Single Member P.C. / Orthopractis
Support email: info@orthopractis.com
Support page: https://www.orthopractis.com/camouflagemesh
Privacy page: https://www.orthopractis.com/privacy
Terms page: https://www.orthopractis.com/terms-of-use
1. Introduction
This Privacy Policy explains how CamouflageMesh and CamouflageMesh Vision handle information when you use the app on iPhone, iPad, or Apple Vision Pro. The policy covers surface capture, AR and spatial workflows, camera or photo palette sampling, mesh processing, colour analysis, preview, export, nearby transfer, support contact, and related Orthopractis support pages.
CamouflageMesh is designed as a local-first surface mesh and colour-planning app. It helps you capture or import a physical-scale surface, sample colours from the surrounding environment, build a camouflaged vertex-colour mesh, inspect the colour table, preview the result, and export files that you choose to save or share.
2. Provider and contact
The app is provided by Orthopractis.com Single Member P.C. / Orthopractis. Public contact details are available through the Orthopractis website. For privacy questions, support requests, or policy questions, contact info@orthopractis.com. The intended support page is https://www.orthopractis.com/camouflagemesh. The intended privacy page is https://www.orthopractis.com/privacy.
3. Summary of the current privacy position
Based on the current local-first implementation package, CamouflageMesh does not require a user account, does not include advertising, does not use tracking for advertising, does not declare a developer-operated analytics endpoint, and does not upload core mesh, photo, AR, colour, or export data to an Orthopractis cloud service as part of the normal packaged workflow. Core processing is designed to take place locally on the device.
Data can still leave your device if you choose to save, export, share, AirDrop, email, send files to a paired or nearby device, place files in cloud storage through the operating-system share sheet, or contact support outside the app. Those actions are controlled by you and may involve Apple services, email providers, cloud storage providers, messaging apps, nearby devices, or other third-party destinations that are not operated by Orthopractis.
4. Information processed locally by the app
Depending on the features you use, CamouflageMesh may process AR frames, world-sensing information, scene reconstruction data, surface mesh vertices, triangle indices, vertex colours, normals, classifications, imported 3D files, selected or captured photos, environment colour samples, colour palette statistics, colour comparisons, generated camouflage roles, colour tables, paint instructions, USDZ or mesh resources, manifests, ZIP files, local session state, and export files.
This information is used to provide the features you request. Surface mesh data is used to build and preview physical-scale geometry. Photos or enterprise camera frames, when available and authorised, are used to derive environment colours. Colour analysis is used to create swatches and match surface colours to the environment. Export data is used to produce the files you choose to save or share.
5. Camera, AR, photo, local network, and enterprise permissions
CamouflageMesh may ask for camera permission when you choose a feature that needs camera capture, such as surface capture or environment photo capture. It may ask for AR, world-sensing, plane detection, or scene reconstruction access when you choose to build or review a physical-scale surface mesh. It may ask for photo library access when you choose an existing image or choose to save generated output. It may ask for local network, peer discovery, or Bonjour-related access when you start a nearby sharing or paired-device workflow.
CamouflageMesh Vision may include an enterprise main-camera workflow for Apple Vision Pro only when the required enterprise licence, provisioning, signed entitlement, supported device configuration, and active app state are present. If those conditions are not present, the app uses fallback workflows such as selected photos, imported files, or existing mesh colours. Enterprise camera frames, when used, are intended to be processed locally for palette sampling and are not uploaded by the app as part of the described workflow.
6. Photos, meshes, spatial data, and sensitive places
Surface meshes, photos, world-sensing data, and exported files can reveal sensitive information. They may show private rooms, bystanders, confidential objects, screens, documents, restricted areas, prototypes, worksites, addresses, or other details that you or another person may not want to share. You are responsible for scanning and exporting only surfaces, spaces, objects, and files that you are authorised to capture, process, store, and share.
Before exporting or sharing, inspect the files and previews. A mesh export may contain geometry even if a photograph looks harmless. A colour table may reveal the palette of a private or restricted space. A ZIP package may include manifests or metadata that describe source files, scale, names, settings, or workflow choices.
7. Exports and user-controlled sharing
When you create an export package, the app may generate files such as a camouflaged mesh, USDZ files where supported, colour table CSV, colour table HTML, colour table JSON, text summaries, paint shopping or instruction lists, palette summaries, manifests, and ZIP archives. These files remain local unless you choose to save or share them through available system tools.
If you use Share, AirDrop, Files, Photos, Messages, Mail, cloud storage, or another destination, the chosen destination may process the file under its own privacy policy and terms. Orthopractis does not control third-party apps, operating-system sharing destinations, cloud folders, email services, or receiving devices selected by you.
8. Nearby device transfer and paired-device workflows
The app package describes optional nearby sharing, QR sync, local peer transport, and paired-device workflows. These features are intended for user-initiated transfer between nearby devices. Transfer availability, reliability, and privacy can depend on device configuration, local network, Bluetooth, Wi-Fi, operating-system state, and the destination device. Use these features only with devices and users you trust.
9. Support requests and voluntary contact
The app does not require an account for the packaged workflow. If you contact Orthopractis by email or through a website form, you may voluntarily provide your name, email address, device model, operating-system version, app build number, screenshots, exported files, logs, or other support details. Orthopractis may use that information to respond to your request, troubleshoot the issue, maintain records of the support interaction, and improve documentation or app quality.
Do not send private photos, confidential meshes, restricted worksite files, patient information, personal data, or third-party content to support unless you have permission and the information is necessary for the request. If you send files to support, you may ask Orthopractis to delete them when they are no longer needed, subject to legal, security, and record-keeping needs.
10. Tracking, advertising, analytics, and third-party SDKs
The current package states that the normal app workflow does not include advertising, tracking, Orthopractis analytics, cloud upload, or an account requirement. The app should not track users across apps or websites, should not use an advertising identifier, and should not profile users for advertising purposes.
If a future version adds analytics, crash reporting, accounts, cloud upload, subscriptions, server-side support upload, advertising, tracking, or third-party SDKs that collect data, Orthopractis must update this Privacy Policy, the App Store privacy answers, and any required privacy manifests before release.
11. Apple and third-party services
The app runs on Apple platforms and may use Apple frameworks, operating-system permission prompts, local file storage, system share sheets, AirDrop, Files, Photos, Mail, and App Store distribution. Apple and any third-party destination selected by you may process information under their own policies. Orthopractis is not responsible for data handling by Apple, email providers, cloud providers, messaging apps, local network devices, or other services you choose outside the app.
12. Children
CamouflageMesh is not directed to children. The app is intended for users who can understand the permission, privacy, export, and responsible-use requirements. Use in schools, training environments, research demonstrations, or supervised settings should follow all applicable consent, safety, and privacy requirements.
13. Retention and deletion
Core scans, photos, meshes, colour tables, exports, and local session files are stored locally only when the app or operating system saves them as part of your workflow. You can delete local files through the app, the Files app, device storage management, the destination app, or by deleting the app. Deleting the app generally removes the app container from the device, subject to normal operating-system backups and destination services selected by you.
Orthopractis does not receive or retain core app content in the current local-first workflow unless you intentionally send it to support or another Orthopractis contact channel. Support emails and website messages may be retained as long as reasonably needed to respond, maintain records, protect legal rights, prevent misuse, or comply with obligations. You may request deletion of support communications by contacting info@orthopractis.com.
14. Security
CamouflageMesh relies on Apple platform sandboxing, operating-system permissions, local processing, and user-controlled export workflows. No software, local storage method, network transfer, or sharing destination can be guaranteed to be perfectly secure. Avoid scanning, storing, or exporting sensitive materials unless you trust the device, destination, network, and receiving user.
15. International users
If you contact Orthopractis by email or through the support website, your support information may be processed in the country where Orthopractis, its email provider, website provider, or support tools operate. Use the support channels only if you agree to that handling. Local app processing on your device does not require an Orthopractis account or cloud upload in the current build.
16. Your choices and rights
You control whether to grant camera, photo, world-sensing, local network, enterprise camera, and other system permissions. You can change permissions in device Settings. You control whether to save, export, share, AirDrop, email, or transfer files. You may request access, correction, or deletion of support information you have sent to Orthopractis by contacting info@orthopractis.com. Some requests may be limited by legal, security, or record-keeping requirements.
17. Changes to this Privacy Policy
Orthopractis may update this Privacy Policy when the app, platform requirements, data practices, support process, or legal requirements change. The updated policy should be posted at https://www.orthopractis.com/privacy or another stable Orthopractis URL. The app should also update in-app consent text when the policy materially changes.
18. Contact
Privacy and support questions can be sent to info@orthopractis.com. Support page: https://www.orthopractis.com/camouflagemesh. Privacy page: https://www.orthopractis.com/privacy. Terms page: https://www.orthopractis.com/terms-of-use.
FaceCamouflage Privacy Policy
Effective date: June 6, 2026
Contact: info@orthopractis.com
Product page: https://www.orthopractis.com/FaceCamouflage
FaceCamouflage is a local field-colour planning and visualization app. This Privacy Policy explains how the app handles camera images, face mesh geometry, environment colour plans, exports and optional local Apple Vision pairing.
Data processed by the app
FaceCamouflage may process:
-
environment photos selected or captured by the user;
-
live camera frames needed to create an AR preview;
-
AR face mesh vertices, triangle indices, vertex IDs and face-zone data;
-
calculated terrain palette values, RGB/HEX colours, Lab values, blend-score components and paint instructions;
-
user-selected slider settings;
-
exported files such as TXT, CSV, PLY, USDZ or preview images;
-
local pairing packets when the user starts Apple Vision pairing;
-
enterprise license status and local MDM configuration values, if deployed by an organization.
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 or blend score.
Camera and face geometry
The rear camera is used to capture the environment reference. The front camera/TrueDepth workflow is used to visualize the colour plan on a live face mesh when supported. FaceCamouflage does not access Face ID authentication templates, Secure Enclave biometric data, or biometric data used to unlock the device. Face mesh data is used for local visualization, colour-zone placement and user-controlled export.
Local network and Apple Vision pairing
If the user starts Apple Vision pairing, FaceCamouflage may send local device-to-device packets containing mesh vertices, triangle indices, paint-zone colours, vertex IDs, blend metrics and coordinate alignment data to the paired Vision device. This is optional and user-initiated.
Exports and sharing
When the user exports or shares files, those files may include face mesh vertices, paint-zone IDs, RGB/HEX colour values, blend scores, instructions and optional preview information. The user controls where exported files are saved or shared.
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, or user behaviour advertising.
Retention
Live session data is temporary unless the user intentionally saves or exports it. Exported files remain wherever the user saves or shares them. Deleting the app removes local app data subject to normal iOS storage behaviour. Files shared to other apps, cloud storage or contacts must be deleted from those locations by the user.
Third parties
The core workflow does not require third-party analytics, advertising or cloud processing. Apple system frameworks may process permission prompts, camera operation, AR rendering, local networking, file sharing and App Store services according to Apple’s own terms and privacy policies.
Children
FaceCamouflage is not directed to children. Children should use the app only with appropriate adult supervision and only with skin-safe removable materials.
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 exports, delete it from the device, Files app, Photos app or any destination where you saved or shared it.
Changes
This policy may be updated. The current policy will be posted at https://www.orthopractis.com/privacy.
Privacy Policy
Last updated: [25/5/2026
VisionMeshCapture is a visionOS app for Apple Vision Pro. It allows users to capture selected reconstructed environment mesh, optionally use approved enterprise main-camera access for local color sampling, load 3D models, align point clouds, and export mesh packages.
Data processed by the app
Depending on how the user operates the app, VisionMeshCapture may process the following data locally on the device:
world-sensing and scene-reconstruction geometry;
selected mesh vertices, faces, normals, classifications, and point-cloud data;
optional enterprise main-camera frames for local color sampling when approved access is available;
imported 3D files such as USDZ, USD, PLY, GLB, GLTF, FBX, OBJ, MTL, and textures;
vertex colors, texture/material summaries, and color analytics;
captured and imported model transforms;
export files including PLY, USDZ, CSV, JSON, and ZIP packages;
local session logs shown in the app UI.
Local processing
VisionMeshCapture is designed to process core capture, color, alignment, and export data locally on device. The app does not require sign-in, an account, or server upload for core functionality.
Generated files remain in the app container unless the user explicitly saves or shares them.
User-controlled export and sharing
When the user prepares an export package, the app may create files such as:
captured_environment.ply;
captured_environment.usdz;
imported USDZ files;
captured_vertices.csv;
captured_faces.csv;
pick/color analytics CSV;
import summaries;
manifest.json;
a ZIP export package.
The user controls whether these files are saved or shared.
Enterprise main-camera access
If approved enterprise main-camera access is available, VisionMeshCapture may use camera frames locally to improve color sampling of selected mesh surfaces. Camera frames are processed locally for the capture/color workflow and are not uploaded by the app.
If enterprise access is unavailable, the app uses a fallback mesh/classification capture path.
No tracking
VisionMeshCapture does not track users across apps or websites.
No advertising
VisionMeshCapture does not include advertising.
No account requirement
VisionMeshCapture does not require a user account or sign-in.
Third-party services
The current app build should not include analytics, advertising, or cloud-upload SDKs. If any third-party services are added later, this Privacy Policy and App Store privacy answers must be updated before distribution.
Sensitive spaces and user responsibility
Spatial mesh data, camera-derived color samples, imported files, and exported packages can reveal private rooms, objects, screens, documents, bystanders, or restricted locations. Users should capture and share only spaces they are authorized to scan and should inspect export files before sharing.
Children
VisionMeshCapture is not designed to knowingly collect personal information from children. Use in schools, training environments, or supervised settings should follow applicable consent and privacy requirements.
Contact
For privacy questions, contact:
info@orthopractis.com
PRIVACY POLICY for
Last updated: June 2, 2026
OrthoFaceCosmetic App and companion OrthoFaceCosmeticVision App
This section explains how OrthoFaceCosmetic handles face data, AR face geometry, face-mesh measurements, cosmetic colour-guidance overlays, Apple Vision Pro local streaming, user exports, sharing, storage, retention, and deletion.
Website:
www.orthopractis.com
Privacy Policy:
www.orthopractis.com/privacy
Terms of Use:
www.orthopractis.com/terms-of-use
Contact:
info@orthopractis.com
1. FACE DATA AND AR FACE GEOMETRY
OrthoFaceCosmetic uses the device camera and Apple ARKit face-tracking features, when supported by the device, to create a live AR face mesh for educational visualization, facial proportion review, and reversible cosmetic colour-guidance overlays.
For the purposes of this Privacy Policy, “face data” may include the following information when the user starts live AR capture or uses related features:
- AR face mesh geometry produced during the active AR session.
- Mesh vertices.
- Triangle indices.
- Fixed vertex ID references.
- Derived facial landmark positions.
- Derived facial zone classifications.
- Symmetry measurements.
- Facial proportion measurements.
- φ / golden-ratio reference measurements.
- Inverse φ, φ², and φ³ relationship values.
- Cosmetic AutoCorrect plan data.
- Cosmetic colour patch definitions.
- Selected facial review surfaces.
- Patch vertex IDs.
- Overlay opacity and intensity settings.
- Retained, hidden, or rejected cosmetic suggestion states.
- Manual vertex-paint selections entered or selected by the user.
- Optional correction TXT, image, 3D, or report files if the user intentionally exports or shares them.
- Optional local Apple Vision Pro stream packets if the user intentionally starts local Apple Vision Pro pairing and streaming.
OrthoFaceCosmetic does not collect or access Apple Face ID authentication templates, Secure Enclave biometric data, passcode data, or any biometric information used to unlock the device.
OrthoFaceCosmetic does not use face data for identity verification, user identification, biometric authentication, advertising, tracking, third-party profiling, employment decisions, insurance decisions, credit decisions, law-enforcement identification, or any automated decision about a person’s rights or eligibility.
The app’s face-related features are designed for educational visualization, facial proportion review, reversible cosmetic planning, AR teaching, and local user-controlled review only.
Live camera frames are used for AR tracking and visualization. OrthoFaceCosmetic does not save raw camera video or raw face photos by default.
2. HOW WE USE FACE DATA
OrthoFaceCosmetic uses face data only to provide the app’s core educational and visualization features.
The planned uses of face data are:
- To create and display a live AR face mesh.
- To map repeatable mesh vertex IDs to facial surfaces.
- To show optional white vertex ID labels on the live AR face mesh.
- To compute symmetry and proportion-review values.
- To compute φ / golden-ratio reference relationships.
- To compute inverse φ, φ², and φ³ reference relationships.
- To identify facial review zones for educational analysis.
- To generate reversible cosmetic colour-guidance overlays.
- To display transparent colour patches on selected facial review surfaces.
- To display arrows pointing to selected review surfaces.
- To explain why a surface was selected.
- To explain what visual effect a cosmetic colour role may create.
- To suggest generic cosmetic product categories.
- To support manual vertex paint when the user enters or selects mesh vertex IDs.
- To let the user retain, hide, reject, or restore cosmetic suggestions.
- To let the user export or share a correction TXT or other report file if they choose.
- To optionally display the same local visualization on the user’s paired Apple Vision Pro device.
The cosmetic colour map is educational and reversible. It does not physically change the face and does not diagnose a condition.
The app uses the following map colours:
Gold = highlight / visual advance.
Blue = matte contour / visual recession.
Rose = blush / lift / soft transition.
Warm red = lip warmth / definition.
Mint = neutral review / keep natural.
Violet = soft matte shadow / anti-shine / lower-value recession.
Cyan = manual technical vertex-ID selection.
These colours are map colours only. They do not mean that the user should paint literal gold, blue, mint, violet, or cyan makeup on the face.
The app may suggest generic cosmetic product categories such as:
- lighter concealer;
- soft highlighter;
- satin cream highlight;
- illuminating balm;
- matte contour;
- neutral deeper shade;
- contour powder;
- contour stick;
- cream blush;
- powder blush;
- lip tint;
- lip liner;
- lipstick;
- lip stain;
- tinted balm;
- gloss;
- skin tint;
- light foundation;
- setting powder;
- anti-shine powder;
- soft contour powder.
OrthoFaceCosmetic does not recommend cosmetic brands or companies.
OrthoFaceCosmetic does not tell users that their face is defective, ugly, wrong, bad, or must be fixed. The app uses non-judgmental language such as:
- review surface;
- visual weight;
- reversible preview;
- cosmetic suggestion;
- optional correction;
- keep natural;
- retain;
- hide;
- reject.
The app is not a medical device, diagnosis tool, orthodontic treatment planner, surgical planning tool, aesthetic-medical prescription system, beauty score, attractiveness score, identity-verification system, or emergency tool.
3. FACE DATA SHARING AND APPLE VISION PRO LOCAL STREAMING
OrthoFaceCosmetic does not share face data with third parties as part of the core app workflow.
By default, face mesh data, vertex IDs, measurements, cosmetic plans, and colour maps are processed locally on the user’s device.
OrthoFaceCosmetic does not upload live face mesh data, vertex IDs, measurement values, cosmetic colour maps, or AR face geometry to an external server as part of the core workflow.
OrthoFaceCosmetic does not use third-party advertising, third-party face profiling, third-party biometric processing, or third-party tracking for face data.
The app may optionally support local Apple Vision Pro pairing. This feature is user-initiated and is intended only to display the same educational visualization on the user’s paired Apple Vision Pro device.
If the user starts Apple Vision Pro streaming, the iOS or iPadOS device may send a local device-to-device packet to the paired Apple Vision Pro viewer. This local packet may include:
- timestamp;
- mesh vertices;
- triangle indices;
- selected vertex states;
- selected measurements;
- cosmetic colour-plan data;
- patch vertex IDs;
- overlay opacity;
- colour intensity;
- arrow visibility state;
- focused patch ID;
- retained patch state;
- hidden or rejected patch state;
- QR marker coordinate-alignment information when pairing is active.
This Apple Vision Pro stream is:
- local;
- user-initiated;
- device-to-device;
- intended only for the user’s paired Apple Vision Pro visualization;
- not a cloud upload;
- not advertising tracking;
- not third-party profiling;
- not biometric authentication;
- not identity verification.
The app may use a SharedQR marker to help the iOS device and Apple Vision Pro viewer share a coordinate reference. The SharedQR marker is used only for spatial alignment between the two local devices.
If Apple Vision Pro pairing is not started by the user, the local Vision stream is not started.
If Apple Vision Pro pairing is stopped, the local stream stops.
If the user exports or shares a correction TXT, image, 3D file, report, or other file, that file is shared only according to the user’s explicit action through the operating system’s share/export interface.
Users should not scan, stream, export, or share another person’s face without that person’s informed permission.
4. STORAGE, RETENTION, AND DELETION
Live face mesh data is session-only by default.
Live AR face mesh data, vertex data, measurement states, and cosmetic patch states are retained in memory only while the AR session is active and while the app needs them for live visualization.
When the AR session is stopped, the app is closed, or the user leaves the live capture workflow, live face mesh data is discarded from the active session.
OrthoFaceCosmetic does not maintain a server-side face database.
OrthoFaceCosmetic does not retain face data on an external backend as part of the core workflow.
OrthoFaceCosmetic does not store Apple Face ID templates, Secure Enclave biometric data, or device-unlock biometric data.
Optional Apple Vision Pro stream data is transient and is used only during the active local paired session.
Optional user-generated files may persist only if the user intentionally saves, exports, or shares them. These files may include correction TXT files, reports, images, 3D visualization files, or other educational exports.
If the user exports or shares a file, the exported file remains only where the user saves or shares it. The user controls that destination and may delete the file from the device, storage location, or recipient destination they selected.
If a user contacts us for support and voluntarily sends screenshots, files, exported reports, or other materials, we use those materials only to provide support, troubleshoot issues, or respond to the user’s request. Support materials are not used for advertising or biometric identification.
Users may request deletion of any support material they have voluntarily sent to us by contacting:
Because the app’s core face-mesh processing is local and session-based, there may be no server-stored face data for us to delete unless the user has voluntarily sent us support material or uploaded/sent files outside the core local workflow.
5. USER EXPORTS AND SHARING
OrthoFaceCosmetic may allow the user to export or share educational files.
These may include:
- correction TXT files;
- measurement reports;
- cosmetic colour-plan summaries;
- selected vertex ID lists;
- screenshots or images if the user chooses to create/share them;
- 3D review or visualization files if the user activates export features;
- technical appendix or teaching documents.
Exports are user-initiated.
The app does not automatically export face data.
Exported correction files may include derived face-related information, such as:
- selected review surface names;
- colour roles;
- cosmetic product categories;
- application instructions;
- blend directions;
- expected visual effects;
- what to avoid;
- vertex IDs;
- measurements;
- opacity or intensity settings;
- retained or hidden suggestion states.
The purpose of these exports is educational review, cosmetic communication, technical documentation, or user-controlled sharing.
Users should review exported files before sharing them.
Users should not export or share another person’s face, face measurements, vertex IDs, screenshots, or cosmetic correction plans without that person’s informed permission.
When the user shares an exported file, the file becomes subject to the privacy practices of the destination selected by the user, such as email, messages, cloud storage, AirDrop, or another app.
6. CONTACT
For privacy questions, support requests, data questions, or deletion requests concerning any support material voluntarily sent to us, contact:
Website:
Privacy Policy:
Terms of Use:
www.orthopractis.com/terms-of-use
If you have questions about how OrthoFaceCosmetic uses face data, AR face geometry, Apple Vision Pro local streaming, exports, or retention, please contact us before using those features.
Users may choose not to start live AR capture, not to show vertex IDs, not to start Apple Vision Pro streaming, not to export files, and not to share any correction report.
Use OrthoFaceCosmetic only for educational visualization, reversible cosmetic review, and user-controlled communication. The app is not a medical device, not a diagnosis, not a treatment plan, not an identity-verification tool, not a beauty score, and not a surgical instruction system.
Orthoface Privacy Policy
Effective date: 2026-05-16
Orthoface is an educational facial measurement and visualization app. It uses camera/ARKit/depth data to generate local 3D face mesh measurements, symmetry indicators, Marquardt-style overlay visualization, Golden Dodeca fit, φ-ratio calculations, 2D unwraps, perfect/corrected USDZ previews, and optional export ZIP files.
Orthoface is not a medical device. It does not diagnose, treat, prescribe, or recommend surgery. Beauty and φ scores are mathematical indicators only and include disclaimers.
Orthoface Data, TrueDepth, and ARKit Face Mesh
Orthoface uses the device camera, TrueDepth camera where available, ARKit face tracking, and depth/mesh information to generate a local 3D surface model of the face. This face model may include numbered mesh vertices, face pose information, reference planes, symmetry-pair measurements, distance values, ratio values, mask overlays, 2D unwrap diagrams, and exportable measurement summaries.
Orthoface does not use TrueDepth or ARKit face data to identify, authenticate, verify, or recognize a person. Orthoface does not access or store Face ID biometric templates. Orthoface does not use face data for advertising, tracking, profiling, or marketing.
How Orthoface Uses Face Data
Orthoface uses face mesh and depth information only for educational facial measurement and visualization. The app may use this data to display a live face mesh, vertex IDs, anatomical labels, reference planes, symmetry indicators, Marquardt-style masks, Blue Guide overlays, Golden Dodeca fitting, phi-ratio lines, curve/spline masks, 2D unwrap diagrams, corrected USDZ previews, and local export files.
Orthoface does not diagnose, treat, prescribe, screen for disease, or recommend surgery.Face mesh data is processed locally on device. It is not automatically transmitted to a developer server. The only off-device transfer is user-controlled local-network transfer to the user’s paired Apple Vision Pro after QR pairing, and user-initiated export/share files.
Local Processing and Storage
By default, face mesh data and measurements are processed locally on the device. The developer does not automatically receive, upload, sell, or share face mesh data. Face data used during a live session is processed in memory. Local export files are stored only in the app sandbox or user-selected destination when the user chooses export/share.
Sharing, Export, and Apple Vision Pro Pairing
If the user pairs an iPhone/iPad with Apple Vision Pro, compact measurement packets may be transmitted over the local network between the user’s own paired devices after QR pairing for immersive visualization. This local device-to-device communication is used only to display the selected overlays in Apple Vision Pro.
If the user chooses export or share, Orthoface may create local files such as TXT, JSON, PLY, STL, OBJ, USDZ, SVG, PNG, or ZIP packages. These files may contain facial geometry, vertex IDs, measurement values, and visualization data. Export and sharing occur only when the user intentionally selects an export/share action. The user controls where exported files are saved or sent.
No Third-Party AI, Advertising, or Tracking
Orthoface does not transmit face data to developer-operated cloud storage by default. Orthoface does not include external AI consultation, ChatGPT, OpenAI, GPT, advertising, or third-party tracking functionality. Orthoface does not sell face data and does not use face data for advertising or tracking.
Retention and Deletion
Live face data is processed during the active session. Export files are retained only where the user saves or shares them. Users may delete exported files from their device or chosen storage location. The developer does not retain server-side face data by default because the app does not automatically upload face data to a developer server.
Educational and Non-Medical Disclaimer
Orthoface is an educational facial measurement and visualization app. It is not a medical device. It does not diagnose, treat, prescribe, screen for disease, or recommend surgery. Measurements, symmetry indicators, mask overlays, phi-ratio guides, and the Overall Concordance Score are mathematical visualization indicators only and should not be used as the sole basis for medical, surgical, aesthetic, or personal decisions.
Face Data We Process
OrthofaceCapture uses ARKit and the TrueDepth camera only after user consent to create a live face mesh for local educational measurement and visualization. The app may process ARKit face-geometry vertices, triangle topology, face transforms, QR alignment transforms, fixed anatomical vertex IDs, symmetry/asymmetry values, calculated measurements, overlays, masks, and export files that the user chooses to create. OrthofaceCapture does not record raw camera video for developer collection, does not identify the user, and does not collect Face ID authentication or biometric identity data.
How Face Data Is Used
Face data is used only to provide local live mesh display, measurement calculations, QR alignment, visualization overlays, optional encrypted local-network streaming to the user's own paired Apple Vision Pro, and optional user-initiated export/share files. OrthofaceCapture does not use face data for advertising, tracking, profiling, user identification, or third-party AI processing.
No Third-Party AI Service or Developer Collection
OrthofaceCapture does not send face data to developer servers, cloud processing services, analytics SDKs, advertising SDKs, tracking SDKs, or any third-party AI service. Face data remains on the user's device unless the user explicitly streams it to the user's own paired Apple Vision Pro over encrypted local Multipeer Connectivity or chooses a system export/share action.
Storage and Retention
Live face data is processed in memory during the app session. The developer does not receive or retain face data. User-created exports, screenshots, share packages, or saved files remain on the user's device, in the app temporary directory, Photos, Files, AirDrop destination, or another user-selected destination until the user, destination app, or operating system deletes them.
User-Initiated Export and Sharing
Export and sharing are optional and are started only by the user. The user is responsible for choosing the destination and should share face mesh, image, or measurement files only with consent from the subject.
Data processed locally
The app may process camera frames, ARKit face geometry, depth/mesh data, fixed anatomical vertex IDs, PCA planes, measurements, symmetry scores, ratio results, Marquardt/Golden Dodeca overlays, 2D unwrap previews, and export files. Processing is local by default.
Local network streaming
If the user pairs iPhone with Apple Vision Pro, Orthoface may stream face-mesh measurement packets over the local network for immersive visualization. This is controlled by the user and is intended for the user's own devices.
Exports
When the user presses export/share ZIP, Orthoface creates user-controlled files such as TXT, JSON, PLY, USDZ, USDA, OBJ, STL, SVG, PNG, 2D unwrap images, QR marker, and README. Exported face geometry and measurements can be sensitive. Share only with trusted recipients.
Local measurement workflow
Orthoface does not include an external relay. Measurement and visualization features are local by default unless the user chooses local-network streaming or export/share.
Product improvement
Do not collect product-improvement, analytics, or exported geometry from users unless you add a separate opt-in consent and update this policy before collection.
Orthoface processes camera, ARKit, depth, and local 3D mesh data to generate measurements and visual overlays. Data is processed locally by default. Users may export ZIP reports manually.
Orthoface is not a medical device and does not diagnose, treat, prescribe, or recommend surgery.
Contact and deletion requests
Contact: info@orthopractis.com.
PlaceMesh Privacy Policy
Effective date: May 26, 2026
PlaceMesh and PlaceMesh Viewer are local spatial capture, visualization, USDZ review, mesh export, and Apple Vision Pro companion applications published by Orthopractis. This Privacy Policy explains what the apps process, what the developer does not collect in this build, and how users control sharing.
1. Short privacy summary
PlaceMesh processes camera-backed AR data, spatial tracking data, QR marker observations, point clouds, mesh vertices, vertex colors, local measurements, USDZ assets, and export files on the user's device to provide capture, visualization, alignment, measurement, local peer sharing, and export features. In the current build, the apps do not require a user account, login, advertising identifier, analytics SDK, cloud project, or developer-operated backend.
2. Data processed by the apps
Depending on which features the user chooses, the apps may process the following on device:
-
Camera and AR tracking data for surface capture, raycasting, QR marker recognition, USDZ placement, and visual alignment.
-
visionOS world-sensing data for QR marker alignment, scene reconstruction, and bounded Vision Capture inside immersive space.
-
Vision body-pose/skeleton observations on iPhone/iPad when the user chooses skeleton-guided capture assistance. This is used to guide point collection and is not a medical or biometric identity feature.
-
Point clouds, mesh vertices, mesh triangle indices, vertex colors, local origin markers, ruler measurements, QR transforms, placement transforms, and capture-box settings.
-
Imported and loaded files such as USDZ, USD, USDA, OBJ, PLY, GLB, GLTF, FBX, JSON, CSV, ZIP, images, and generated export packages.
-
Local network session state needed to pair nearby user-controlled devices.
3. What the developer collects
In this build, Orthopractis does not collect camera frames, world-sensing data, location data, contacts, advertising identifiers, analytics events, mesh files, USDZ files, exported files, or peer-transfer contents through a developer-operated server. The developer receives information only when a user intentionally sends it, such as by emailing support at info@orthopractis.com.
4. Device permissions and purpose
The apps request permissions only for app features:
-
Camera / AR access: local surface capture, QR recognition, raycasting, mesh preview, USDZ placement, and skeleton-guided point collection on supported devices.
-
World sensing on Apple Vision Pro: QR alignment, scene reconstruction, and boxed immersive mesh capture.
-
Local network / Bonjour: peer-to-peer transfer between nearby user-controlled devices running PlaceMesh and PlaceMesh Viewer.
-
Photo/file export permissions where applicable: saving or sharing files only when the user selects an export or share action.
-
Motion where applicable: stabilizing immersive placement, capture guidance, and local measurements.
5. User-controlled sharing and export
Data leaves the device only when the user chooses an explicit action such as Export, Share, AirDrop, Save to Files, ShareLink, Send to AR, USDZ to AR, or paired-device transfer. The user controls the destination and is responsible for choosing whether to share generated files or imported assets.
6. Local network sharing
Peer-to-peer sharing uses Apple's local networking frameworks to exchange processed scene data between nearby devices controlled by the user. Typical transferred data may include mesh vertices, vertex colors, triangle lists, point clouds, QR alignment transforms, USDZ file data or references, and placement transforms. Orthopractis does not receive this peer-transfer content.
7. Imported models and third-party content
Users are responsible for the rights, permissions, and content of imported USDZ or other 3D files. PlaceMesh does not grant rights to third-party assets and does not verify whether a user has permission to scan, import, export, or share a particular object, person, space, model, brand asset, or file.
8. Retention and deletion
Files saved by the app remain on the device or in user-selected storage until the user deletes them. Users may delete exports, imported assets, project files, and app data through the app where available, through Files, through device storage settings, or by deleting the app.
9. Children and sensitive spaces
The apps are not directed to children. Users should not scan people, private spaces, confidential sites, copyrighted objects, or sensitive environments unless they have the required permission and a lawful basis to do so.
10. Security
The apps use platform file storage, system permission prompts, local sandboxing, and user-controlled export workflows. No software can guarantee absolute security. Users should avoid exporting or sharing sensitive scans unless they trust the destination.
11. Changes
This policy may be updated as app features evolve. The in-app consent screen and website copy identify the current policy date.
12. Contact
Privacy and support contact: info@orthopractis.com
Privacy URL: https://www.orthopractis.com/privacy
Support URL: https://www.orthopractis.com/placemesh
Terms URL: https://www.orthopractis.com/terms-of-use
PlaceEasy Privacy Policy
Effective date: 2026-05-30
Developer: Orthopractis Contact: info@orthopractis.com Support: info@orthopractis.com Privacy Policy URL: https://www.orthopractis.com/privacy
Summary
PlaceEasy is designed as a local file-import and AR/spatial placement tool for iOS and visionOS. The current build does not include analytics, advertising, user tracking, account registration, cloud sync, server uploads, subscriptions, or third-party SDKs.
All controls, help, privacy text, and terms remain in the normal app window or the transparent iOS AR overlay. The visionOS immersive space contains only RealityKit scene content: imported files plus their Cube A and Sphere B rigs.
Every-load consent before app use
PlaceEasy shows a Privacy Policy and Terms of Use consent dialog every time the app or app window is loaded, before the normal iOS AR or visionOS app content opens. The user must tap Yes — agree and open PlaceEasy for that launch. If the user taps No — decline and close, PlaceEasy keeps the normal app content closed, clears the current acceptance state, and requests the current app/window scene to close.
The app may store a local consent version and acceptance date on the device as a reference record, but this does not bypass the consent dialog on the next launch. Consent is requested again every time the app loads.
Data collection by the app
PlaceEasy does not collect personal data in the current build. Imported 3D files stay local to the device unless you manually share, export, back up, or delete them outside the app through Apple system tools.
If we later add accounts, analytics, crash reporting, cloud storage, support uploads, server-side processing, subscriptions, advertising, or third-party SDKs, we will update this policy, our App Store privacy answers, and the app privacy manifest before release.
Imported files
When you choose USDZ, USD, USDA, USDC, Reality, or FBX files from the system Files picker, PlaceEasy copies valid selected files into the app’s local Documents/ImportedAssets folder.
USDZ, USD, USDA, USDC, and Reality files are used for local AR/spatial display and manipulation. FBX files are copied only as conversion/reference files and are not rendered directly by RealityKit in this build.
The in-app Unload active file control removes the active file from the live AR/immersive scene, but it does not delete the copied local file. The Clean copied files action deletes PlaceEasy local import copies from the app container. You can also delete copied files through the Files app, device storage management, or by deleting the app.
Camera and AR use on iOS
On iOS, PlaceEasy uses the camera only for ARKit tracking and the live AR camera background. Camera frames are processed locally by Apple’s ARKit/RealityKit frameworks for AR placement. PlaceEasy does not store, upload, sell, or analyze camera frames.
World-sensing and spatial placement on visionOS
On visionOS, PlaceEasy uses local spatial/world placement only to position imported files and their cube/sphere handles in the room. The immersive space contains no HUD, ornaments, file picker, popover, sheet, or SwiftUI control surface. File import, workflow, cleanup, help, privacy, terms, and settings remain in the normal PlaceEasy window.
PlaceEasy does not upload world-sensing data, room data, imported files, or placement settings in this build.
Tracking and advertising
PlaceEasy does not track users across apps or websites. PlaceEasy does not use advertising identifiers, third-party advertising SDKs, analytics SDKs, data brokers, or cross-app tracking.
Support communications and Wix website
If you contact us by email or through the Wix support site, we may receive the information you choose to provide, such as your name, email address, device model, app version, message, screenshots, and troubleshooting details. This information is used only to respond to support requests, improve support documentation, and maintain the app.
Do not send confidential, restricted, construction-sensitive, medical, personal, or client-owned files unless you have permission and we have agreed to receive them.
Our Wix website may process visitor information according to Wix’s own privacy practices and any Wix features enabled on the site. Review Wix’s privacy policy and cookie tools when configuring the site.
Children
PlaceEasy is not directed to children. The app does not knowingly collect personal information from children.
Data retention and deletion
Imported files remain in the app’s local Documents storage until you tap Clean copied files, delete them through system file management, or delete the app. Deleting the app removes its local app container from the device. Device backups may include app documents depending on the user’s system backup settings.
Support emails and Wix support messages are retained only as long as reasonably needed to respond, maintain records, protect legal rights, or comply with obligations. You may request deletion of support communications by contacting info@orthopractis.com, subject to legal or security retention needs.
Security
PlaceEasy relies on Apple platform sandboxing and the system document picker for local file access. No storage or processing method can be guaranteed to be perfect, so avoid importing files that you are not permitted to use or store on the device.
International users
If you contact us through the support website or email, your support information may be processed in the country where the developer or website provider operates. Use the app only if you agree to this handling of support communications.
Changes
This policy may be updated when PlaceEasy changes. The updated policy will be posted at https://www.orthopractis.com/privacy. Continued use after an update means the current version of the policy applies to the current app behavior.
Contact
Questions about privacy or support can be sent to info@orthopractis.com.
Privacy Policy VisionMeshCapture
Last updated: 6.5.2026
VisionMeshCapture is a visionOS app for Apple Vision Pro. It allows users to capture selected reconstructed environment mesh, optionally use approved enterprise main-camera access for local color sampling, load 3D models, align point clouds, and export mesh packages.
Data processed by the app
Depending on how the user operates the app, VisionMeshCapture may process the following data locally on the device:
-
world-sensing and scene-reconstruction geometry;
-
selected mesh vertices, faces, normals, classifications, and point-cloud data;
-
optional enterprise main-camera frames for local color sampling when approved access is available;
-
imported 3D files such as USDZ, USD, PLY, GLB, GLTF, FBX, OBJ, MTL, and textures;
-
vertex colors, texture/material summaries, and color analytics;
-
captured and imported model transforms;
-
export files including PLY, USDZ, CSV, JSON, and ZIP packages;
-
local session logs shown in the app UI.
Local processing
VisionMeshCapture is designed to process core capture, color, alignment, and export data locally on device. The app does not require sign-in, an account, or server upload for core functionality.
Generated files remain in the app container unless the user explicitly saves or shares them.
User-controlled export and sharing
When the user prepares an export package, the app may create files such as:
-
captured_environment.ply;
-
captured_environment.usdz;
-
imported USDZ files;
-
captured_vertices.csv;
-
captured_faces.csv;
-
pick/color analytics CSV;
-
import summaries;
-
manifest.json;
-
a ZIP export package.
The user controls whether these files are saved or shared.
Enterprise main-camera access
If approved enterprise main-camera access is available, VisionMeshCapture may use camera frames locally to improve color sampling of selected mesh surfaces. Camera frames are processed locally for the capture/color workflow and are not uploaded by the app.
If enterprise access is unavailable, the app uses a fallback mesh/classification capture path.
No tracking
VisionMeshCapture does not track users across apps or websites.
No advertising
VisionMeshCapture does not include advertising.
No account requirement
VisionMeshCapture does not require a user account or sign-in.
Third-party services
The current app build should not include analytics, advertising, or cloud-upload SDKs. If any third-party services are added later, this Privacy Policy and App Store privacy answers must be updated before distribution.
Sensitive spaces and user responsibility
Spatial mesh data, camera-derived color samples, imported files, and exported packages can reveal private rooms, objects, screens, documents, bystanders, or restricted locations. Users should capture and share only spaces they are authorized to scan and should inspect export files before sharing.
Children
VisionMeshCapture is not designed to knowingly collect personal information from children. Use in schools, training environments, or supervised settings should follow applicable consent and privacy requirements.
Contact
For privacy questions, contact:
Privacy Policy OrthoGaitApp
Privacy Policy for OrthoGait App and OrthoGaitViewer App
Effective date: April 18, 2026
Orthopractis respects user privacy. This Privacy Policy explains how OrthoGaitApp for iPhone and iPad and OrthoGaitViewer for Apple Vision Pro handle information, permissions, local processing, optional paired-device communication, exports, and user controls.
This policy applies to:
- OrthoGait App
- OrthoGaitViewer App
If these apps are updated to add new data flows, cloud services, analytics, advertising, account systems, or other collection features, this policy must be updated before release.
1. Summary
OrthoGait App and OrthoGaitViewer app are designed around on-device processing and user control.
In the core packaged workflow:
- no account sign-in is required
- no advertising is included
- no third-party tracking is used
- no developer-hosted cloud account is required
- exports are created only after explicit user action
- paired-device communication is optional and occurs only over the same local network
2. OrthoGait App
OrthoGaitApp is the iPhone and iPad capture application.
It uses the device camera to estimate gait, posture, and related movement metrics on device. It can show live measurements, support Static Calibration, review session quality, and create exports when the user explicitly chooses to do so.
When the optional paired-device workflow is enabled, OrthoGaitApp can broadcast abstract pose, metric, and shared-marker state packets from the iPhone or iPad to a paired OrthoGaitViewer device on the same local network. In the normal live viewer workflow, images and video are not transmitted to the viewer.
3. OrthoGaitViewer App
OrthoGaitViewer is the native Apple Vision Pro companion application.
It receives abstract posture, joint, gait, quality, and optional supplemental metric packets from OrthoGaitApp over the same local network after user consent. It can display the session in a viewer window and, when enabled, in an immersive environment.
OrthoGaitViewer can also use Apple Vision Pro spatial sensing and printed-marker recognition to help align the mirrored session in the room. This workflow is optional and is used for local alignment and visualization.
In the normal viewer workflow, OrthoGaitViewer is not intended to receive a live image or video feed from OrthoGaitApp.
4. Permissions Used
OrthoGait App
OrthoGaitApp may request:
- Camera access, to perform on-device pose and movement estimation
- Local Network access, to optionally mirror abstract pose and metric packets to the paired OrthoGaitViewer device on the same local network
OrthoGaitViewer App
OrthoGaitViewer may request:
- Local Network access, to receive the paired session stream from OrthoGaitApp
- Spatial or world-sensing related permissions, to support local room alignment and immersive visualization on Apple Vision Pro
If a user does not grant a required permission, related features may be unavailable.
5. Data Handling Approach
On-device processing
The core movement-estimation workflow is designed to run on the user’s device.
Optional local-network pairing
If the user enables the paired workflow, the apps exchange live abstract pose, metric, and marker-state packets over the same local network so the Vision Pro viewer can mirror the current session.
No required account system
The packaged workflow does not require account creation or sign-in for core use.
No advertising or third-party tracking
The packaged workflow is not intended to use advertising SDKs or third-party tracking technologies.
6. What OrthoGait App does not do in the core packaged workflow
In the core packaged workflow, OrthoGaitApp is not intended to:
- require the user to create an account to begin capture
- upload normal live capture sessions to an Orthopractis-operated cloud service
- use third-party advertising identifiers for tracking
- send normal live camera video to OrthoGaitViewer during ordinary paired viewing
7. What OrthoGaitViewer App does not do in the core packaged workflow
In the core packaged workflow, OrthoGaitViewer is not intended to:
- require a user account for core viewing
- use third-party advertising identifiers for tracking
- operate as a public cloud viewer service
- require the transfer of the iPhone or iPad camera feed during ordinary paired viewing
- perform personal identity recognition
8. Exports
Both apps can create local export files only after explicit user action.
OrthoGait App exports
OrthoGait App may create local session exports containing movement-related measurements, summaries, timestamps, and related session information chosen by the user.
OrthoGaitViewer exports
OrthoGaitViewer may create a local export of the recent viewer measurement window after explicit user action.
Exported files are controlled by the user. If the user chooses to save, share, or send an export using Apple platform features or a third-party destination selected by the user, that user action controls where the file goes after export.
9. Retention
Orthopractis does not operate a required user account database for the core packaged workflow described here.
For the core packaged workflow:
- live processing occurs on device
- local paired communication occurs within the user’s local network environment when enabled
- exported files remain where the user saves them, until the user deletes or moves them
If a future version adds remote storage, cloud sync, online collaboration, or account-based history, this policy must be updated.
10. Third Parties
The core packaged workflow is not intended to include third-party advertising or third-party tracking SDKs.
However, the apps run on Apple platforms and may use Apple-provided operating-system functionality such as permissions, local networking frameworks, file storage locations, or the share sheet. Those platform-level services are governed by Apple’s own terms and privacy practices.
11. Security and User Control
The apps are designed to support user control over privacy-sensitive functions by:
- requesting permissions through Apple system dialogs
- keeping core movement processing on device
- making paired-device communication optional
- making export user-initiated
- not requiring account sign-in for the core packaged workflow
Users can manage permissions in device Settings and can stop using optional paired-device features at any time.
12. Intended Use and Important Limitations
OrthoGait App and OrthoGaitViewer App are intended for movement review, biomechanics, wellness, education, training, informational, and research-oriented workflows.
They are not intended to provide diagnosis, emergency triage, or treatment decisions. Measurements and supportive summaries are algorithm-derived estimates and may contain errors or inaccuracies.
13. Children’s Privacy
These apps are not directed to children as a Kids Category product. If you believe personal information has been provided to Orthopractis in a way that conflicts with applicable law, contact the address below.
14. Changes to this Policy
Orthopractis may update this Privacy Policy when the apps, features, or data practices change. The effective date at the top of this page should also be updated.
15. Contact
Orthopractis
Email: info@orthopractis.com
Website: https://www.orthopractis.com
Privacy page: https://www.orthopractis.com/privacy
Privacy Policy – Ergonomics
Last updated: 20/4/2026
Ergonomic ("the App") is developed by Orthopractis. This Privacy Policy explains how the App handles information.
1. Overview
Ergonomic is designed to provide posture awareness and ergonomic assessment using on-device camera processing. The App does not require user accounts and does not collect personal identity information.
2. Camera Usage
The App uses the device camera to:
-
detect body landmarks
-
estimate posture and alignment
-
calculate ergonomic metrics such as eye-to-screen distance and joint angles
Camera data is processed in real time on the device.
The App does not record, store, or transmit raw video or images to external servers.
3. Data Processing
All core processing is performed locally on the device.
When multi-device functionality is used (e.g., spatial visualization):
-
only processed posture data (such as joint positions and orientation values) is transmitted
-
transmission occurs over a local network connection
-
no raw camera data is shared
-
4. Data Collection
The App does not collect personal data such as:
-
name
-
email
-
location
-
identifiers
The App does not create user profiles.
QR Marker Usage
The App may use printed QR markers as spatial references for alignment purposes with apple vision pro. These markers are used only to establish coordinate positioning and do not contain personal data.
No information from QR markers is stored or transmitted externally.
5. Data Storage
The App does not store personal data on external servers.
Any temporary data used for real-time processing remains on the device and is not retained beyond app usage.
6. Third-Party Services
The App does not use third-party analytics, advertising networks, or tracking systems.
7. Data Sharing
No personal data is shared with third parties.
8. Security
The App relies on Apple’s secure system frameworks and on-device processing to protect user data.
9. Children’s Privacy
The App does not knowingly collect personal information from children.
10. Intended Use
The App is intended for:
-
posture awareness
-
ergonomic self-assessment
-
education and visualization
The App is not intended for medical diagnosis, treatment, or clinical decision-making.
11. Changes
This Privacy Policy may be updated. Changes will be reflected on this page.
12. CONTACT
Support:info@orthopractis.com
Website: https://www.orthopractis.com
Ergonomic & ErgonomicViewer_visionOS
Last Updated: April 2026
1. Overview
Ergonomic and ErgonomicViewer_visionOS (collectively, “the App”) are designed with privacy as a core principle. The App enables real-time posture visualization using on-device processing and spatial computing technologies, including Apple Vision Pro.
We are committed to ensuring that your data remains secure, private, and under your control.
2. Data Collection
The App does not collect personal data in the traditional sense.
During use, the App processes:
-
Body landmark positions (e.g., joint coordinates)
-
Posture-related measurements (e.g., angles, distances)
-
Device spatial positioning (for alignment in immersive space)
These data are used solely for real-time posture visualization and analysis.ll posture processing occurs locally on device. Only abstracted posture data are transmitted over a local network. No images, video, or personal data are collected, stored, or shared
3. Camera Usage
The App uses the device camera to detect body landmarks and estimate posture.
-
No photos or videos are recorded
-
No images are stored
-
No camera data is transmitted externally
Camera data is processed locally and temporarily on your device.
4. Data Processing
All processing is performed on-device:
-
Posture detection and analysis occur on iPhone or iPad
-
Spatial visualization occurs on Apple Vision Pro
-
No cloud processing is used
This ensures maximum privacy and minimal data exposure.
5. Data Transmission (Local Network Only)
When using Ergonomic with ErgonomicViewer_visionOS:
-
Devices communicate over a local network connection (Wi-Fi or peer-to-peer)
-
Only processed posture data are transmitted (e.g., joint positions and orientations)
-
No images, video, or raw camera data are transmitted.all posture processing occurs locally on device. Only abstracted posture data are transmitted over a local network. No images, video, or personal data are collected, stored, or shared
This communication is used exclusively for real-time visualization.
6. No Personal Identification
The App does not:
-
Perform facial recognition
-
Identify users
-
Track identity across sessions
-
Collect biometric identifiers
All posture data are anonymous and non-identifiable.
7. Data Storage
By default:
-
No data are stored
-
No session data are retained
If optional features enable saving data:
-
Storage remains local to the device
-
Users have full control over saved content
8. No Third-Party Sharing
We do not:
-
Share data with third parties
-
Sell user data
-
Use analytics services that collect personal information
No data leave your device.
9. Network Scope
The App operates under a local-only communication model:
-
No external servers
-
No cloud infrastructure
-
No remote data transmission
All device communication occurs within the user’s local environment.
10. Data Minimization
The App follows a strict data minimization principle:
Only the minimum required data for posture visualization are processed and transmitted.
This ensures:
-
Efficient performance
-
Reduced data exposure
-
Enhanced privacy protection
11. Security
We implement safeguards to protect data integrity:
-
Local processing reduces exposure risk
-
No persistent transmission channels
-
Temporary in-memory data handling
Users maintain full control over their environment and data.
12. Intended Use
The App is intended for:
-
Posture awareness
-
Educational use
-
Ergonomic observation
It is not intended for medical diagnosis or treatment.
13. Children’s Privacy
The App does not knowingly collect personal data from children.
Since no personal data are collected or stored, risks are minimized.
14. User Control
Users can:
-
Start or stop posture capture at any time
-
Disconnect devices
-
Control any optional data storage features
15. Changes to This Policy
We may update this Privacy Policy periodically.
Updates will be reflected with a revised “Last Updated” date.
16. Contact
For questions or support:
🌐 Orthopractis.com
ORTHOHAND MOTION – PRIVACY POLICY
Effective date: 2026-03-30
OrthoHand Motion processes motion session data for visualization, wellness tracking, education, and research workflows. The app is not intended to diagnose, treat, cure, or prevent disease.
1. DATA PROCESSED
The app may process motion session data such as timestamps, tracked joint positions, orientations, derived metrics, device metadata, calibration state, app version, and consent choices.
2. ON-DEVICE BY DEFAULT
Motion session data is processed and stored locally on device by default. Optional exports are created only when initiated by the user.
3. RESEARCH MODE
Research Mode may create structured CSV and JSON exports and stage anonymized local contribution folders. In this build, cloud upload is disabled by default and any future upload flow must be explicitly enabled by the user.
4. OPTIONAL AI FEATURES
If AI-generated summaries are added in a future build, selected session summary data may be transmitted to a third-party AI service only after explicit user consent.
5. DATA NOT COLLECTED IN THIS BUILD
This build does not intentionally collect name, email, Apple ID, face imagery, raw camera video, voice audio, diagnosis, treatment recommendation, or advertising identifiers as part of Research Mode staging.
6. RETENTION
Local files remain on device until deleted by the user or removed when the app is uninstalled.
7. EXPORTS
Exported files are controlled by the active subscription tier and by user action. Users are responsible for handling exported files in accordance with their own privacy, ethics, and legal obligations.
8. CONTACT
Support:info@orthopractis.com
Website: https://www.orthopractis.com

