Privacy Policy

This policy explains what information Vidyst collects when you use the Vidyst app for macOS, Vidyst Remote for iPhone and iPad, your Vidyst account, the account dashboard, the guest join page and this website; how we use, store and share it; and the choices you have. Vidyst is the controller of the personal information described here.

At a glance:

• Your cameras, screen and audio are captured, mixed, encoded and recorded on your Mac. We never store or analyze them. They leave your Mac only for the destinations you choose and, when you invite guests, for the live call with them.
• Custom RTMP servers and their stream keys are stored on your Mac, not on our servers.
• Vidyst Remote talks only to your own Mac, over your local network. It has no account, collects no data and never reaches our servers. See Vidyst Remote for iPhone and iPad.
• When you connect YouTube, we use your YouTube data only to run your broadcasts, live chat and live statistics in Vidyst. We never sell it, never use it for advertising, and never use it to train AI models. See YouTube and Google data.
• Your dashboard shows your own session history: how long you were live, where you streamed to, and how many guests joined. It belongs to your account and is deleted with it.
• The app sends usage counts and crash reports. Once you sign in they are linked to your account, so we can see how people get from downloading the app to using it. You can turn this off. The app has no advertising SDKs, and we do not sell your information.
• Our websites measure visits, page performance and errors. The account dashboard links this to your account; the guest join page does not.
• Every company that processes data for us is listed under Subprocessors.

Media stays on your Mac

Capture, compositing, encoding and recording happen locally. We do not receive, store or analyze your video, audio or recordings. When you go live, your stream is sent directly from your Mac to the destinations you choose, such as YouTube, Twitch or a custom RTMP server, and is then governed by those services' policies.

The one exception is a call with guests. Live audio, video and screen shares between you and your guests are relayed in real time through Cloudflare Realtime, Cloudflare's media relay, so that they reach each other over any network. They are encrypted in transit, are not recorded or stored by us or by Cloudflare, and stop the moment the call ends. See Guests.

Permissions the app asks for

macOS asks for your consent before Vidyst can use each of these. You can change them at any time in System Settings › Privacy & Security.

• Camera and microphone. To use your cameras and microphones as sources in your scenes, recordings and streams.
• Screen recording and system audio. To capture the displays, windows, apps and app audio you add to a scene.
• Local network. To record to network drives and NAS storage on your local network, and to let an iPhone or iPad you have allowed control Vidyst with Vidyst Remote.

Information stored on your Mac

• Sign-in session. A refresh token in your macOS Keychain, and a cached copy of your name, email address and plan in the app's preferences so the studio opens even when you are offline.
• Custom RTMP servers. Their names and server addresses in a local database in Application Support, and their stream keys in your Keychain. They are never sent to us.
• Scenes and settings. Your scene collections, layouts, images you add, and your recording and streaming preferences.
• Recordings. Saved only to the folders or drives you choose.
• Allowed remotes. For each iPhone or iPad you allow, the name of the device, when you allowed it and the key the two of them use, in your macOS Keychain. Removing a device in Settings › Remote deletes it.
• Analytics identifier. The random install identifier described in App usage data, and any usage events or crash reports waiting to be sent.

The app reads basic facts about your Mac, such as its chip and model, on your Mac to choose encoder settings. Only the general facts listed under App usage data are ever sent, and only if usage data is on.

Information we collect on our servers

