Privacy Policy

Information we collect

• Account information: your email address, name, and password (stored in hashed form), or your Google profile details when you sign in with Google.
• Profile details: your line or lines of work, how you prefer to be addressed (the grammatical form in gendered languages) and your date of birth. How you prefer to be addressed is asked when you open your account (in Hebrew, where the address needs it). Your date of birth is asked only when you are about to receive money through MyVisito (connecting payouts, your first paid product or ticket sales), as part of the seller record, and it is our age check: selling through the shop, hosting paid events and collecting payments open at 18. It is not asked to open an account or to publish a card. They are never shown on a card, never visible to visitors or other members, and you can change them in your profile at any time.
• Card content: everything you choose to place on your cards, such as your name, role, contact details, photos, logo, services, prices, and links. When you publish a card, that content becomes publicly visible at its web address; with the default public search setting it may also be indexed by search engines, and you can switch the card to private (not indexed) at publish time or anytime in the editor. A published card is also listed by default in the MyVisitors community directory on our site (name, photo, role, and field only, never contact details), and you can remove it from the directory at any time in the card's settings.
• Workspace details: your workspace name and the public web address (handle) you choose.
• Usage and analytics: events on your own cards, such as views, contact saves, link taps, and shares, so we can show you how your card performs.
• Copilot conversations: when you use the AI copilot, we store your chat with it, along with any images, PDFs, or links you attach, so the assistant works and you can return to a conversation. Flyer Studio: when you design a flyer with AI, the words you typed are sent to the image model (OpenAI) to draw the flyer, and your photo is sent only when you switch on "Compose my photo into the design"; neither is used to train those models.
• Technical information: when you create an account, and again on each sign-in, we record your IP address, approximate location, and device and browser type. At sign-up and after you sign in, we also check the device and keep a device identifier derived from technical characteristics of your browser and device. We do all of this to protect your account and the service and to prevent fraud and abuse, and it also happens when a sign-up is started and not completed. The device identifier is used for these purposes only: never for advertising, never to follow you across other sites, and it is never sold or shared with anyone other than the service providers listed in this policy. Your recent sign-ins are shown to you in your account security settings, and if you mark a device as trusted we remember it so you are not asked for a second factor every time. The detailed record of each device check is kept for a limited time, and longer only while it is needed to prevent abuse, for example the record of a blocked account.
• Blocked accounts: when we block an account for abuse (see "Suspension and termination" in our Terms of Use), the account is locked, not deleted. Its cards go offline, and the account and its data stay in our systems for as long as the block lasts. So that the same abuse cannot return, we also keep a record of the block, which holds the details that identify the account and the technical information described above. We keep that record for as long as it is needed to protect the service, in our legitimate interest of preventing fraud and abuse. Deleting a blocked account is a separate step: it happens when you ask us to delete it or when we decide on it separately, and the record of the block stays even then. If you believe you were blocked by mistake, contact us as described in this policy and we will review it.
• Visit counts on our public website: when you read a page on our marketing site or blog, we count the visit and how far the article was read, without a cookie and without any identifier on your device. Your address is turned into a code that changes every day and is never stored, so visits cannot be linked to you or to each other across days. We use these counts only to learn which pages help people.
• Payment information: when you buy a plan, your payment is handled by Stripe. We receive billing details such as your name, email, country, and subscription status, but not your full card number.
• Identity verification: if we place your account under review and the question is whether the account is really yours, we may ask you to verify your identity. The document and the selfie are collected and checked by Stripe Identity on Stripe's own page. We receive only the outcome of the check and store only that outcome with its date; we never receive or store the document, the photo, or your identity number. This is asked only where a specific risk was identified, never routinely.

Information from card visitors and leads

When you publish a card, people can view it, and some information is collected from those visitors.

Lead details: when a visitor leaves their details through a lead form on your card, those details (such as name, phone, email, and message) are collected for you, the card owner. For that lead information you are the data controller, and we process it on your behalf as your service provider. You are responsible for having a lawful basis to collect it and, where the law requires, for giving those visitors your own privacy notice.

