Privacy, in plain language.

Updated October 29, 2026. TourScape is operated by Scott Corlett.

Information you choose to provide

A project request may include your name, business email, company, role, property address, production preferences, and a message. The private project studio also stores the media, rights notes, and property details you submit. Please do not upload financial records, identity documents, access codes, or other information unrelated to property marketing.

How it is used

We use this information to save your project settings, queue your selected production, and deliver your films. Submitting a brief does not authorize a charge or subscribe you to a marketing mailing list. TourScape sends transactional notices when generated scenes are ready to review and when final films are ready. Resend delivers these notices using your project email address. You can turn production emails off in your studio; these notices do not subscribe you to marketing email. Email sign-in, when available, sends the verification messages needed to access your account.

Private studio and hosting

Existing studio accounts use Sign in with ChatGPT for account identification. Where email sign-in is offered, Clerk verifies your email and manages your sign-in session. TourScape uses your verified email and account identifier to associate records and invitations with you. Email accounts have a separate workspace from existing ChatGPT accounts; we do not merge projects based only on an email address. Sign-in verification messages are transactional, not marketing subscriptions. Project media is stored privately and is accessible to your signed-in account and the authorized TourScape operator. The public website and data storage use OpenAI Sites hosting and its infrastructure providers.

Publication and production

Uploading media does not make it publicly visible. Starting a cinematic collection authorizes TourScape to send your selected photographs, uploaded footage, logo, floor plan and production settings to Modal. Modal runs camera generation, production coordination and final-film assembly. It uses private temporary working files; source uploads and delivered films are stored in your private TourScape studio. Older original-media editing may still run on the TourScape production computer. If you choose the cinematic satellite arrival, the confirmed map coordinates are sent to the public USGS imagery service. Map tiles are cached by the rendering worker. The opening uses historical imagery whose age and detail vary. Cinematic logo, plan and soundtrack assembly run in the cloud. Cinematic collections are available through paid checkout. For standard original-media orders, the renderer removes working files and cached scenes after seven days; cinematic media is retained for review until deleted. Cloud cinematic working files are removed after seven days; persistent spending records are retained to prevent duplicate generation. Source uploads and delivered films remain in your private studio until deleted. Original-media orders do not use a third-party AI generator. Cinematic processing uses Modal as identified in the production consent; do not include sensitive information in scene photographs. You decide whether to download and publish your films. Creating a share link makes the selected film, supplied floor plan, and details you approve available to anyone with the link, without sign-in. Contact details and the logo are shown on branded pages only. Stop sharing disables the link and media access, but cannot recall copies already downloaded. Production updates are saved in your studio.

Property galleries and buyer inquiries

You can explicitly select property photos and MP4 clips for your public gallery. Unselected uploads remain private. Selected files, including original credits and clip audio, can be viewed and saved by anyone with the shared link. If you send a showing request or question, your name, email, optional phone, preferred times and message are stored in the listing representative’s private TourScape inbox. Your submission is not a confirmed appointment or a marketing subscription. The representative can delete inquiries; you can also request deletion using the contact below. Inbox replies open the representative’s email app. If available and enabled by the account owner, an email service sends an alert with a secure inbox link but no inquiry details; an alert already being sent may still arrive after alerts are turned off. The account owner and authorized workspace members with access to the project may view and manage these inquiries. Social campaign drafts are private saved plans and do not publish or schedule posts. No main social-platform passwords are collected.

Social account connections and scheduled posts

If you connect a social account for automatic publishing, Zernio handles the platform authorization. TourScape stores your customer profile identifier, account names and identifiers, and delivery records. When you approve a campaign, we send Zernio the selected video, captions, platform settings and schedule. A temporary, unguessable media link lets the publishing service fetch that video. It expires seven days after its scheduled delivery and stops serving if you cancel the post or disable the property page. The provider and destination platform may retain copies they have already downloaded under their own policies.