• Account information. Your email address, name and account identifier from the sign-in method you choose (Apple, Google or email). Sign-in happens in your browser; the app never sees your password. Signing in with Google gives us only your name, email address and profile; it does not give us access to YouTube.
• YouTube connection. If you connect YouTube: your channel identifier, channel name and profile image address, the permission you granted, and your Google OAuth tokens, encrypted. Everything we store from YouTube is listed under YouTube and Google data.
• Twitch connection. If you connect Twitch: your Twitch user identifier, display name and profile image address, the permissions you granted, and your Twitch OAuth tokens, encrypted. See Twitch.
• Destinations. For a connected YouTube or Twitch channel, the destination's name and ingest server address, and for YouTube the identifier of the reusable live stream we create on your channel. Stream keys for YouTube and Twitch are read from the platform each time you go live and are never stored.
• Broadcast details. For streams you create in the app: title, description, audience and privacy setting, schedule, the options you choose (such as latency, DVR, "made for kids", ad breaks and category), each destination's status, broadcast identifier and watch link, and any error the platform returned.
• Thumbnails. If you set a custom thumbnail, the image passes through our server on its way to your YouTube broadcast. We keep only the address YouTube serves it from, not the image.
• Guest rooms. Your room's title and settings, its invite link (the link's code is encrypted), the email addresses you invite and whether each invite was opened or joined. See Guests.
• Your session history. What each session was called, when it ran, how long it was live, how much it recorded, the names you gave the destinations it went to, and how many guests were in it. See Your session history.
• Billing. If you subscribe, payments are processed by Dodo Payments (or, for a subscription bought earlier, by Razorpay). We keep your plan, subscription status and history, which of the two you pay through, invoice amounts and links, the type of payment method, whether the card was issued abroad and its country, your customer identifier there, the country used to price your plan (from your IP address at checkout), and copies of the payment notifications they send us. We never receive your full card or bank details.
• Session security. Hashes of sign-in codes and refresh tokens, used to keep you signed in and to detect token reuse.
• Feature rollouts. When the app or dashboard asks which new features are turned on for you, our server asks PostHog using your account identifier and email address, so a feature can be rolled out to some accounts before others.
• Service logs. Our API keeps short-lived operational logs, such as which request failed and why, to keep it running. Errors are reported to PostHog without your name, email, account identifier or location.

YouTube and Google data

Vidyst uses YouTube API Services. Connecting YouTube is optional: you only need it to stream to YouTube or use YouTube live chat in Vidyst. By connecting YouTube you agree to the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy.

The permission we ask for

When you connect, Google's consent screen asks you to grant one permission: https://www.googleapis.com/auth/youtube.force-ssl, which Google describes as letting us see, edit and permanently delete your YouTube videos, ratings, comments and captions. It is the narrowest permission that lets an app create and run live broadcasts and read and post live chat. We use it only for the features below; we do not upload, edit or delete your existing videos, comments, ratings or captions, except for the broadcasts Vidyst creates or you choose to run from Vidyst.

What we access and why

• Your channel. Its identifier, name and profile image, to show which channel is connected; and its subscriber count, to show new subscribers during a stream.
• Your live broadcasts. We create, schedule, update, start and end broadcasts for the streams you set up in Vidyst, and list the upcoming broadcasts on your channel (including ones scheduled in YouTube Studio) so you can pick one to go live on. This covers their title, description, privacy setting, scheduled time, thumbnail, latency, DVR, "made for kids", ad-break and category settings, and status.
• Your live stream ingest. We create one reusable live stream on your channel and read its ingest server address, stream key and health, so your Mac can send video to YouTube and show whether YouTube is receiving it.
• Live statistics. The current viewer count, views and likes of the broadcast you are streaming, to show them in the studio.
• Live chat. The messages on the broadcast you are streaming, including each sender's display name, channel identifier, profile image and badges (owner, moderator, member, verified), Super Chats and Super Stickers with their amounts, membership events, and messages YouTube removed. We also post the messages you send from Vidyst.

How it flows

Our server keeps the long-lived refresh token and never sends it to your Mac. Our server calls YouTube to connect your channel and to create and manage your broadcasts and live stream. For live chat, live statistics and channel details, our server gives your Mac a short-lived access token (valid for about an hour), and the app calls YouTube directly. All of these requests are encrypted in transit.

What we store, where, and for how long

• On our servers, while YouTube is connected: your channel identifier, name and profile image address; the permission you granted; your refresh token and current access token, each encrypted with AES-256-GCM; and the identifier and ingest address of the reusable live stream.
• On our servers, with your session and broadcast history: for each stream you ran from Vidyst, the title, description and settings you entered, the YouTube broadcast identifier, watch link, custom thumbnail address and status. This is kept for as long as your account, so your history stays complete, and is deleted with your account.
• Never stored by us: your YouTube stream key (read from YouTube each time you go live), your subscriber, viewer and like counts, the list of your upcoming broadcasts, and your live chat, except as described for guests below.
• Kept current, or deleted: your channel name and profile image address are re-read from YouTube each time the app checks your connection, and are deleted from our servers if they have not been refreshed for 30 days. Your access token is renewed as it is used and removed by our hourly clean-up once it expires; your refresh token is kept only while you stay connected; both are deleted the moment you disconnect. The broadcast identifiers, watch links and statuses in your stream history are your own record of the streams you ran, so they are kept with your account and deleted with it, or sooner if you ask us.
• On your Mac: live chat and live statistics are kept in memory only while the app is running and are gone when you quit.
• Shared with your guests: if guests are in your room while you are live, Vidyst shows them your live chat so they can read along. For each message, the room holds the sender's display name, the message text, its type and any Super Chat amount, never profile images or channel identifiers. The room keeps only the latest 100 messages and clears them when your stream ends.