Subscribing to a card's updates: when someone taps Subscribe on a card (from the card itself, an event invitation, a public page, or the discovery screen in the app), the card owner sees their name and, if they have a MyVisito card, a link to it, as part of the owner's audience. The subscriber's email address stays with MyVisito and is used only to deliver the owner's updates; it is not handed to the owner. A phone number or an email address reaches the owner only if the subscriber chooses to share them, in the values the subscriber types (they may differ from the account's), and the subscriber can change or remove them at any time from their subscriptions list in the app. For details a subscriber shares this way the card owner is the data controller, exactly like lead details, and we process them on the owner's behalf. The sentence saying what the owner sees is shown before the subscription is confirmed. A subscriber can unsubscribe at any time from their own list in the app, and every update carries an unsubscribe link.

Event guest lists: names, phone numbers, and emails a host adds to an event guest list are the host’s data. The host is the data controller for that list, and we process it on their behalf to deliver their invitations, confirmations, reminders, and updates. Guests can opt out of phone messages at any time through the link on the event page or by replying to a message, and we honor that opt-out across the whole service. When someone registers to an event through its public page, we also record the technical details of that registration (IP address, approximate location, network, device and browser type, and the page that led there) and show them to the host, so the host can spot abuse, impersonation or duplicate registrations. Hints derived from them are presented to the host as facts to check, never as a verdict about the guest. Since September 2026, email a host sends to guests carries the host’s own identification in its footer, the business name and postal address the host entered in their settings, and that identification is disclosed to every recipient of those emails. When a guest unsubscribes and chooses to tell us why, we keep that reason with the unsubscribe and show the host that the contact is blocked; the host cannot remove that block.

Your own card from the details you left: when you leave your details on a card, subscribe to a card's updates, or register for a business event, MyVisito may offer you a card of your own built from those same details (your name and, where you gave them, your job title and company). This offer is MyVisito's own, made to you as the person who typed the details, and it changes nothing for the card owner or host, who keeps your details as described above. You see the offer on the screen right after you leave the details; after details left on a card or a card's updates, if you do not take it, we send you a single reminder by email, to the address you typed, within two days, and then nothing more. After an event registration the offer stays on the confirmation screen only, and no reminder is sent. The link in that offer is personal and expires after fourteen days. A card is created only once you confirm your email with a code; until then no account exists. At private events and webinars no such offer is made.

After a business event: for a business event, the organizer can turn on a "who is coming" list. Whether you appear on it is your choice at registration (a checkbox), and you can join or leave the list at any time from your personal ticket page. The list shows only your name and, if you have a MyVisito card, its photo and job title, never a phone number or an email. The morning after a business event we email its registered guests one summary: who was on stage (with their cards), the guests who chose to be listed, and how many guests saved your card. That summary goes out once, only to people who registered for that event, and every message carries an unsubscribe link. When a host names a performer, speaker or supplier on the event page and links that name to a real person, we show the link only after that person accepts it (at a private event, a supplier credit can appear as soon as the host links it, and shows nothing but the name and the card).

Replies to our messages: when someone replies to a WhatsApp or SMS message sent from our number, we record the reply, including its text, so that we can answer it, register an RSVP made from the message itself, honor an opt-out request, and keep our sending number safe from abuse. The text of a reply is deleted after 90 days; only the fact that a message arrived, over which channel, and what we did about it is kept beyond that.

Automatic screening of submissions: every message a visitor sends through a public card, page, or event (a lead form, a question, a meeting request, a message to an organizer) is checked automatically before the owner is notified. A submission that looks automated is held for the card owner instead of delivered, together with the request details and approximate location; the owner can bring it in or delete it, and a held submission is deleted after 30 days. We do this in our legitimate interest of keeping the service free of spam and abuse.

Messages between members: a message you send to another member through MyVisito is kept as part of that conversation for both of you. You can unsend your own message within 24 hours of sending it; it is then removed for both sides and a note that a message was deleted stays in its place. To let a recipient report abuse, the content of an unsent message is kept for 30 days in storage that neither side can read, and is then deleted for good. Deleting a message for yourself only hides it from your own view. An email notification that was already sent about a message cannot be recalled.

Visitor analytics: when a published card is viewed, we record analytics events (such as a view, a QR scan, a saved contact, or a link tap) together with approximate location (country and city), device and browser type, and the referring website. We use this to give the card owner performance statistics and to protect the service. We do not use it to identify individual visitors or to serve advertising.

Card scanning: a card owner can scan a paper business card, and on some cards a visitor can choose to scan their own business card to hand over their details. In both cases the photo is processed by AI only to extract the contact details on it (such as name, phone, email, and social links) into the card owner's contacts. The card owner is the data controller for the scanned details, just like lead-form details, and we process them on the owner's behalf.

Contacts import: a card owner can import contacts from a file, such as a CSV or vCard export from another app. The imported details go only into that owner's own contacts; the owner is the data controller for them, is responsible for having the right to import them, and we process them on the owner's behalf.

Imported public reviews: a card owner can import their public Google reviews onto their card, including each reviewer's public name, profile photo, and review text. The imported reviews become part of the owner's card content, and the owner is responsible for displaying them.

The places directory

Our site includes a directory of places (venues such as clubs, bars, halls and restaurants) with a page for each. The details on a place's page (name, type, address, phone, website, social links, a map and a logo) come from publicly available sources, including OpenStreetMap and the place's own website, from details members entered when naming the place on their own shows or events, and from the place itself once it claims the page. Where a place is run by one person, some of these details (for example a contact phone) may be personal data. We process them on the basis of our legitimate interest in running a public directory of places where events happen, we show only business contact details that the place itself makes public, and we never add private details.

If you own or manage a place and want its details corrected, the page claimed, or the page removed, or if you object to your details appearing, write to contact@myvisito.com and we will act promptly.

Buyers and purchases (Earn)

Card owners on selling plans can offer products for sale from their cards ("Earn"). If you buy from a seller, the seller is the merchant and the data controller for your purchase; we process your details on the seller's behalf as their service provider.

For each order we collect and store for the seller: your name, email, phone if you provide it, your shipping address for physical products, your answer to any question the seller added at checkout, and the product, amount, and status of the order. We use these details to deliver your purchase (your order page and order email) and to show the seller their orders and buyers.

When your payment is collected through MyVisito's own payment rail (shown on the checkout page and on your card statement as MyVisito together with the seller's name), the payment itself is processed by Stripe on MyVisito's account. We receive the order details and the payment status; your full card number is handled by Stripe and never reaches our servers. Cancellation rights depend on the product type and applicable law, as explained in the Commerce Rules; requests are made from your order page.

