Visioner CRM

Legal

Privacy Policy

Last updated: July 19, 2026

Visioner CRM is built for strategic account work. That can include sensitive customer and relationship information, so our privacy posture emphasizes data minimization, clear cloud-feature boundaries, and explicit opt-in for sensitive workflows.

1. Scope

This Privacy Policy explains how Visioner CRM collects, uses, stores, and protects information when you use the Visioner website, web app, Android app, iOS app, beta programs, support channels, and related cloud services.

Visioner CRM is operated by Ronisens Inc. References to Visioner, we, us, or our mean Ronisens Inc. and the Visioner CRM product team.

2. Information We Collect

Account and registration information may include your name, email address, company, role, plan interest, workspace identifier, and support messages.

Security information may include temporary one-time verification challenges, delivery status, failed-attempt counts, IP address, and browser information used to protect signup and login. Visioner stores one-time email codes only as cryptographic hashes, and codes expire after a short period.

Product data may include account names, customer domains, contacts, titles, phone numbers, notes, tags, projects, tasks, org charts, files, relationship health, account signals, and activity logs that you choose to enter, import, or sync.

If you use optional cloud features such as BCC email capture, sync, backup, contact enrichment, or intelligence workflows, Visioner may process the selected data needed to provide those features. For email capture, this can include sender, recipients, subject, timestamps, readable message text, attachment names and sizes, routing metadata, summaries, and project classification status. Visioner does not currently retain raw MIME or binary attachment files.

Usage and device information may include page views, feature events, browser or app version, operating system, timestamps, IP-derived rough region, errors, and diagnostic logs.

3. Browser Workspace and Cloud Data

Visioner is SaaS-first, but the browser may keep a local workspace cache for speed and continuity. Data you enter, import, sync, upload, route through cloud features, or send to support may be processed by Visioner to provide the service.

Browser reset, cache clearing, or device loss may affect locally cached data. You are responsible for maintaining exports or backups for data that has not been synced or otherwise stored in the service.

4. Mobile Apps, Personal Space, and Device Permissions

The Android and iOS apps have separate Personal and Work spaces. Personal can be used without a Visioner account. Personal relationships, user-chosen cadence, importance, private context, snooze or pause state, and touch history are stored in a protected on-device vault by default and are not uploaded to Visioner Cloud merely because you use Personal.

When you choose people from Apple Contacts, Visioner reads only the selected contact records needed for the feature, such as name, organization, title, email address, phone number, and linked profile URL. A device contact identifier may be stored locally to support explicit updates and avoid duplicates. Visioner does not upload your full address book or scan contacts you did not select.

On supported Android versions, the system Contact Picker returns only the person and fields you select without giving Visioner general Contacts permission. On earlier supported versions, Visioner requests read access only after you start an import and then reads the contact you choose. Sending a Visioner contact back to Android Contacts opens the system contact editor for your review and confirmation; Visioner does not request direct Contacts write permission.

Contacts access is requested only when needed for an import or synchronization action. Calendar access is requested only when you connect an optional Visioner task calendar. The mobile app uses dedicated Visioner Personal and Visioner Work calendars for task title and due-date synchronization and does not scan unrelated calendars. Notification permission is requested only when you enable reminders, and relationship reminder text is designed not to name a contact, customer, or task on the lock screen.

Switching between Personal and Work does not move data. If you explicitly add a Personal person to a chosen Work Account, Visioner copies contact fields such as name, title, email address, phone number, and linked profile URL. Personal cadence, importance, last-touch time, context notes, and interaction history remain in Personal.

Visioner does not read iMessage, SMS, call-log, or mailbox history. Email, Message, and Call actions use platform-provided compose or external-app interfaces and remain user initiated. BCC email capture processes only messages that a user deliberately sends to a Visioner capture address. The iOS Share Extension and Android Share Target process text or URLs that you explicitly share and may hold a minimal protected draft on device until the main app imports it.

Work is the Visioner Cloud companion. After you sign in, selected Work records, offline edits, and captures may synchronize with the workspace as described elsewhere in this policy. Personal data remains outside that sync unless you perform the explicit contact-fields-only action above.

5. How We Use Information

We use information to provide and improve Visioner, create and maintain workspaces, route and summarize emails, generate local and cloud signals, process support requests, manage billing, prevent abuse, debug errors, analyze activation and retention, and communicate about the product.

We do not sell your CRM content, account notes, project records, or private email content.

6. Cloud Providers and Subprocessors

Visioner may use service providers for hosting, analytics, email delivery, payment processing, database storage, file storage, support, AI-assisted workflows, and contact enrichment. These providers process information only as needed to deliver the relevant service.

Payment details are handled by payment processors such as Stripe or PayPal when enabled. Visioner does not intend to store full card numbers.

7. Email Capture and Attachments

BCC email capture is an optional cloud feature. When enabled, emails sent to a Visioner capture address may be used to match verified senders, customer domains, account aliases, projects, contacts, and review queues.

In V1, Waiting Reply status is a reminder based on the outbound email and user workflow. Automatic reply detection requires forwarded replies, mailbox rules, or future Gmail/Outlook authorization.

We aim to minimize raw email retention over time by keeping metadata, summaries, routing decisions, and user-confirmed activity records where practical. During beta, retention behavior may evolve as the product matures.

8. Third-Party Integrations and BYOK

Some enrichment features allow an authorized workspace Owner or Admin to connect a third-party API key. Visioner encrypts connected keys in the workspace credential vault, does not return the plaintext key to the browser after connection, and uses it only for authorized provider calls initiated for that workspace.

You are responsible for ensuring your use of third-party APIs, customer data, and enrichment results complies with applicable laws, provider terms, and your company policies.

9. Security

We use reasonable technical and organizational measures to protect information, including HTTPS, access controls, secret management, audit logs for sensitive cloud calls, and limited internal access.

Signup and login use a standard automated security check with a globally available one-time email-code fallback when the standard check is unavailable. One-time codes are short-lived, single-use, rate limited, and stored only as cryptographic hashes.

No online service can guarantee perfect security. Please do not use Visioner as the only copy of critical legal, contractual, financial, or compliance records.

10. Retention and Deletion

We retain information for as long as needed to provide the service, support users, comply with legal obligations, resolve disputes, prevent abuse, and improve the product.

Personal relationships can be removed in the Android or iOS app together with their private Visioner touch history. This does not delete the separate Android or Apple contact, external Visioner Calendar events, or a Work contact that you previously created through an explicit copy. On-device app data is also subject to your device, backup, and app-removal settings.

You may request deletion of account information or cloud-stored workspace data by contacting support. Some records may remain in backups, logs, billing records, or legal archives for a limited period where required or reasonably necessary.

11. Your Choices

You can choose whether to use Personal on device, sign in to Work cloud services, enable sync, select contacts, enable Calendar or notifications, use BCC capture, share content into Visioner, upload files, or connect third-party APIs. You can change permissions later in Android or iOS Settings, although the related feature may stop working.

You may export or delete local data using product controls where available. You may also contact support for help with cloud data access, correction, export, or deletion requests.

12. International Use

Visioner may process information in the United States or other locations where we or our service providers operate. By using Visioner, you understand that information may be transferred and processed outside your country or region.

13. Changes

We may update this Privacy Policy as Visioner develops. If changes are material, we will update the date on this page and take reasonable steps to notify users where appropriate.

Contact

For privacy questions, access requests, or deletion requests, contact support@visioner.cc, or review the dedicated Account and Data Deletion page.