Privacy Policy

Last updated: 7 October 2026

This Privacy Policy explains how REMARSO LLC, a New Mexico limited liability company, operating VirtualTourEasy ("VTE", "we", "us", "our"), collects, uses, stores, shares, and protects personal information through virtualtoureasy.com, our dashboard and tour builder, and the tours we host.

For details about connected accounts, see Google integrations and Facebook Login. To remove your information, see our data deletion instructions.

1. Information We Collect

Account Information

When you create an account, we collect:

Tour Content

Content you upload or create on the platform, including:

Lead Capture Data

If you use our lead capture forms within tours, we collect information submitted by your tour viewers, such as name, email, phone number, and messages. You are the data controller for leads collected through your tours.

Analytics Data

We automatically collect analytics on tour views, including:

Payment Information

Payment processing is handled entirely by Stripe. We do not store your full credit card number, CVV, or other sensitive payment details on our servers. We receive and store only a reference to your Stripe customer ID and subscription status.

Usage Data

We collect feature usage, page visits, signup events, referral and campaign information, device and browser information, and error and diagnostic logs to operate and improve the Service and measure how users find it. Product analytics can associate activity with your VTE user and organization identifiers, role, plan, and email domain. When session recording is enabled, we collect interaction recordings with configured masking of text and inputs.

2. How We Use Your Information

3. Third-Party Services

We share data with the following third-party providers as necessary to operate the Service:

Stripe

Processes payments and manages subscriptions. Stripe receives your payment details directly. See Stripe's Privacy Policy.

Cloudflare

Cloudflare provides hosting, CDN, security, database, file storage, and key-value storage. This includes hosting account information obtained through Google and Facebook, uploaded content, Street View publication records, and Street View authorization credentials. See Cloudflare's Privacy Policy.

AI processing providers

Power our AI media features. When you use AI tools (photo enhancement, 360° generation, scene generation, outpainting, text-to-360°, video, narration), the media and text you supply are sent to specialist third-party AI providers for processing under contract with us. They may process your content only to return a result to us, and are not permitted to use it to train their own models. A current list of our AI sub-processors is available to customers on request — contact support@virtualtoureasy.com.

Resend

Handles transactional email delivery (account verification, password resets, notifications). Your email address is shared with Resend for this purpose. See Resend's Privacy Policy.

Analytics and diagnostics

We use Google Tag Manager to deliver measurement tags and measure signup conversions through Google Analytics and Google Ads. Where enabled, PostHog processes product usage and interaction data, and Sentry processes error and performance diagnostics. These providers may receive device, browser, network, page, and event information. Product analytics also receives VTE identifiers and account attributes described above. Tour owners can configure their own analytics or tracking integrations; those owners are responsible for explaining their use to tour viewers. See Google's Privacy Policy, PostHog's Privacy Policy, and Sentry's Privacy Policy.

Google integrations and Google user data

Google Sign-In: If you choose Google Sign-In, we request the openid, email, and profile permissions. We receive your Google account identifier, email address, email-verification status, name, and profile picture. We store the account identifier, email, name, and profile picture and use the verification result to create or link your VTE account, authenticate you, and display your profile. The Google access token used to retrieve your sign-in profile is not stored as a continuing Google connection. Our own session credentials keep you signed in to VTE.

Optional Google Street View connection: Separately from signing in, you can connect a Google account in Settings → Integrations. We request email access and the https://www.googleapis.com/auth/streetviewpublish permission to upload and manage Street View photos. We receive and store the connected account's email address, access token, refresh token, and token expiry. The connection belongs to your VTE organization and supports publishing actions by users with access to that organization's tours.

When you choose to publish a scene, we send its panorama image, latitude and longitude, heading, and publication metadata to Google. We retrieve photo identifiers, Maps links, processing status, and errors to show the result in VTE. We store these publication records and use the connection to check status and remove a photo when you request removal. The refresh token lets us maintain this connection without asking you to sign in to Google for each action.

Public content: Photos accepted for publication can be visible to the public on Google Maps and Street View, with their location and Google contributor attribution. Google processes that published content under its own terms and privacy policy. Disconnecting VTE or deleting a VTE tour or account does not itself remove previously published Google Maps photos.