On the seller-owned Stripe rail, Stripe processes the payment in the seller's connected account. Legacy orders may reference another provider or an external payment link that was available when the order was created. In every case, the full card number is handled by the payment provider and never reaches MyVisito's servers.

If the seller connected external tools (such as an email marketing service, a CRM, or a spreadsheet), we pass your order details to those tools on the seller's instructions. The seller may also issue you an invoice through an invoicing service they connected.

Order records are kept for the seller and for fraud prevention, dispute handling, and legal compliance. To exercise your privacy rights over purchase information, contact the seller directly, or write to contact@myvisito.com and we will route your request to them.

How we use your information

• To create, host, and display your digital business cards (to perform our contract with you).
• To generate and edit card content with AI when you ask the copilot to do so (to perform our contract with you).
• To show analytics about cards, to keep the service secure, and to prevent fraud and abuse (our legitimate interest in running a safe, useful service).
• To process payments and manage subscriptions (to perform our contract and meet legal and tax obligations).
• To send you service emails such as verification codes and important account notices (to perform our contract), and, only with your consent where required, occasional product updates.
• To respond when you contact support (our legitimate interest and, where relevant, our contract with you).
• To comply with the law and enforce our terms (to meet a legal obligation and our legitimate interests).

Usage measurement inside your account