How we share it

We do not sell YouTube data, share it with advertisers or data brokers, or use it for advertising, credit decisions or to train AI models. We share it only:

• with the guests you admit to your room, as described above;
• with the subprocessors that host our servers and database (Cloudflare and Neon), which store and process it only on our behalf;
• when the law requires it, or to protect the security of Vidyst and its users.

We do not transfer or disclose Google user data to third parties for any purpose other than the ones described in this policy.

Our analytics provider, PostHog, never receives your YouTube data. Usage events count things such as how many YouTube destinations a stream used, and error reports carry YouTube's error codes (for example "quota exceeded"), never your channel, broadcasts or chat. Our staff do not read your YouTube data unless you ask us to for support, it is needed for security or abuse investigations, or the law requires it.

How we protect Google user data

We treat your Google OAuth tokens and YouTube data as sensitive data. Security procedures are in place to protect the confidentiality, integrity and availability of your data, and we use encryption to protect it, as follows. The same measures apply to your Twitch data. See also How we protect your data.

• Encryption in transit. Every request between the app, our servers, our database and Google is sent over HTTPS/TLS. We never send Google data over an unencrypted connection.
• Encryption at rest. Your refresh token and access token are encrypted with AES-256-GCM before they are written to our database, each with a fresh random value and bound to your account, so an encrypted token copied anywhere else cannot be decrypted. The database itself is also encrypted at rest by our database provider.
• Key management. The encryption keys are stored as encrypted secrets in our hosting platform, separate from the database and from our source code. They are never sent to the app or to any third party.
• Least privilege. The long-lived refresh token never leaves our servers. Your Mac receives only a short-lived access token, valid for about an hour, and only for the features that need it. We request a single YouTube permission and use it only as described above.
• Access controls. Our database tables use row-level security and are readable only by our API's own database role, and our API returns your data only to requests authenticated as you. Access to our production systems is limited to the people who operate Vidyst, who use it only to run, secure and support the service.
• Data minimization. We store only the Google data listed above. Stream keys, live chat, viewer counts and your list of upcoming broadcasts are never stored, and Google data is never sent to our analytics provider.
• Prompt deletion. Disconnecting YouTube revokes our access at Google and deletes your tokens and channel details from our servers immediately. Expired access tokens and connection attempts are purged every hour, and a channel name and profile image address that has not been refreshed from YouTube for 30 days is deleted by the same clean-up.
• Incident response. If we learn of unauthorized access to your Google data, we will revoke the affected tokens, secure our systems, and notify you and the relevant authorities as the law requires.

Limited Use

Vidyst's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• We use Google user data only to provide and improve the user-facing features of Vidyst described in this policy, which you can see in the app.
• We do not use or transfer Google user data for targeted or personalized advertising, sell it, transfer it to data brokers or information resellers, or use it to determine credit-worthiness or for lending purposes.
• We do not use Google user data to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models, and we do not transfer it to third parties for that purpose.
• No person reads your Google user data unless you give us permission for a specific purpose such as support, it is necessary for security purposes such as investigating abuse, or it is required to comply with the law.

Cookies and device identifiers

Vidyst does not place cookies or read device identifiers on YouTube's behalf, and no third party serves content or advertising in Vidyst. The app keeps your sign-in in your Keychain and a random analytics identifier on your Mac, neither of which is linked to your YouTube data. Our websites use the first-party cookie described under Website and dashboard analytics.

Disconnecting and deleting YouTube data

