Rendition

Legal

Privacy Policy

Effective July 15, 2026

Rendition is built for commercial property scans and public walkthroughs. Do not use Rendition for content that must remain confidential or private.

1. Scope

This Privacy Policy explains how Rendition collects, uses, discloses, stores, and otherwise processes information when you use the Rendition website, the Rendition capture app, hosted 3D tours and viewers, and related services.

Rendition is a commercial property capture and processing service. It is not designed for confidential, private, regulated, classified, sensitive, medical, financial, biometric, child-directed, or restricted-location scans.

2. Property scans are public by design

Do not scan or upload any space, object, person, document, screen, artwork, security device, credential, private residence area, personal item, trade secret, or other material unless you have all rights and permissions needed for public processing and public display.

Unless Rendition separately agrees in a signed written contract, scans, images, keyframes, generated previews, walkthroughs, floor plan drafts, derived models, metadata, and hosted outputs are treated as public or commercially shareable content. They may be accessible through shareable links, embedded viewers, previews, caches, or backups.

Deletion, unpublishing, access changes, or account cancellation may not remove copies already processed, cached, distributed, backed up, downloaded, shared, indexed, trained on, or incorporated into derived outputs.

3. Shared tour links, buyer leads, and analytics

A published tour has two link variants. The branded link shows the agent's or company's branding and a "Contact agent" lead form. The MLS-safe (unbranded) link strips branding and never shows a lead form — it exists so the tour can be embedded on the MLS or a portal without a competing call to action.

If a visitor voluntarily submits the "Contact agent" form on a branded tour, we collect the name, email address, optional phone number, and optional message they enter, and forward that lead to the listing's agent by email so they can respond directly. This form only appears on branded links; it never appears on MLS-safe links.

Separately, we record aggregate, non-identifying analytics for published tours: view counts (branded vs. MLS-safe), device type, time spent, engagement, referring domain, and per-room dwell time. This analytics pipeline does not store IP addresses, cookies, or any per-visitor identity, and known bot and crawler traffic is filtered out before it is counted. A named, contactable lead is only ever created when a visitor affirmatively submits the contact form described above.

4. Information we collect

Account information, including name, email address, and authentication identifiers (managed through Firebase Authentication), organization and company details, workspace membership, and account settings.

Capture content, including property photos and video frames, camera pose and spatial/sensor data captured during a phone walkthrough (such as device orientation and, where available, depth data), property name and address, timestamps, and other capture metadata submitted through the capture app.

Generated outputs, including floor plans, photo stills, 360° views, 3D walkthrough tours, thumbnails, and measurements derived from your capture content.

Buyer lead data and tour analytics, as described in Section 3 above.

Usage and device data, including app events, diagnostics, crash logs, IP address, browser and device identifiers, operating system, device model, approximate location, referral data, pages viewed, and upload/processing status.

Subscription data. Rendition does not process card payments directly and stores no card numbers. Subscriptions are purchased through the Apple App Store or Google Play; Apple or Google handle your payment details under their own privacy policies, and Rendition receives only a purchase or subscription status token used to verify and apply your entitlement (for example, how many active spaces your plan allows).

5. How we use information

To provide, operate, secure, support, bill, and improve Rendition.

To process captures, generate property walkthroughs and spatial outputs, host and publish results, recover interrupted uploads, detect errors, verify quality, and maintain processing queues.

To deliver buyer leads to the listing's agent and send related notifications (invitations, tour-ready notices, new-lead alerts, and weekly usage digests) by email.

To train, evaluate, fine-tune, benchmark, validate, and improve computer vision, reconstruction, mapping, compression, quality scoring, moderation, search, and AI systems.

To create and use derived, aggregated, de-identified, statistical, or analytical information for any lawful business purpose.

To enforce terms, prevent abuse, protect safety and security, investigate fraud, comply with law, and defend legal claims.

To communicate about accounts, transactions, product updates, security notices, support issues, and commercial opportunities.

6. Distributed and international processing

Captures are processed by a distributed worker fleet operated by or for Stratis (Rendition is powered by Stratis; see stratis.ai). Hosted tours, accounts, and stored data run on Google Cloud and Firebase infrastructure. Transactional email is sent through a third-party email delivery provider. Those systems and operators may be located in any country or region.

By using Rendition, you authorize transfer, storage, access, replication, processing, caching, backup, and technical review of content and metadata in the United States and any other location where Rendition, its hosting providers, or Stratis-operated processing nodes operate.

You are responsible for determining whether your scans may lawfully be transferred, processed, published, displayed, trained on, or stored in those locations.

7. How we disclose information

We may disclose information to hosting providers, distributed processing providers (Stratis), authentication providers, app-store payment platforms (Apple, Google), email delivery providers, customer support providers, security providers, and professional advisors.

We may disclose scans and generated outputs to workspace members, link recipients and viewers of a published tour, and — for buyer leads — the listing's agent, as described in Section 3.

We may disclose information if required by law, legal process, government request, safety need, rights enforcement, business transfer, merger, acquisition, financing, reorganization, bankruptcy, or sale of assets.

We may publish or disclose aggregated, de-identified, benchmark, statistical, or derived information without restriction, subject to applicable law.

8. Retention

We retain information for as long as needed to operate Rendition, provide services, preserve scan outputs, maintain records, resolve disputes, enforce agreements, comply with law, improve models, and support backups and disaster recovery.

Capture content and derived outputs may be retained indefinitely unless Rendition agrees otherwise in writing or applicable law requires deletion. Some copies may remain in backups, logs, caches, public links, distributed systems, trained models, or derived datasets after deletion from primary product views. Public tour links are shareable and may be cached by browsers, search engines, or third-party services outside Rendition's control.

9. Your responsibilities

You must provide all required notices, consents, permissions, releases, and authorizations before scanning or uploading a property or any content involving people, personal property, private spaces, regulated locations, copyrighted works, tenants, guests, employees, customers, or third-party rights.

You must not use Rendition to upload sensitive personal information, secrets, access credentials, documents, personal records, nonpublic business data, restricted facilities, illegal content, or content you are not permitted to publish and process.

10. Privacy rights

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of certain personal information. You may also have rights to appeal a decision or opt out of certain processing where required by law.

Some requests may be limited by legal exceptions, public content status, business records, security needs, distributed processing, backups, trained models, derived data, or other users' rights.

To make a privacy request, contact support@stratis.ai. We may need to verify your identity and authority before acting on a request.

11. Children

Rendition is not directed to children and may not be used by anyone under 18. Do not scan children or child-focused spaces unless you have all required legal authority, notices, permissions, and releases.

12. Security

We use technical and organizational safeguards designed to protect information, but no service is perfectly secure. Public or shared scan outputs should be treated as public, not confidential.

13. Changes

We may update this Privacy Policy from time to time. Updates are effective when posted unless a later date is stated. Continued use of Rendition after an update means you accept the updated policy.

Questions: support@stratis.ai. These terms work together with the Terms of Service.