When you are signed in to your account area, we measure how the service is used: which screens are visited and how pages are used (clicks, scrolling, and movement between screens), including through an analytics and session-replay service that works for us. Text you type and media you upload are masked before anything is recorded. We use this information to operate, secure, and improve the service; it is part of providing the service under our Terms of Use, which you agree to when you create an account.

This in-account measurement is separate from measurement on our public website, which runs according to your cookie choice as described below and in our Cookie Policy.

AI processing

When you use the copilot, the text you provide and your card content, plus any images, PDFs, or links you attach, are sent to our AI provider only to produce the result you requested. This content is not used to train AI models.

We do not use the copilot to make decisions about you that produce legal or similarly significant effects without human involvement. Please do not paste other people’s sensitive personal information into the copilot unless you are permitted to.

Published content (cards and shop products) may be automatically scanned by AI to detect violations of our Terms of Use, such as illegal or harmful content. Flagged content is reviewed by a person before any final decision about your account.

Signing in with Google

If you choose to sign in with Google, we receive only your basic profile information: your name, email address, and profile picture. We use it solely to create and secure your account and to prefill your profile.

If you also connect Google Calendar (from Settings > Integrations, or by leaving the calendar box ticked when signing in), we ask for one narrow permission: to create a calendar named "MyVisito" in your account and to manage the entries we put in it (the events you publish, the meetings you confirm, the consultations people pay for, and their Google Meet links). We never read your other calendars or their events. We store the encrypted refresh token, the id of that calendar and the ids of the entries we created, and delete them when you disconnect.

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We do not share, sell, or use Google user data for advertising, and we do not use it to train AI models. You can disconnect Google from your account at any time, and you can request deletion of this data by contacting us.

Pre-saves on music services

When an artist offers a pre-save for an upcoming release and you tap a music service (Apple Music, Deezer or TIDAL), you authorize that service directly, and it gives us a token for one purpose: adding that release to your library on release day. We store the token encrypted, use it only for that release, and delete it when you remove the pre-save (a link in the release-day message does that) or once the release is delivered and the retry window ends. We never read your listening history or change anything else in your library. A Spotify pre-save opens a page run by a partner or by the artist's distributor, under that page's own privacy terms.

Cookies

We use a small number of cookies and similar technologies to keep you signed in, remember preferences such as language, and measure usage. On our public website, measurement runs only with the relevant permission through the cookie banner; inside your signed-in account area, usage measurement is part of the service itself, as described above. For our own advertising on Facebook, Instagram, LinkedIn and inside ChatGPT, the Meta Pixel, the LinkedIn Insight Tag, the ChatGPT Ads Measurement Pixel and a server-side connection to those three networks run on our public website only with your permission through the cookie banner, and the identifiers we send (email, account id) are hashed first; without that permission nothing reaches them. If you arrive through a partner (affiliate) link, a temporary attribution cookie is set for up to 90 days so the referral can be credited. A card owner may configure Google Analytics or Facebook Pixel on their public card; those tools remain off until the visitor separately allows card-owner tracking. Our Cookie Policy explains every category and how to change your choice.

How we share information

We do not sell your personal information. We share it only with the categories of service providers below, which run the service under our instructions and data-processing agreements, and only with what each needs to perform its role:

• Cloud infrastructure providers: hosting the service and running its database, authentication, and file storage.
• AI providers: processing your copilot and import requests, only to produce the result you asked for; never to train their models.
• Email delivery providers: sending transactional emails such as verification codes and account notices.
• Usage measurement: analytics and session-replay services measuring our own service, with typed text and media masked; on the public website only according to your cookie choice, and inside your signed-in account area as part of the service.
• Advertising measurement: Meta, LinkedIn and OpenAI (ChatGPT Ads), to measure our own campaigns, receiving hashed identifiers and signup (and, for Meta and OpenAI, first-purchase) events only when you allowed MyVisito analytics on our public website.
• Fraud-prevention providers: turning an IP address into an approximate location, to protect against abuse.
• Cloudflare Turnstile: bot protection on sign-up, sign-in and other forms on the service. The check usually completes by itself; once in a while it asks you to tick a box. For this, Cloudflare receives technical information about your browser and connection, including your IP address, and uses it only to tell a person from a bot, never to identify you or build a profile of you. Cloudflare's Turnstile privacy policy describes this in full.
• Fingerprint (FingerprintJS, Inc.): fraud prevention when you sign up, including a sign-up that is not completed, and after you sign in. Fingerprint receives technical characteristics of your browser and device, your IP address and, after you sign in, an identifier of your account. It returns a device identifier and risk signals to us and stores them on servers in the European Union. We use them only to protect accounts and to prevent abuse, never for advertising and never to follow you across other sites.
• Stripe: payment processing when you purchase a plan, and, if you sell through MyVisito, payments from your buyers through your own connected Stripe account. For sellers using payments through MyVisito (currently offered in Israel), buyer payments are processed on MyVisito's own Stripe account, with MyVisito acting as the seller's limited payment collection agent; card details are handled by Stripe and never reach our servers. Where we ask you to verify your identity, Stripe Identity performs the check on Stripe's page and returns only the result to us.
• Google: sign-in, if you choose to use it, and Google Tag Manager measurement tags (on the public website according to your cookie choice, and inside your signed-in account area as part of the service).
• Apple and Google Wallet: if you add a card to Apple Wallet or Google Wallet, the details shown on the pass (such as the name, role, photo, and card link) are sent to Apple or Google to create the pass on your device.
• Zoom: if you connect your Zoom account, we create, update and delete meetings and webinars in it for the sessions you sell, confirm or host, sending Zoom the session title, time, duration and a short agenda line. We store your encrypted OAuth tokens, your Zoom user id and account email, and the ids and join links of the sessions we created; we never access recordings, chat, transcripts or participant data. Everything is deleted when you disconnect in MyVisito or remove MyVisito inside Zoom. Zoom's own privacy policy applies to your Zoom account.
• Tools you connect yourself, such as a CRM, an email marketing service, a spreadsheet, an automation service, a payment provider, or an invoicing service: we send lead and order details to them at your direction, and their own terms and privacy policies apply to them.

Legal disclosures and business transfers

We may disclose information if required by law, to respond to lawful requests, to protect the rights, safety, and security of our users and the service, or in connection with a merger, acquisition, or sale of assets, in which case we will take reasonable steps to ensure your information stays protected.

Where your information is processed

We and our providers process information in the United States and in other countries. When we transfer personal information out of the European Economic Area, the United Kingdom, or Israel, we rely on appropriate safeguards, such as the European Commission’s Standard Contractual Clauses, so that your information keeps a comparable level of protection.

Connecting Instagram

If you connect your Instagram professional account, we receive from Meta an access token, your Instagram account id, username and profile picture, and, through Meta's webhooks, the comments and direct messages the account receives. We use them for two things: to send the automatic replies you configured (a public reply under a comment, a private message with the link you chose), and to show you each person's conversation in your MyVisito inbox so you can read it, add a private note and answer them (within the 24 hours Instagram allows after their last message). We never post on your behalf, never read other accounts, and never use this data for advertising or to train AI models.

The conversations (the messages the person sent, the replies sent by your automations or by you, their username and profile picture, and whether they follow the account) are stored so the inbox can show them. They are visible only to the account's owner and managers.

Only when a person types their email address in the conversation does it become a contact in your own audience (your CRM), together with their Instagram username. You are responsible for that contact list; the person may ask you to remove it at any time.