Connecting an account alone does not publish content. You must approve a posting plan. Scheduled posts retain the content you approved even if you later edit the draft. Cancel them in the delivery queue before replacing them. Disconnecting an account applies across your TourScape properties and requires cancelling its upcoming deliveries first; it does not delete already published posts. For Bluesky, you may choose to submit a dedicated app password to establish your connection. It is sent securely to Zernio; TourScape does not save it. Telegram uses a temporary connection code that you send to the provider’s bot in a private chat. Slack connects the channel you choose through its authorization screen; its scheduled posts contain your caption and property link rather than an uploaded film. Our earlier Meta-only connection stores encrypted access credentials where it was used. Manage access or request deletion.

Calling Sophie

If you call our sales number, Sophie identifies herself as TourScape’s AI assistant. Retell AI and its telephone and AI service providers process your voice and responses to answer questions and guide you to our website. We configure this agent to retain basic call attributes only, rather than stored audio recordings or transcripts. Basic metadata, such as the calling number, call time, duration and call status, may be retained for service operation and billing. Please do not share card details, passwords, sign-in codes or sensitive personal information during a call. Purchases take place through our website’s secure checkout. Calling does not subscribe you to marketing or authorize outbound calls. For human assistance or a privacy request, email hello@gettourscape.com.

Cookies and technical information

Sign-in may use cookies required by the authentication service. A short-lived secure cookie binds a Meta connection request to your browser. We do not add advertising trackers. The hosting platform may process technical logs for delivery and security. Request controls may temporarily store a hashed network identifier to limit abuse.

Public website analytics

TourScape measures public page views, estimated visitors, visits and traffic sources for up to 90 days. Visitor and source measurement began October 28, 2026; earlier page views cannot be converted into visitor counts. These are estimates of browsers, not exact counts of people. Different devices, cleared storage and browser privacy settings affect the totals.

For these first-party measurements, we keep random visitor and visit identifiers in your browser’s local storage, rather than analytics cookies. The visitor identifier expires after 90 days; a visit ends after 30 minutes of inactivity. Our analytics database stores only SHA-256 hashes of these identifiers, never the original identifiers. We do not connect them to your sign-in account, customer records, property details or personal contacts.

Traffic-source and medium labels come from recognized campaign tags and the referring website’s hostname. If a landing link to a public page, sign-in or the studio entry pages contains UTM source, medium, campaign, term or content tags, or Google or Facebook click identifiers, we keep eligible compact tags in this browser for up to 30 days so they can follow you through sign-in to checkout. At checkout those tags are sent to Stripe as checkout metadata and, for subscriptions, subscription metadata. Please do not put names, emails, phone numbers, addresses or other personal information in campaign tags. Values are limited in length and characters; invalid values are discarded. For up to 90 days, the visit analytics database stores only whether each accepted UTM field was present, together with the separately grouped source and medium; it does not store the campaign, term or content values, click identifiers or full URLs. Confirmed paid orders store a grouped source and medium for aggregate gross sales reports; orders without eligible tags are unattributed. Stripe retains checkout metadata under its own policies. When browser storage is blocked, public page views may still be counted, but visitor, source and checkout attribution are unavailable. Do Not Track, Global Privacy Control and the opt-out below disable analytics and new attribution. Turning analytics off clears stored campaign tags in this browser but does not erase information already sent to Stripe. Abuse controls may retain a temporary hourly hashed network identifier, as described above.

Separately, verified sign-up dates and sign-in provider types are kept in private operational records. When a registration date is unavailable, we record a first observed sign-in separately from a new registration. Our servers also record Stripe-confirmed paid orders, subscription renewals and refund or dispute holds. Aggregate revenue by source uses campaign metadata on the confirmed payment or subscription; it is not linked to the anonymous browser identifiers used for traffic measurement.

An owner-only dashboard and a read-only report protected by a dedicated secret key let our authorized marketing reporting bot review aggregate website traffic, sign-ups, paid orders, renewals, checkout and collection-start counts. These reports expose no individual visitor identifiers or customer records. Visit counts and grouped revenue remain in TourScape’s hosting database; eligible checkout attribution is also shared with Stripe as described above.

Updates and deletion requests

You may ask to correct or delete a brief or uploaded media by emailing hello@gettourscape.com. Include the request reference and use the email associated with the project. We may need to verify the request before releasing or deleting private information.