Sharing and permitted use: We use Google user data to provide and improve the account and publishing features described here, including related support, security, and product diagnostics. Cloudflare hosts it; our email delivery provider receives your account email for service communications, and analytics providers receive the limited account attributes described above. Google receives the content you choose to publish. We may disclose data when necessary for security or to comply with applicable law. We do not sell Google user data, use it for personalized advertising or retargeting, or use it to train generalized AI or machine-learning models. Google connection credentials are not sent to our AI media providers. Human access to Google user data is limited to support with your agreement, necessary security investigation, or legal obligations.

VirtualTourEasy's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements where applicable. These integrations do not request access to Gmail messages, Google Drive files, contacts, or calendars.

Disconnecting and revoking access: Use Settings → Integrations to disconnect Street View and remove the stored connection credentials and connected email label. You can also remove VTE's authorization in your Google Account connections. Removing authorization prevents future authorized access but does not itself delete account information or publication records already held by VTE. Use the deletion process below to request their removal. Remove published Street View photos through VTE while still connected, or manage them through Google Maps.

Facebook Login

If you choose Facebook Login, we request public_profile and email. We receive and store your app-scoped Facebook user identifier, first and last name, profile picture URL, and email address when Facebook makes it available. We use them to create or link your VTE account, authenticate you, display your profile, and send account-related communications. An email address is required for this sign-in method; you can use email registration if Facebook does not supply one.

We use the Facebook access token to retrieve this profile during sign-in; we do not store it as an ongoing Facebook connection. Facebook Login does not give VTE access to your posts, private messages, friends list, or permission to publish to your Facebook account. Account information is hosted by Cloudflare, and your email is used by our email delivery provider for service communications. The analytics and diagnostic processing described above also applies to VTE accounts created with Facebook.

You can remove VirtualTourEasy in Facebook's Apps and Websites settings. Removing access does not automatically delete your VTE account or information already stored by us. Follow our data deletion instructions to request deletion of Facebook-derived data or your VTE account, including if you can no longer sign in.

4. Cookies and Local Storage

We use the following:

Analytics and advertising measurement tools may use cookies or similar identifiers to measure visits, referrals, and conversions. Product analytics may also use browser storage. You can manage cookies through your browser settings; blocking essential authentication cookies may prevent sign-in. Third-party settings and browser controls affect the information those tools can collect. Tour owners may add their own tracking as described above.

5. Data Storage and Security

Your data is stored on Cloudflare's global infrastructure (R2 for files, D1 for structured data). We implement industry-standard security measures including:

While we take reasonable precautions, no method of electronic storage is 100% secure. We cannot guarantee absolute security.

6. Data Retention

7. Your Rights (GDPR & Global Privacy)

Regardless of where you are located, you have the following rights:

To exercise any of these rights, contact us at support@virtualtoureasy.com. We will respond within 30 days.

Request deletion of your data

Email support@virtualtoureasy.com with the subject “Data deletion request”, your VTE account email, and whether you want your entire account or specifically your Google- or Facebook-derived information removed. We may verify account ownership before acting. Do not send passwords, authorization tokens, or payment card details. This route is available on every plan and if you cannot sign in. See our full deletion instructions for self-service options and what deletion affects.

8. Children's Privacy

VirtualTourEasy is not intended for children under the age of 16. We do not knowingly collect personal information from children under 16. If we learn that we have collected data from a child under 16, we will delete it promptly. If you believe a child has provided us with personal data, please contact us.

9. International Data Transfers

Your data may be processed and stored in various locations globally through Cloudflare's infrastructure. By using the Service, you consent to the transfer of your data to countries outside your country of residence, which may have different data protection laws.

10. Changes to This Policy

We may update this Privacy Policy from time to time and will notify you of significant changes by email or through a notice on the Service. Before using Google user data for a new purpose or accessing additional Google data, we will explain the change and request your consent as required by Google's policies.

11. Contact Us

If you have questions about this Privacy Policy or how we handle your data: