Aevi Studio Privacy Notice

Effective: November 6, 2026. This notice covers Aevi Studio at studio.aeviform.com, including beta access requests, business Workspaces and public product experiences. It is separate from the Aevi Capture Privacy Policy, which describes Capture's on-device workflow.

Who is responsible

Aevi Studio is operated by Dmitry Sergeenko, under the Aevi Form name. Contact founder@aeviform.com for privacy, access or deletion requests.

We are responsible for account administration, beta requests, service security and our support correspondence. A business publishing a Product decides what it uploads and makes available to its customers. That business is responsible for its content, permissions and its own privacy notices. If your intended use requires a separate data processing agreement, contact us before uploading personal data for that use.

Information we handle

• Beta requests: your email, company, description of products, intended placement and optional website. We use these to assess the request, communicate about access and prevent duplicate or abusive submissions.
• Accounts and Workspaces: email, a protected password hash, authentication and recovery records, Workspace settings and account status. We do not need or ask you to send your password by email.
• Products and files: product names and presentation settings, uploaded 3D models, converted Web files, thumbnails, versions, processing and upload history, public links and access settings. Models and descriptions may contain personal information if you include it.
• Service activity: upload/processing errors, request identifiers, status and timing information, resource use, access changes, deletion records and security information. Hosting and network providers also process connection information, such as IP addresses, to deliver and protect the service. Rate limiting uses connection and account information.
• Product viewing: events such as a Viewer opening, a model loading or an AR button being clicked, with the Product, representation version, broad source category and time. These are event counts, not a count of identified people, confirmed native AR sessions or sales. The application event record does not include a viewer's name, email or IP address.
• Support and feedback: messages you send us and optional account-deletion feedback. Feedback is stored separately without an account/email link; free text can still identify you, so leave out sensitive information.

Why we use information

We use information to review access requests, provide accounts, store and process models, deliver the public experiences you enable, respond to support, understand product use and keep the service secure and recoverable. Required account and file information is necessary to provide the requested service; a beta request does not create an account automatically. Optional website details and feedback are not required.

Where data protection law requires a legal basis, we rely on taking steps at your request and performing our service agreement for account and model services; our legitimate interests in operating a reliable service, preventing abuse, measuring basic product use and responding to business enquiries; consent for optional analytics cookies; and legal obligations where applicable. You may object to processing based on legitimate interests. We do not sell personal information, use Studio model uploads to train AI models, or use them for targeted advertising.

Public products and your choices

Studio is a cloud service. Uploading is not a private-draft workflow. A supported Product can become accessible by its public link once processing succeeds. A person with an enabled link can view or download the representations available through it. A link can be reshared or discovered on a website where you place it. Upload only material you are entitled and prepared to share this way.

Viewer, permanent links, QR codes, embeds and AR are separate ways of using a Product. Replacing a model preserves its public identity; the previous complete version remains available until the replacement is ready. Disabling access or deleting a Product closes future access through Studio, but cannot recall files another person already downloaded or copied. A business embedding Studio remains responsible for its own website's practices.

Cookies and browser storage

Studio uses an essential sign-in cookie and browser storage for features such as upload recovery and interface preferences. The current sign-in policy allows up to seven days without qualifying activity and a maximum of thirty days before signing in again; access can end earlier after logout, revocation or an account change. These features are separate from advertising cookies.

The public Aevi Form website has optional Google Analytics with an Accept/Decline choice and an Analytics preferences control. See Website privacy for that processing. Public product event counts described above do not require a cross-site advertising identifier. Your browser may also send connection information to Apple or Google if you choose a native AR experience, or to another website when you follow its link; their own notices apply.

Service providers and international processing

We use Railway for hosting, databases, model processing and primary file storage; Backblaze B2 for encrypted recovery copies; and Resend for transactional service emails. Support email is handled in Google Workspace. GitHub Actions, UptimeRobot and Healthchecks.io support operational checks and alerts. These monitoring services are not given the backup decryption key; monitoring is not a public model catalogue.

Our current application hosting and backup infrastructure is in the United States; providers may also process data in other countries. This means data may be processed outside your country, including outside the EEA or UK. We use providers' applicable data processing terms and transfer safeguards, including Standard Contractual Clauses where applicable. You can contact us for information about relevant safeguards. Their terms describe their own processing: Railway, Backblaze, Resend and Google Workspace.

Access by the operator and service providers is limited to operating, supporting and protecting the service. Information may also be disclosed when required by law or necessary to protect legal rights or investigate abuse. Public Product representations are disclosed to the people who request them while you enable access.

How long information is kept

• Access requests: scheduled for deletion once older than 180 days. Related email correspondence is handled as support correspondence below; creating an account starts a separate account record.
• Accounts, Products and models: kept while needed to provide your active account and Products. Product/account deletion closes access and starts background cleanup. Account deletion removes active sign-in sessions and recovery tokens and replaces the active email/password record. File cleanup can take additional time and is retried if a dependency is unavailable.
• Product event records: scheduled for cleanup after 30 days. Daily aggregate metrics are scheduled for cleanup after 400 days, or after Product/Workspace deletion. Cleanup runs in batches, so these are retention thresholds rather than promises of deletion at an exact second.
• Application diagnostics: scheduled for cleanup after 90 days without a new occurrence. Other limited security, traffic, delivery and deletion records do not all share an automatic age cutoff. We retain them for service integrity, preventing deleted or revoked access from reappearing, troubleshooting and resolving security or legal issues; contact us to request review or deletion of identifiable information that is no longer needed.
• Support and optional feedback: kept while a request or follow-up remains relevant, or where needed to document a service decision, resolve a dispute or investigate a security issue. We review the need when handling the request or a deletion request, and remove or de-identify information no longer needed. There is no universal automatic deletion period for support mail or free-text feedback.
• Recovery copies: encrypted backups follow a seven-day daily and thirty-day weekly recovery policy. Backup removal follows the retention/cleanup cycle and storage protection rules, so live deletion does not immediately erase an existing backup. Backups are restricted to recovery and integrity checks; recovery must reapply current deletions and revocations. Provider delivery and security records may follow the provider's own retention rules.

Your rights and contact

Depending on applicable law, you may request access, correction, deletion, a portable copy, restriction, or object to certain processing. If we rely on consent, you may withdraw it; this does not affect earlier lawful processing. Use the account/Product deletion controls or contact founder@aeviform.com. We may verify your identity and ask for information needed to locate the relevant account or Product without exposing another Workspace's data. We respond within the period required by applicable law. You may also complain to your local data protection authority.

For a question about a business's Product content, contact that business or send us the public Product URL. Do not send passwords or private models unless we arrange an appropriate support channel. Studio is intended for adult business users, not for children. It does not make solely automated decisions about people with legal or similarly significant effects; model validation and processing decide whether a technical file can be served.

Security and updates

We use access controls, HTTPS, protected credentials and encrypted recovery copies. No online service can promise absolute security. Do not upload sensitive personal information or material requiring a confidentiality guarantee during this beta.

We will update this notice when practices change and identify the effective date. Material changes affecting participants will be brought to their attention through an appropriate service communication. See the Private Beta Notice and Studio Support.