• In Vidyst: disconnecting YouTube revokes our access at Google, and deletes the stored tokens, your channel details and the YouTube destination from our servers immediately.
• At Google: you can remove Vidyst's access at any time from your Google security settings page. We stop using the connection as soon as Google tells us access was removed.
• Everything: deleting your account deletes all YouTube data we hold, including your broadcast history. To ask us to delete only your YouTube data, email support@vidyst.com.

Twitch

If you connect Twitch, you grant Vidyst permission to read your stream key, manage your broadcast (title and category), and read and send chat as you. Our server keeps your encrypted tokens and gives your Mac a short-lived access token for chat. Your stream key is read from Twitch each time you go live and is never stored. Twitch chat comes directly from Twitch to your Mac, is kept in memory only, and is shared with your guests in the same way as YouTube chat. Disconnecting Twitch revokes our access and deletes the stored tokens. Twitch's handling of your data is described in the Twitch Privacy Notice.

Live chat

Chat messages, commenter names and profile pictures come directly from YouTube or Twitch to your Mac. They are kept in memory only while the app runs and are not stored by the app. They reach our servers only to show them to your guests, as described above. Hiding a message hides it only in Vidyst (and for your guests); messages you send are posted to the platform.

Guests

You can invite people to join your show from a browser at guest.vidyst.com. Guests don't need an account.

• What guests share. The name they enter (remembered in their own browser for next time), and the camera, microphone and screen they choose to share. Their browser asks for permission first.
• Audio and video. Relayed live through Cloudflare Realtime and never recorded or stored by us. The host, however, can show guests in their stream and recordings, which then follow the host's choices and the destinations' policies.
• Room state. While a call is running, our server holds who is in the room, their names, whether their camera and microphone are on, and who was removed. People are dropped from it shortly after they leave.
• Backstage chat. Messages sent in the room's chat are kept with the room, the latest 100 only, so guests who arrive later can catch up.
• Email invites. If the host invites a guest by email, we store the address with the room and send the invite through Resend. We use the address only for that invite.
• Security. Join attempts are rate-limited by IP address, which is not stored.

The guest join page's analytics are described under Website and dashboard analytics. Guests who want their invite email removed can ask the host or contact us.

Vidyst Remote for iPhone and iPad

Vidyst Remote is a free companion app that controls Vidyst on your Mac: going live, recording, switching scenes, the mixer and guests. It is a controller only. No camera, screen or recording video is sent to it, it has no account to sign in to, and it collects nothing about you. Its App Store privacy label is "Data Not Collected".

• Local network. The only permission the app asks for, and iOS asks the first time. It is used to find your Mac on the network you are both on and to send it your key presses.
• What it stores on your device. Once you pair: your Mac's name and address, an identifier for this device, and the key the two of them share, in the iOS Keychain, marked for this device only so it is never in a backup or in iCloud. On iPad, which keys you add to or remove from the deck are kept in the app's own preferences. Nothing else.
• What it exchanges with your Mac. Your key presses go to the Mac, and the Mac sends back what the studio is doing: whether you are live or recording and for how long, your destinations and their status, your scene, layout and overlay names, your audio channels with their names, mute state and fader positions, and the names of guests in your room. No audio or video is ever part of it. The app holds this in memory while it is open and loses it when you close it.
• Where it goes. Only to your Mac, directly, over your local network, encrypted with a key the two of them agreed on when you paired. It never travels over the internet, never passes through our servers, and we never see it.
• Pairing. Before a device can control anything, both screens show the same six-digit code and you have to allow it on the Mac. Each device gets its own key, and only devices you have allowed can connect. What the Mac keeps is listed under "Information stored on your Mac".
• No analytics on the device. The app has no analytics, crash reporting, advertising or third-party code, and makes no network connection other than to your Mac. "Try the Demo" on the connect screen runs entirely on your device.
• What the Mac records. If usage data is on in Vidyst on your Mac, two usage events mention the remote: that you turned the feature on or off, and that you removed a device. Neither says anything about the device or what you pressed. See App usage data.
• Ending it. Remove the device in Vidyst › Settings › Remote on your Mac, which deletes its key and disconnects it at once, or choose Forget This Mac in the app, which deletes the pairing from your device. Turning off Allow Vidyst Remote stops the Mac listening altogether.

Your session history

