Privacy Policy
VIEWCY.COM INC.
PRIVACY POLICY
Last updated: November 17, 2026
What changed in this version. This Policy now covers the Viewcy apps and organizer tools as well as the website; explains that the organizer you buy from receives your details and is responsible for them; names the service providers we use; describes the analytics and session recordings on our site; adds a section on Google user data (Google sign-in and the Google Calendar connection for teachers); and sets out how long we keep data, your rights under EU, UK and California law, and how to delete your account.
1. Who we are and what this covers
Viewcy.com Inc. ("Viewcy", "we", "us") is a company in Brooklyn, New York. This Policy explains how we handle personal information when you use www.viewcy.com, the Viewcy mobile apps, the Viewcy check-in app, our organizer tools, our public API, and the checkout and calendar widgets that organizers embed on their own websites (together, the "Service"). It applies to everyone who uses the Service: organizers and their staff, attendees, members and students, and visitors.
2. Organizers and the people who buy from them
Viewcy is a platform. Events, memberships and lessons are offered by independent organizers, and when you buy from one of them, the organizer receives your name, email address, the answers to their checkout questions, your order details and, for lessons, any note you wrote to the teacher. The organizer is an independent controller of the copy it receives and is responsible for how it uses it after the sale; Viewcy remains responsible for its own use of the same information, as this Policy describes. Our Terms of Service require organizers to use it only for what you bought, to keep it secure, and to follow the privacy laws that apply to them. If you have a question about how an organizer uses your information, contact the organizer; we will help you reach them if you cannot.
For everything else in this Policy, including your Viewcy account, your use of the Service and the information we collect automatically, Viewcy is the controller.
3. What we collect
Information you give us.
- Account details: your name, email address, username and password, and your phone number if you verify it or ask for a sign-in code by text. If you enable two-factor authentication, the secret and recovery codes for it.
- Purchases and bookings: the names and email addresses on each ticket, the answers to an organizer's checkout questions, membership subscriptions, lesson bookings and the notes you write to a teacher, donations, and your check-in at the door.
- Payment information: card and bank details go directly to Stripe, our payment processor; we never see your full card number. We keep a reference to your Stripe customer record and, if you save a payment method, its brand, last four digits, expiry month and year, country and whether it supports 3-D Secure.
- Organizer information: your business details, the events, memberships, lessons, videos, images, files and text you publish, the venues and addresses of your events, your collaborators, your fee and refund settings, and the identity and bank details you give Stripe when you set up payouts (which Stripe, not Viewcy, holds).
- Messages: what you send us through support chat or email, and messages organizers send through the Service.
Information we collect automatically. When you use the Service we log your IP address, device and browser type, operating system, language, the pages and screens you view, the links you click, the site that referred you, the times of your visits, and error and crash reports. We use analytics tools (Statsig, Google Analytics, Microsoft Clarity and Vercel) to measure how the Service is used, and on our production site these include session recordings that replay mouse movements, clicks, scrolling and the text on the page (Statsig on our newer pages, Microsoft Clarity on our older ones, and Sentry for a sample of sessions and for every session in which an error occurs), so that we can find and fix problems. Payment details are entered in Stripe's own secure fields and are not part of these recordings. The mobile apps send us the app version, platform and an installation identifier. The check-in app records which tickets were scanned and when. Organizers' embedded checkouts collect the same information as a checkout on our site.
Information we get from others. Organizers, and guests they have approved for a private event, add guests and send invitations, which gives us the name, email address and sometimes the phone number they entered for you. Stripe tells us whether a payment succeeded and the country of the card. Google, Apple and Facebook send us your name, email address and account identifier when you sign in with them. Google sends us the information described in section 6 when a teacher connects a calendar.
4. How we use it
- To provide the Service: create your account, sell and deliver tickets, memberships and lessons, show your tickets at the door, run organizers' events and tools, stream and host video, and process payments and payouts.
- To send you the messages the Service needs: order confirmations, tickets, receipts, booking and membership notices, sign-in codes, security alerts and support replies. These are not marketing and you cannot opt out of them while you have an account.
- To send messages on behalf of organizers, such as event updates, invitations and the emails an organizer writes to their attendees. The organizer decides what is sent; every marketing email has an unsubscribe link.
- To tell you about Viewcy: our own news and features, and, if you tick the box at checkout that says "Send me emails about the best events happening nearby", events near you, chosen from where the events you have attended took place. The other checkout box, "Keep me informed about future events from this organizer", is the organizer's consent, not ours. You can opt out of either at any time; every marketing email has an unsubscribe link.
- To keep the Service safe and working: prevent fraud and abuse, enforce our Terms, debug errors, measure performance, and understand how features are used so that we can improve them.
- To run our AI features: when an organizer uses the AI event creator, what they type and the draft it produces are sent to our AI provider; to recommend events, we send the public text of events, videos and organizer profiles (titles, descriptions, tags, bios, and the public names of organizers and collaborators; never your account email address or your purchases, though public text an organizer wrote can itself contain contact details) to our AI provider to compute similarity scores.
- To comply with the law and with lawful requests, and to establish or defend legal claims.
Where the GDPR or UK GDPR applies, we rely on the performance of our contract with you, on our legitimate interests in running, securing and improving the Service, on your consent where we ask for it (for example, for marketing or a calendar connection), and on our legal obligations.
5. How we share it
- With organizers, as described in section 2, and with the collaborators an organizer has invited to help run their profile.
- With other people where you choose to: for example, when you transfer a ticket, join a public playlist, or appear in an organizer's public guest count.
- With the service providers that run Viewcy, who may use your information only to provide their service to us: Stripe (payments, payouts and in-person card readers); Google (sign-in, Google Calendar connections, Google Play billing, Google Analytics, and Google Maps and Places for venue search and addresses); OpenAPI.it (geocoding of venue addresses); Apple (sign-in, App Store billing and Apple Wallet passes); Meta (sign-in with Facebook, where you use it, and the Meta Pixel described in section 8); Microsoft (Clarity session recordings and heatmaps); Resend and Mailchimp Transactional (email delivery); Twilio (text messages); Mux (video hosting and streaming); Intercom (support chat and our help center, which receives your name, email address and account identifier when you are signed in); Sentry (error reports, the session recordings described in section 3, and the in-product requests described next when our project board can't be reached); ABE (our project board, which receives the requests you send us through an in-product form, such as an app or feature suggestion: your name, contact details, message and the event it concerns); Statsig (feature flags, product analytics and session recordings); Supabase (our own store of product analytics: the sessions and actions on our site, with device and referrer details, tied to your account when you are signed in); Convex (storage for the weekly sales report: the recipient email addresses and organizer identifiers); Vercel, Heroku and Cloudflare (hosting, databases, network and security); Amazon Web Services (storage of uploaded images and files); Anthropic and OpenAI (the AI event creator and recommendation scoring, through their APIs, under terms that do not let them train their models on it); Telegram (a sales notification to our own team for each completed payment, naming the organizer, the event and the amount, never the buyer); Neon (the database behind our reserved-seating charts, for the events that use them: the event name, the seats you pick and a temporary hold token, never your name); Gravatar, run by Automattic (if you have not uploaded a profile photo, your browser loads a default avatar from Gravatar using a hash of your email address (or of your name, if your account has no email address), which Gravatar can match to an account you hold there).
- When the law requires it, to respond to subpoenas, court orders and lawful requests, to protect the rights, property or safety of Viewcy, our users or others, and to enforce our Terms.
- In a business transfer: if Viewcy is involved in a merger, acquisition, financing or sale of assets, your information may be transferred as part of that deal, and we will tell you before it is handled under a different privacy policy.
- Aggregated or de-identified data, such as attendance totals, which cannot reasonably identify you.
We do not sell your personal information, and we never give attendee lists to advertising platforms or data brokers. When an organizer pays us to run an advertising campaign for their event, we use the organizer's budget and the ad platform's own audience tools; we do not upload attendee lists to the ad platform. Advertising pixels, ours and organizers', are described in section 8.
6. Google user data
This section covers the information we receive from Google through Google's APIs, separately from everything else in this Policy. Viewcy's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google sign-in
If you sign in with Google, we receive your name, email address and Google account identifier. We use them to create your account and sign you in; your name and email address then become your account details, handled as described in the rest of this Policy.
Google Calendar connection for teachers
A teacher who offers private lessons on Viewcy can connect a Google Calendar from the Team page of their course so that lessons booked on Viewcy appear on it. When you connect, you ask Google to let Viewcy see and edit events on your calendars. Viewcy uses that permission only to add each lesson booked through Viewcy to your calendar, and to update or remove that event when the lesson is rescheduled or cancelled. The event we create holds the lesson's start and end time, the course name, the student's name and any note the student wrote when booking.
We do not read, store or share your other calendar events or any other content of your Google account, and we do not use Google user data for advertising, to build profiles, or to develop, improve or train machine-learning or AI models. People at Viewcy do not access it, except with your consent, to resolve a support request you have made, for security, or where the law requires. To make the connection work we store, encrypted, the access credentials Google gives us, the identifier of the calendar we write to, the identifiers of the lesson events we created, and bookkeeping about the connection (when the credentials expire, which permission was granted, when we last synced and any error). We do not ask Google for your account's identity, so we do not learn or store the email address of the Google account you connected. We share none of this with anyone except Google and the hosting providers that store it for us, and we never sell it.
You can disconnect at any time from the same Team page, and you can also remove Viewcy's access from your Google Account at myaccount.google.com/permissions. Either one prevents any new write to your calendar, and disconnecting in Viewcy deletes the stored credentials at the same moment; a write that was already in progress at that instant may still complete. Lessons already on your calendar stay there unless you remove them. If we ever change how Viewcy uses Google user data, we will tell you and ask for your consent again before we do.
7. Text messages
We send text messages only when you ask for them or opt in. A verification text goes to you when you ask for a code to verify your number or sign in. Access-status texts for a private event go to you if you check the optional box for that event when you request access; on an event where guests sign in by phone, an approval notice may also go to the number you verified to request access. A ticket text, with a link to your tickets, goes to you once per order if you enter a mobile number in the optional field at checkout or on the order confirmation page; we use that number for that order's ticket text and to check whether that number has already answered the event organizer's question about texts. Promotional texts from Viewcy about events and offers, including invitations, go to you only if you check a separate optional box agreeing to them; at checkout and on the order confirmation page that box names one event organizer and covers Viewcy texts about that organizer's events. We ask each number once per organizer and keep the answer, yes or no, so we do not ask again. We send one text confirming each opt-in. No box or mobile number is needed to request access or buy tickets, and we never treat a phone number an organizer enters or imports, an invitation, or a number given only for ticket delivery, as your consent to promotional texts. We do not sell or share phone numbers or text-message consent with anyone for their own marketing; the only other use of a verified phone number is the hashed purchase report to Meta described in section 8. Message frequency varies. Message and data rates may apply. Reply STOP to any Viewcy text to stop all Viewcy texts to your number, or HELP for help.
Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties, except service providers that help us deliver the Viewcy messaging program. Our SMS Terms describe the program in full.
8. Cookies and similar technologies
We use cookies and similar technologies (local storage, pixels and software development kits in the apps) for four things: to keep you signed in and keep your cart and seat holds while you check out (strictly necessary); to remember your preferences; to measure how the Service is used, including the analytics and session recordings described in section 3; and to run support chat. Our older pages show a cookie notice on your first visit; our newer pages, including event pages and checkout, do not yet, and this Policy is the notice for them. You can delete or block cookies in your browser settings; blocking the strictly necessary ones will stop checkout and sign-in from working. We honor the Global Privacy Control signal: if your browser sends it, we load no Meta Pixel configured through Viewcy, neither ours nor an organizer's; tags an organizer delivers through their own Google Tag Manager container are under the organizer's control and are not affected by the signal. We do not respond to the older Do Not Track signal.
Advertising pixels. Viewcy places its own Meta Pixel on our pages, including event pages and checkout, which tells Meta the pages you view and the actions you take there (viewing an event, adding tickets to a cart, completing a purchase and its value) together with the identifiers Meta sets in your browser. When you are signed in, or have just bought a ticket, the pixel also gives Meta your email address and first and last name in a form that Meta hashes before use, so that it can match the visit to a Meta account. When you complete a purchase, we also report it to Meta from our servers (Meta's Conversions API): the order value and the event, a hashed form of your email address, name, account identifier and, if you have verified one, phone number, your IP address and browser, and the identifiers Meta set in your browser. That report goes to our pixel and, where the organizer has connected their own Meta Pixel to Viewcy, to theirs. We use all of this to measure our own marketing and the advertising campaigns we run for organizers through Boost; Meta uses it under its own policy. Organizers can also add their own Meta Pixel, Google Analytics and Google Tag Manager to their event pages, checkout and embedded checkout; what those send is under the organizer's control and responsibility. For organizers we enable it for, we also pass a hashed (SHA-256) form of the email address on your order to their Google Tag Manager container when you complete a purchase, so that they can measure their Google Ads conversions; we do not pass it when your browser sends Global Privacy Control. Where California law applies, a pixel like this may count as "sharing" personal information for cross-context behavioral advertising. To opt out, turn on Global Privacy Control in your browser or a browser extension: it stops us loading any Meta Pixel configured through Viewcy and stops our server-side purchase report, though not the Google tags an organizer adds; or block the pixel with a content blocker. You can also adjust your choices in Meta's ad preferences and Google's ad settings.
9. How long we keep it
- Your account and its content: for as long as your account exists.
- Orders, tickets, payments, refunds and payouts: for as long as your account exists and, after that, for as long as tax, accounting and payment rules require, usually seven years.
- Information organizers hold about their attendees: for as long as the organizer keeps it; the organizer decides, within the law.
- Public API request logs: 90 days.
- Google Calendar credentials: until you disconnect, when they are deleted.
- Text-message choices and STOP requests, with the phone number they belong to: kept after your account is deleted, so we keep honoring them.
- Support conversations, error reports and analytics: for the period our providers keep them, after which they are deleted or anonymized.
When you ask us to delete your account we confirm the request within 30 days. Deletion cannot run while you hold tickets to a future event, have upcoming events as an organizer, own an organization, or run a membership program that still has paying members; we will tell you what has to end first, and run it once it has. Memberships you hold yourself are cancelled as part of the deletion. Deletion removes your email address, phone number, photo, password and sign-in links from your account; your name stays on the records of your past orders, and we keep what we must keep under the law or to resolve a dispute, only for that purpose. A backup of the deleted profile, including your email address, is kept so that a deletion made in error can be reversed; tell us if you want that backup erased too, and we will erase it.
10. Your rights and choices
Wherever you live, you can ask us to tell you what personal information we hold about you, to correct it, to give you a copy, to delete it, or to stop using it for a particular purpose. To close your account and delete your data, email support@viewcy.com from the address on your account with "Delete my account" in the subject; we will confirm your identity and the request within 30 days, tell you about anything that has to end before the deletion can run (section 9), and tell you what we have to keep and why. You can change your name, email address and other account details yourself in your settings. Every marketing email we send has an unsubscribe link, and texts can be stopped with STOP; transactional messages continue while you have an account.
If you are in the European Economic Area, the United Kingdom or Switzerland, you also have the rights to restrict or object to our processing, to data portability, to withdraw consent at any time without affecting earlier processing, and to complain to your data protection authority. We respond within one month.
If you are a California resident, the California Consumer Privacy Act gives you the right to know what personal information we collect, use and disclose, to delete it, to correct it, and not to be discriminated against for exercising those rights. We do not sell personal information. The advertising pixels described in section 8 may count as sharing for cross-context behavioral advertising; section 8 says how to opt out. You may use an authorized agent to make a request, and we will verify the agent and the request before acting on it. The categories of information we collect, where we get it, why, and who we disclose it to are set out in sections 3 to 5.
Requests about information an organizer holds about you should go to the organizer; we will pass a request on if you cannot reach them.
11. Children
The Service is not for children under 13, and we do not knowingly collect personal information from them. A parent or guardian who buys a ticket or books a lesson for a child does so under the parent's own account, and the child's name on a ticket or booking is handled as part of that purchase. If you believe a child under 13 has given us personal information, email support@viewcy.com and we will delete it.
12. Security
We protect your information with encryption in transit, one-way hashing of passwords, encrypted storage of calendar credentials and other secrets, access controls, and monitoring. Card payments are handled by Stripe, which is certified to the PCI DSS. You can turn on two-factor authentication in your settings. No system is completely secure; if a breach affects your personal information, we will tell you and the relevant authorities as the law requires.
13. Where your information goes
Viewcy is based in the United States and our servers are there, so your information is transferred to and processed in the United States, where privacy law may differ from your country's. Our providers may process it in other countries too. Where the GDPR or UK GDPR applies, we rely on the safeguards the law provides for these transfers, including the standard contractual clauses and Data Privacy Framework certifications our providers offer, and you can ask us for details.
14. Changes to this Policy
When we change this Policy we update the date at the top and summarize the change there. If a change materially affects how we use personal information we already hold, we will tell account holders by email or in the product before it takes effect.
15. Contact us
Email support@viewcy.com with "Privacy" in the subject, or write to:
Viewcy.com Inc.
470 Ocean Avenue, Apt. LF6
Brooklyn, New York 11226-2884
United States
Our Terms of Service and Accessibility statement are published alongside this Policy.