The access token is stored encrypted and refreshed while the connection is active. Disconnecting Instagram in the app deletes the token immediately; deleting your account deletes the connection, its rules and its conversations. After a disconnect the conversations stay in your inbox, read-only, until your account is deleted or you ask us to delete them; a data deletion request made through Meta deletes them. A record of the replies that were sent is kept as usage history. You can also ask us to delete this data by writing to contact@myvisito.com.

Data retention and deletion

We keep your information for as long as your account is active. You can delete a card at any time, and you can permanently delete your entire account yourself from your account settings (Login and security > Delete account) on the web or in the mobile app. Deletion is immediate: your cards go offline, your data is removed, and any active subscription is cancelled immediately with no further charges. You can also request deletion by writing to contact@myvisito.com.

Some information is kept longer where we must: billing and tax records are typically kept for around seven years, and limited information may remain to meet a legal obligation, resolve a dispute, or enforce our terms. After account deletion we retain a minimal record of the account (such as the account email, billing history, and usage records of paid features such as AI credits) for fraud prevention, dispute handling, accurate billing, and legal compliance. Uploaded images may remain in storage for a period even after the card that used them is deleted, and copies may persist in routine backups for a limited time. Lead details you collect are kept until you delete them.

Your privacy rights

Depending on where you live, you have rights over your personal information. We honor these rights for everyone where we can.

If you are in the EU/EEA or the UK, you have the right to access, correct, delete, or receive a copy of your personal information, to restrict or object to certain processing, and to withdraw consent at any time. You also have the right to complain to your local data protection authority.

If you are in California or another US state with privacy rights, you have the right to know what personal information we collect, to access and delete it, and to correct it. We do not sell or "share" personal information for cross-context advertising, so there is nothing to opt out of, and we honor recognized opt-out signals such as Global Privacy Control. We will not discriminate against you for exercising your rights, and you may use an authorized agent.

If you are in Israel, you have the right to review and correct information we hold about you under the Protection of Privacy Law.

To exercise any right, email contact@myvisito.com from your account address. If you are a card visitor or a lead, the card owner is responsible for your information; you can contact them directly, or contact us and we will route your request to them.

Security

We protect information using measures that include encryption in transit, encryption at rest through our infrastructure providers, database-level access policies and user roles, one-way password hashing through our authentication provider, and restricted access to production systems. Card payments are handled by Stripe, and MyVisito does not store your full card number. MyVisito also completes an annual PCI DSS assessment (SAQ A) that Stripe validates. No method of storage or transmission is completely secure, but we work to protect information and improve our safeguards.

Data breaches

If a data breach affects your personal information, we will notify you and the relevant authorities where the law requires, and take reasonable steps to limit the impact.

Children

MyVisito is open from age 16. Between 16 and 18 the service is the card only; selling, hosting events and purchases open at 18, and the date of birth given on the seller record before any money is collected is how we check this. The service is not directed at anyone under 16, we do not knowingly collect information about children under 16, and an account we learn belongs to someone under 16 may be closed. If you believe a child under 16 has given us personal information, contact us and we will delete it.

SMS messages and your phone number

MyVisito is a trade name (DBA) of EMODEFLOW LLC, the registered sender of our SMS messages. When you enter your phone number in your account, we use it for two things only: to send you a one-time verification code, and to deliver the account alerts you switch on yourself in Settings (a new lead or booking request on your card, an event registration, a sale). Each alert has its own on/off switch, and you can reply STOP to any message to stop receiving SMS from us.

Message frequency varies with your activity and the alerts you enable. Message and data rates may apply. Reply STOP to any message to opt out, or HELP for help.

We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent are excluded from every other category of sharing described in this policy: they are never shared with anyone except the messaging providers that carry the message (Twilio for international SMS and WhatsApp, ActiveTrail for SMS in Israel), and only to deliver it.

Changes and contact

If we make material changes to this policy we will take reasonable steps to let you know. For any question or request about your privacy, or to reach EmodeFlow, LLC as the data controller, write to contact@myvisito.com, or by mail: EmodeFlow, LLC, 1111b South Governors Avenue, Suite 93153, Dover, DE 19904, United States.