Your dashboard (studio.vidyst.com) shows you what you have been doing with Vidyst: hours live, how many sessions, guests hosted and how much you recorded. To show it, the app reports each finished session to our servers under your account: what you called it, when it started and ended, how long it was live, how many bytes it recorded, and the names you gave the destinations it went to, such as "YouTube" or the name of your own RTMP server.

Guests are counted, never named: a session keeps how many people joined it and how many were on stage at once, and each guest only as an unreadable hash that is unique to your account. Nothing else from a session is reported — no stream keys or server addresses, no scene or layout names, no file names or folders, no chat messages, and no audio or video.

A session is written to your Mac when it ends and sent in the background, so reporting never holds up or interrupts a show, and a session still reaches your dashboard after a crash or a week offline. This history is yours, is only ever shown to you, and is deleted with your account.

App usage data

This is separate from your session history above. To learn which parts of Vidyst are used and where it falls over, the app sends counts of what happens: layouts switched, minutes recorded, destinations added, guests admitted, errors hit, and how long things took. Each event carries your plan tier and facts about your Mac such as its chip, macOS version and screen count. Before you sign in, events carry a random identifier generated on first launch. Once you sign in, they carry your Vidyst account identifier instead, the app tells PostHog your account's email address and name once (and again if they change), and the earlier events from that install are linked to your account too, so we can see how people get from downloading the app to streaming and choosing a plan. On our side this joins the analytics from the account dashboard, which are already linked to your account (see Website and dashboard analytics).

The same channel carries error and crash reports: the type of error, where in the app it happened, a cleaned-up message and the app's stack trace. A crash is written to your Mac and sent on the next launch.

Apart from that one message with your email address and name, the app never sends file names or folder paths, stream keys, server addresses, scene or layout names, guest names, YouTube or Twitch data, or any chat message or media. Your IP address is discarded at our analytics endpoint rather than stored, and no location is derived from it. Because it is linked to your account once you sign in, we can find and delete it: email us and we will remove it. Usage from an install that never signed in stays tied only to the random identifier; deleting the app's preferences on your Mac issues a new one.

Turn it off in Vidyst › Settings › General › Privacy. Development builds never send anything. We use PostHog to collect and store this data.

Website and dashboard analytics

This website (www.vidyst.com), the account dashboard (studio.vidyst.com) and the guest join page (guest.vidyst.com) use PostHog to understand how they are used and where they break. They record the pages you visit, the buttons and links you click, how fast pages load (web vitals), errors in the page, and basic facts from your browser such as its type, screen size and the page that referred you. A first-party cookie keeps a random identifier so visits from the same browser can be counted together.

• This website and the dashboard may record sessions so we can see where people get stuck. Text you type is masked and never recorded, and the dashboard also masks your plan, payment and invoice details.
• When you sign in to the dashboard, these events are linked to your Vidyst account identifier, email address and name, along with what you do there, such as starting a checkout, changing plans or connecting a sign-in method.
• The guest join page is never recorded and is not linked to an account. It counts steps such as opening an invite, joining, sharing a screen or sending a chat message, but never the invite code, your name, chat messages or any audio or video.

How we use information

• To sign you in and keep your session secure.
• To create, start and end broadcasts on the platforms you connect, and show their chat and statistics.
• To run calls with your guests and send the invites you ask us to.
• To determine your plan, bill you, and unlock the features it includes.
• To show you your own session history in your dashboard.
• To understand how Vidyst is used, fix errors and roll out new features safely.
• To provide support and send important service messages.

We do not sell your personal information, use it for advertising, analyze your media, or use your data or content to train AI models. Where the law requires a legal basis, we rely on performing our contract with you (running your account, broadcasts and plan), our legitimate interests (security, analytics and improving Vidyst), your consent (connecting YouTube or Twitch, and the permissions your Mac and browser ask for), and our legal obligations (billing records).

Subprocessors

These companies process personal information on our behalf, under contracts that require them to protect it and use it only to provide their service to us:

Platforms you connect or stream to, such as YouTube, Twitch and your custom RTMP servers, are not our subprocessors. They receive the data needed to run your broadcasts and handle it under their own policies. We will update this list before adding a new subprocessor.

How we protect your data

We protect personal and sensitive data, including your account details, OAuth tokens, YouTube and Twitch data, and billing records, with these measures:

