Vista · Privacy

Privacy Policy

This policy explains what Vista processes, why, who receives it, and how you can exercise your choices.

Effective October 28, 2026

Who we are and what this policy covers

Vista is operated by Amit Ben Dror, trading as Altitude ("we", "us"), at Espronceda 195, Barcelona, Spain. This policy covers Vista accounts, conference workspaces, research, badge capture, follow-ups, and connected services. Contact amit@altitudebiz.dev for privacy questions or requests.

When an organization uses Vista to manage prospect and conference information, that organization determines why it collects and uses that information. We process its workspace information to provide the service under its instructions. We also process account and operational information to administer and secure Vista. If your information was added by a customer, you can contact that organization or ask us to help route your request.

Information we collect and its sources

  • Account and workspace access: account identifier, name, email address, sign-in provider, workspace membership, permissions, and authentication/session information received from you and our authentication provider.
  • Workspace content: company briefs, event plans, professional contact details, company and role information, public profile and source links, meeting notes, booth answers, follow-up drafts, and team actions. This comes from users, their connected services, public sources, event organizers, and research or contact-data providers.
  • Badge capture and voice notes: badge photographs you select or capture are uploaded for text extraction; extracted details and written conversation notes can be saved to your workspace. When you tap the microphone, Vista saves your recording in this browser, including while offline. When connected, Vista uploads the recording to private Base44 storage and sends it to OpenAI for speech-to-text processing. The transcript is added to the associated note for you to edit. Voice notes are available to your sign-in within that workspace. Original audio is not sent to your CRM by this feature. Device copies remain in browser storage; clearing browser data before upload can lose a recording. Removing a saved contact does not automatically remove its audio. Contact us to request deletion of stored recordings.
  • Connected-service information: authorized account or portal identifiers, access credentials, selected field mappings, and contact, company, property, and activity information needed for the actions you enable.
  • Billing: if you use paid features, checkout may share your account email and workspace reference with Stripe. Payment details you enter are handled by the payment provider.
  • Technical information: request and device/browser information, timestamps, errors, security and service logs, and browser storage used for sessions, preferences, cached workspace information, and pending captures.

Google sign-in

If you choose Sign in with Google, Google and our authentication provider, Base44, process the sign-in. Vista uses your Google account identifier and email address to establish your account, authenticate you, and associate you with your workspace. Basic profile information, such as a name or profile image, may also be provided by the sign-in service if included in the permissions you authorize. Google sign-in does not give us your Google password.

Google sign-in is for account authentication. It does not grant Vista access to your Gmail messages, Google Drive files, Calendar, or Google contacts. We use information obtained through Google sign-in for authentication, account management, workspace access, support, and security. We store the account information needed for those purposes through Base44 and share it with providers only as needed to deliver those functions, with authorized workspace members where needed to identify teammates, or for the legal and security disclosures described below.

We do not sell Google user data, use it for advertising, or use data obtained through Google sign-in to train generalized AI models. Vista'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.

You can remove Vista's Google authorization through your Google Account connections. Revoking authorization does not itself delete your Vista account, end every existing Vista session, or remove workspace records. For account deletion, use the request process below.

How we use information

We use information to authenticate users, manage workspace access, research conferences and business prospects, extract badge details, save conversations, generate research and follow-up drafts, carry out authorized connected-service actions, prevent duplicates, provide support, and diagnose and secure the service. Vista does not sell customer or contact data.

AI and research providers may receive the relevant workspace brief, professional contact details, source material, badge image, or notes needed to perform the feature you use. Generated research and drafts can be inaccurate and should be checked before use.

Where applicable law requires a legal basis, we rely on performing our agreement with you, legitimate interests in operating and protecting the service, compliance with legal obligations, or consent where required. Customer organizations are responsible for the legal basis for the prospect information and outreach they direct us to process.

HubSpot and other authorized connections

When an authorized workspace user connects HubSpot, Vista can read contact and company information to match records and create or update authorized records, associations, notes, and mapped properties. Access credentials are stored to maintain the connection. Vista does not receive your HubSpot password.

Delivery depends on the workspace's selected workflow: captures can wait for review, or be sent directly to the configured HubSpot destination after capture processing. Users can also explicitly send saved details without an email lookup. Direct delivery may happen without a separate per-contact preview. Follow-up drafts and CRM record delivery are distinct actions.

