Aevi Form

Aevi Capture Privacy Policy

Effective date: September 7, 2026

Aevi Capture is an on-device 3D capture application developed by Dmitry Sergeenko under the Aevi Form name. This policy explains what information the app handles and how it is stored.

Summary

Aevi Capture does not require an account and does not send capture data, 3D models, usage analytics, advertising identifiers, or diagnostics to an Aevi server. Capture and 3D reconstruction run on the device using Apple frameworks.

Information handled by the app

Aevi Capture handles the following information only to provide its features:

The current version does not include an Aevi account, cloud upload, advertising, cross-app tracking, or third-party analytics SDK.

Camera and LiDAR access

Aevi Capture requests camera access only when the user starts a scan. Apple Object Capture and Photogrammetry frameworks use camera and LiDAR input to guide capture and reconstruct the object on the device. Camera access can be changed at any time in the device's Settings app.

Storage and retention

Capture images and checkpoints are stored in the app's private container while a scan is active. After Aevi Capture successfully validates and saves the completed USDZ model, it removes that scan's source images and checkpoints.

If capture is interrupted, its source material remains available for recovery for up to seven days unless the user deletes it sooner. Completed models remain in the Library until the user deletes them or removes the app. Deleting a model removes its USDZ file, thumbnail, and collection memberships. If a file cannot be removed immediately, Aevi Capture records the cleanup and retries it later.

Source images, checkpoints, and thumbnails are excluded from device backup. Completed USDZ models and Library metadata may be included in the user's encrypted device backup, depending on the user's device and backup settings. These backups are provided by Apple and are not received or controlled by Aevi.

Sharing

Aevi Capture shares a model only when the user chooses Share and selects a destination in Apple's system Share Sheet. The selected destination may process the file under its own terms and privacy policy. Aevi does not receive a copy of the shared model.

Data collection and tracking

Aevi Capture does not collect data from the app for the developer, does not track users, and does not sell personal information. The app's privacy manifest declares no collected data and no tracking. It declares the required-reason APIs used for local file timestamps and local preferences.

User choices and deletion

Users can:

Because the current version has no Aevi account or server-side storage, there is no server-side user record to access or delete.

Children's privacy

Aevi Capture does not knowingly collect personal information from children or from any other user.

Security

Sensitive files in the app container use iOS data protection. No method of storage is guaranteed to be completely secure, but Aevi limits the information handled by keeping the capture and reconstruction workflow on the device.

Changes to this policy

This policy may be updated when Aevi Capture's features or data practices change. The published page will show the effective date of the current version.

Contact and support correspondence

Developer: Dmitry Sergeenko, Aevi Form. Email: founder@aeviform.com. Support: aeviform.com/support/aevi-capture.

If you choose to email support, we receive your email address and the information you include so we can respond. Support email is handled through Google Workspace. This is separate from the app's local capture workflow; the app does not automatically send support messages or attachments. Do not send photos or models unless needed and you choose to share them. You can contact us to request deletion of support correspondence, subject to any applicable retention obligations.

This policy covers Aevi Capture 1.0. Future Aevi Studio accounts and cloud uploads will have separate disclosures. Visiting this website may involve technical request information handled by its hosting provider; this is separate from data handled locally by Aevi Capture.