• Encryption in transit. All traffic between the app, our websites, our servers, our database, YouTube, Twitch, our subprocessors and your guests is encrypted with HTTPS/TLS. Guest audio and video are encrypted in transit through Cloudflare Realtime. Vidyst Remote's connection to your Mac is encrypted with TLS using a key unique to that pairing, which no one else can present.
• Encryption at rest. Platform OAuth tokens and guest link codes are encrypted with AES-256-GCM before they are stored, and our database is encrypted at rest by our database provider. Encryption keys are kept as secrets in our hosting platform, separate from the data and from our source code.
• Hashing. Sign-in codes and session refresh tokens are stored only as SHA-256 hashes, so they cannot be read back even from the database.
• Secure sign-in and sessions. Sign-in uses a browser-based flow protected with PKCE, and connecting YouTube and Twitch uses OAuth with PKCE. Session tokens rotate on every use, and reusing an old token ends the whole session.
• On your Mac. Your sign-in session and custom RTMP stream keys are kept in the macOS Keychain, which encrypts them and limits access to Vidyst.
• Access controls. Database tables use row-level security and are readable only by our API's own database role. Every API request is authenticated, and you can only reach your own data. Access to production systems is limited to the people who operate Vidyst.
• Payment data. Card and bank details are entered directly with Razorpay or Dodo Payments and never reach our servers.
• Abuse protection. Guest joins and room chat are rate-limited, and our hosting provider protects our servers against abusive traffic.
• Minimization and retention. We collect only what is listed in this policy, purge expired credentials every hour, and delete data when you disconnect a platform or delete your account.
• Subprocessors. The companies listed under Subprocessors are bound by contracts that require them to protect the data they process for us.
• Incidents. If we learn of a breach affecting your personal information, we will act to contain it and notify you and the relevant authorities as the law requires.

No system is perfectly secure, but we review and improve these measures as Vidyst grows. To report a security issue, email hello@vidyst.com.

Retention and deletion

We keep each type of information only for as long as described below. When the retention period for a type of data expires, we delete or destroy it. Deleted data may remain in our database provider's encrypted backups for a short period until they are overwritten.

• Expired sign-in codes, tokens and pending connection attempts are purged automatically every hour.
• Signing out revokes your session on our servers and removes it from your Mac.
• Disconnecting YouTube or Twitch revokes our access at the platform and deletes the stored tokens and channel details.
• Live chat mirrored to your guests is cleared when your stream ends.
• Your session history, broadcast history, destinations and guest room are kept for as long as your account, and are deleted with it.
• Information stored on your Mac stays there until you delete it, for example by removing the app's files in Application Support and its items in Keychain Access.
• Removing a device in Vidyst › Settings › Remote deletes its key from your Mac immediately. What Vidyst Remote stored on an iPhone or iPad is deleted when you choose Forget This Mac, and when you delete the app, though iOS may keep its Keychain item until the device is reset.
• To delete your account and the data we hold, email support@vidyst.com from the address on your account. We delete your account and all data we hold about you, including all Google user data, within 30 days of your request, and confirm by email. We may keep billing records where the law requires it.

Updates

The app checks for new versions in the background every few hours by downloading a small release file from downloads.vidyst.com, and can download and install updates for you. You can turn automatic checks and automatic installs off in Vidyst › Settings › General. Update checks send only the app's name and version in the request, with no account or install identifier. Background checks and update restarts wait while you are recording, streaming or have guests in the room.

This website

This site does not use advertising trackers. Cloudflare may process standard request logs, such as IP address and user agent, for security and reliability. Prices are shown in US dollars everywhere; this site does not use your location to set them.

Children

Vidyst, including Vidyst Remote, is not directed at children under 13, or under 16 where local law sets a higher age, and we do not knowingly collect their personal information. If you believe a child has given us information, contact us and we will delete it.

International transfers

We and our subprocessors may process information in countries other than yours, including the United States and India. Where required, we rely on appropriate safeguards for these transfers, such as standard contractual clauses.

Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal information, to withdraw consent, or to object to or restrict certain processing. Contact us and we will respond within a reasonable time, and within any period the law sets. You may also complain to your local data protection authority.

Changes

If we make material changes to this policy, we will update the date above and, where appropriate, notify you in the app.

Contact

Questions about privacy, or a request about your data? Email hello@vidyst.com. See also our Terms of Service and Support.