Optional email-sending connections are separate from sign-in. If you configure Gmail sending, Vista stores the Gmail address and app password you supply and sends the approved recipient, subject, and message through Gmail. Microsoft sending uses separately authorized access credentials. Sending and delivery records are stored to track the requested action. Remove the sending connection and revoke its credentials with the provider to end that access.

Disconnecting the integration in Vista stops its future use of that connection. You can also revoke the app's access in HubSpot. Disconnecting does not erase records already saved in Vista or HubSpot; deletion must be handled separately in each service.

Who receives information

  • Your workspace: authorized teammates and workspace administrators can access shared content according to their permissions.
  • Service providers: Base44 provides application infrastructure, authentication, data storage, and integrations. Hosting, AI processing, research and contact-data, support, and operational providers process information needed for the features they provide.
  • Services you authorize: HubSpot and other destinations receive data when the workspace's users authorize the relevant connection and action. Those services also apply their own terms and privacy policies.
  • Legal, security, and business disclosures: information may be disclosed to comply with applicable law, respond to valid legal requests, protect rights and security, or complete a business transfer subject to applicable privacy obligations.

Information may be processed in countries other than your own, depending on the providers used. Applicable data-protection requirements govern those transfers. Contact us for information about the providers and transfer arrangements relevant to your workspace.

Browser storage, camera, and microphone

Vista uses browser storage and caching to keep sessions and preferences, remember workspace information, and retain pending captures during connectivity problems. Some capture data is stored only on the device until it can be uploaded. Clearing site data can remove unsent captures; signing out does not necessarily erase all locally cached data. Use a trusted device and confirm captures have been saved before clearing storage.

You control camera and microphone permissions in your browser or device settings. You can type contact details and notes instead. Browser or keyboard dictation is also subject to the speech provider's privacy settings. Vista loads web fonts from Google Fonts, which receives ordinary network request information such as your IP address when those fonts are requested.

Public pages and visit measurement

On our public Films and Events pages we count visits, which films are played and how far they are watched. These counts are anonymous and do not include your name or contact details.

If you choose Accept on the notice on those pages, we also use Apollo.io's website visitor service. It uses cookies and your IP address to work out which company a visit comes from, and shows us the company name and the pages visited, not who you are. If you choose Decline, or make no choice, Apollo is not loaded. You can change your choice at any time with the Cookie settings link at the bottom of those pages. We do not use this inside the signed-in Vista app.

Retention and security

For connected LinkedIn accounts, Vista stores up to 100 recent text messages per saved Inbox conversation, including message identifiers, direction, and timestamps, so authorized users can read conversations while live updates are paused. Attachments are not copied into this history. Access follows current workspace and sender permissions. Explicitly disconnecting that sender in Vista removes its saved Inbox history from active storage; temporary expired credentials pause updates without removing saved history.

We retain account and workspace information for as long as it is needed to provide the service and maintain the workspace, unless an earlier deletion request applies. Retention also depends on the type of information, customer instructions, security and support needs, and legal obligations. Badge uploads, cached copies, and provider backups can have a different lifecycle from the extracted contact record; deleting a contact or clearing a queue card does not necessarily delete its uploaded image or every copy.

We do not promise immediate removal from all backups or logs. When handling a deletion request, we identify the account and workspace records, uploads, and provider-held copies in scope and explain any information that must be retained and why. Disconnecting an account is separate from deleting its information.

We use authenticated access, workspace permissions, and encrypted network transport to protect information. Access credentials are managed through our application infrastructure and connected-service authorization systems. No service can guarantee absolute security.

Access, correction, deletion, and other choices

Email amit@altitudebiz.dev to request access, correction, export, restriction, or deletion of your personal information or Vista account. Include the account email or relevant workspace and describe your request; do not send passwords or access tokens. We may verify your identity and authority before acting. We respond within the time required by applicable law and explain any lawful limits on the request.

Deleting an individual's account may not delete records that their organization is entitled or required to keep in a shared workspace. You may also have rights to object to processing, withdraw consent without affecting earlier lawful processing, and complain to the appropriate data-protection authority, depending on where you live. Revoking a connected provider's access does not delete records held by that provider.

Policy changes

This policy is effective September 18, 2026. We publish changes here and update the effective date. If we materially change how we use personal information, including Google user data, we will provide notice through the service or account contact details and obtain consent where required before using it for a new purpose.