Privacy Policy

One policy for Kevv and Keystory, both built and operated by Kevv AI Labs Inc. It covers kevv.ai, the app.kevv.ai workspace, the keystory.kevv.ai web app and the Keystory Chrome extension. Plain English; no dark patterns.

1 Who we are and what this covers

Kevv AI Labs Inc., a Delaware corporation ("Kevv AI Labs", "we", "us"), operates Kevv, a bilingual real estate video studio for individual real estate professionals at kevv.ai and app.kevv.ai, and Keystory, a listing content studio at keystory.kevv.ai with the Keystory Chrome extension (together, the "Services"). This policy explains what we collect, how we use and share it, and the choices you have.

REscript (rescript.kevv.ai), which emails daily real estate scripts to subscribers, is also operated by us but is covered by its own privacy policy.

Effective date. This version (version 2026.5) was published on October 31, 2026 and takes effect on December 15, 2026. Until then, the policy that applied to an account that existed before this version was published continues to apply to it: the earlier version of this policy (version 2026.4) from the date it took effect for that account, and before that date, the policy of each product.

2 One account across our products

Kevv, Keystory and REscript are operated by the same company and use the same sign-in system (Supabase), so the same email address or Google account works for each, and signing in on one of our sites can sign you in on the others in the same browser.

Each product keeps its own data and plans. Your Kevv client list, videos and uploads are not shared with Keystory or REscript, and your Keystory listings, reports and videos are not shared with Kevv or REscript. Kevv and Keystory share two things, described below: your brand card, and a Keystory voice you choose to copy into Kevv. The first time you open a product while signed in, it creates its own account record from your sign-in identity (your email address and user ID).

Credits. You can spend your Keystory credits in Kevv. When you use it, Kevv sends Keystory your user ID and your sign-in token, the kind of item (for example, a narrated property video or a studio video), the number of credits for a studio video, a reference number and a short label that appears in your Keystory wallet activity (for a studio video, its title), and Keystory tells Kevv your credit balance and plan. No client records or voice data is shared for this.

Brand card. Kevv and Keystory use one brand card: your display name, company, phone number, license number and licensing state, brand color, headshot and logo. Keystory stores it. When you open Kevv's onboarding or settings, Kevv sends Keystory your user ID and sign-in token to read the card, and an edit you make in either product updates the same card. The first time Kevv reads it, details you had already entered in Kevv fill any fields that are empty in Keystory. Kevv keeps a copy of your headshot and logo to place on the videos you make in Kevv. No client records, listing content or voice data is shared for this.

A Keystory voice you copy into Kevv. If you set up a cloned voice in Keystory, you can copy it into Kevv instead of recording again. This happens only when you choose "Use my Keystory voice" in Kevv's voice settings and agree to Kevv's voice notice. Kevv then receives your Keystory voice sample for that language, its transcript, and the version and date of the consent you gave in Keystory, and keeps its own copy. From then on the two voices are separate: deleting your voice in one product does not delete it in the other.

3 What Kevv collects

Information you provide.

Account and profile: your email address and user ID from our sign-in provider, and the profile details you add: legal and preferred name, phone number, real estate license number, brokerage name, specialties and service areas, and profile photo. Your brand card is shared with Keystory (see One account across our products).
Client list: for each client you add, their name and preferred content language, and the email address, phone number and WeChat ID you enter. Kevv uses these details only so you can send that client your videos. It no longer keeps notes, activity, search criteria, budgets, stages or other client details (see Kevv features removed in October 2026).
Videos: the property videos you create, including their storyboards, scripts, versions and formats; for each delivered version, a record of how each shot was made (its type, the listing photo or upload it came from and a fingerprint of that image, the AI model, settings and prompt, and the provider's job ID) and the voice and music used; the styles you save (music, captions, pacing, voice, brand card and language); and, for each video you email, a record of the send with a one-way hash of the recipient's address.
Uploaded photos and footage: where Kevv offers uploads, the photos and video clips you upload, Kevv's converted copies of them, their file details (such as type, size and length), and your confirmation that you have the rights and consents to use them. Kevv removes location data (GPS EXIF) and other metadata from the photos and clips it keeps, keeps clips without sound, and deletes the original file once it is converted. Your uploads can show the property and, if you include them, people. If a generated shot in a video you share was made from a photo you uploaded, the video's share page shows that photo, as cropped for the shot, to anyone with the link.
News content: the topics you research and the scripts and news videos you create.
Voice data: audio you dictate to the assistant (converted to text and not stored) and, only if you choose to create one, a voice sample for your cloned voice, recorded in Kevv or copied from Keystory at your request (see Voice recordings and cloned voices).
Payment information: Kevv does not currently take payments in the app. If you buy a paid Kevv service, Stripe processes the payment and we do not store your full card number.
Communications: messages you send us.

Information collected automatically.

Device and usage: browser type, operating system and device type as sent by your browser; pages and features used, actions taken and timestamps, as recorded in our service logs and activity history. In Kevv this includes the steps of each video project (such as created, storyboard ready, edited, confirmed, delivered, shared or sent to a client) with their times, credits and counts, which we use to measure and improve the studio; these records do not include the content of your videos or your clients' details.
Logs: IP addresses, sign-in times, server logs, error reports and diagnostic data.
Share link activity: when someone opens a video share link you send, we record the view and what they do on the page (such as playing or downloading the video or tapping your contact details), together with their browser's user-agent string (which shows the browser and device type), a one-way hash of their IP address and a random ID kept in their browser.
Cookies and local storage: a sign-in session cookie, and your browser's storage for preferences such as language, map position and search filters. The kevv.ai website sets no cookies. We do not use analytics or advertising cookies.

Information from other sources.

If you sign in with Google, the basic profile information described in Google sign-in data.
Property listing information from OneKey MLS through our listing data service.
Until October 2026, when you added a client with an email address, or a seller or landlord client with a property address, Kevv automatically looked up additional information about that client from People Data Labs and BatchData (see Service providers). Kevv no longer does this, and the information it saved has been deleted (see Kevv features removed in October 2026).

4 Kevv features removed in October 2026

On October 30, 2026, Kevv became a real estate video studio and removed these features: Buyer Reports, including their public links and PDFs; client activity records, notes, search criteria, property matching and alerts, saved searches and their updates, CSV contact import and AI client summaries; showing tours and tour links; MLS share links and Collections; market insights and agent performance figures; and live voice conversations with the assistant, which used an OpenAI realtime model through Microsoft Azure OpenAI. Kevv no longer collects, shows or uses data for them.

We have deleted the data these features collected. It included:

client activity records and notes; search criteria such as budgets, preferred areas, property types, must-haves and move-in dates; stages, tags and follow-up dates; AI-written client summaries; and the other client details Kevv no longer keeps, such as birthdays, job titles, companies, buyer, seller and landlord property details, and the information from the earlier People Data Labs and BatchData lookups;
listing matches, property alerts, saved searches and their updates;
showing tours and their stops;
MLS share links and Collections, with their view records and the feedback clients left on them;
Buyer Reports, their PDFs and stored files, and their share link records;
copies of this data in your assistant conversation history and the records of the assistant's actions, including transcripts from live voice conversations.

When it was deleted. We permanently deleted this data from our database when we published this version on October 31, 2026, and the stored Buyer Report files within 14 days after that. Copies in our database backups expire within 14 days after the deletion. Your account, client list (names, content language and contact details), videos, news content, voice, brand card and credits are kept.

5 What the Keystory web app collects

When you sign in and use keystory.kevv.ai, we store:

Account: your email address and a user ID from our sign-in provider, Supabase. If you sign in with Google, Supabase also receives your Google name and profile picture; Keystory does not use them.
Listings & reports: the listing data you save, the reports you build (including any client name and brief you enter), and the agent profile information you add (name, company, phone, email, headshot, logo); the profile details on your brand card are also used by Kevv (see One account across our products).
Listing links from your phone: when you share or paste a listing link into Keystory on a phone, we store the link and the address it contains as a draft. Keystory does not visit the listing page; the Chrome extension fills in the details when you open that listing on a computer.
Voice recordings: if you record or upload a voice sample, see Voice recordings and cloned voices.
Billing: Stripe customer and subscription identifiers, order status, and your credit ledger. Card details are handled by Stripe and never reach Keystory.
Engagement on share pages: on public report and video share pages (e.g. /share/abc123) we record page views, scroll depth, listing clicks, contact button clicks, video plays, and time spent, plus the viewer's browser type and referring page, against an opaque first-party session cookie. If a viewer marks a listing as interesting or not, or sends you a question, we store that response. We do not store viewers' IP addresses or run third-party analytics SDKs.

6 What the Keystory Chrome extension collects

The extension runs only on real estate listing pages of seven specific sites: Zillow, StreetEasy, Redfin, Realtor.com, Homes.com, Compass, and OneKey MLS. On a listing page it reads the publicly visible listing data, such as address, price, beds, baths, square footage, year built, lot size, property type, taxes and HOA fees, parking, school ratings, listing status, MLS number, days on market and price history, open houses, amenities, photos, the listing description, and the page URL, and sends it to your Keystory account at keystory.kevv.ai. On Zillow it may also request the listing's details from Zillow's own site in that tab.

Keystory also saves the listing's photos: the photos that listing page itself showed, at the size the page showed them. From version 2.0.0, if you click Allow on the extension's "Save photos from your browser" card, Chrome lets the extension read the listing sites' photo servers; it then downloads each photo without your cookies and uploads it to your Keystory account in the background. Without that permission, or for any photo that cannot be uploaded from your browser, Keystory's servers copy that same photo address instead. Keystory's servers never visit the listing page itself and never request any other size or version of a photo.

The extension does not read or transmit anything on any other website. It does not run on banking, email, social media, or any non-listing page.

The extension stores a few small things in your browser via chrome.storage: your auto-save on/off preference, and a list of listing URLs it has saved with the time saved (used to avoid duplicate saves). From version 1.9.0 it also remembers whether Keystory last reported you signed in or out, only until you close Chrome. Version 1.9.0 and later remove listing URLs older than 30 days whenever the extension starts and each time it saves a listing; earlier versions remove them the next time they check a listing page. Version 2.0.0 also keeps a short list of photos waiting to upload (the photo address and Keystory's ids for it), removed after each upload and within 30 minutes, and, until you close Chrome, the links of homes you saved from your phone that its popup showed you.

If you are not signed in to keystory.kevv.ai, Keystory rejects any save the extension sends and stores nothing. From version 1.9.0, the extension asks Keystory whether you are signed in before each automatic save, and while Keystory reports you signed out it reads and sends no listing data. From version 2.0.0 the same check comes before photo uploads, and a signed-out answer deletes any uploads the extension had queued.

7 What we don't collect

No browsing history outside the seven supported listing sites. Kevv has no browser extension.
No personal data about your clients beyond what you choose to enter or upload. (Kevv's automatic client lookups ended in October 2026.)
No third-party advertising or marketing trackers, and no analytics or advertising cookies.

8 Voice recordings and cloned voices

Both products can narrate your videos in your own voice. This is optional and starts only when you record or upload a voice sample in that product's settings, or copy your Keystory voice into Kevv, and agree to the notice shown there. Each product keeps its own voice: a voice set up in Kevv is not used by Keystory, and a voice set up in Keystory is not used by Kevv unless you copy it into Kevv; the copy is then Kevv's own and is deleted separately. We use your sample and cloned voice only to narrate videos that you create; we do not use your voice for anyone else, and we do not use voice samples to train our own AI models.

Kevv

Dictation (speech-to-text): when you use the microphone in the assistant's message box, your browser records what you say (up to one minute at a time) and Kevv sends the recording to Microsoft Azure OpenAI, which converts it to text. Kevv does not store the recording. The text appears in the message box for you to review; if you send it, it is saved in your assistant conversation like a typed message. What the assistant does for you, such as starting a video, is saved like any other change you make, together with a record of the action. Kevv no longer offers live voice conversations with the assistant (see Kevv features removed in October 2026).
Setting it up: you record yourself reading a short script in Settings → Your cloned voice (English and Chinese are set up separately), or copy the voice you set up in Keystory for that language, and confirm the consent shown there.
What we keep: your recording and a cleaned-up copy, stored in private Cloudflare R2 storage; the script you read; an automatic transcript and quality measurements used to check the recording; and the version and time of your consent.
Narrated property and news videos: our own GPU servers in Microsoft Azure (West US 2) run open-source models: one checks your recording, and another generates narration from your sample each time a narrated property or news video in your voice is made. For these videos your sample is not sent to an outside AI provider.
Cinematic property videos: when a Cinematic video uses your own voice, we send your sample to MiniMax, which creates a cloned voice from it, keeps that voice on its servers so your later Cinematic videos can reuse it, and reads your narration with it. A Cinematic video in a standard voice sends MiniMax the narration text only. We use MiniMax's mainland China service, so your sample, cloned voice and narration text are processed and stored in China. A voice saved before this notice is used for Cinematic videos only after you allow it in Settings → Your cloned voice.
Deleting it: in Settings → Your cloned voice, choose Revoke. We delete the recording and its cleaned-up copy from storage (retrying automatically if a deletion fails), ask MiniMax to delete the cloned voice and the uploaded sample if your voice was used for a Cinematic video, and keep a record of your consent and its revocation. A voice you copied from Keystory is deleted only from Kevv; delete it in Keystory separately. Videos already made in your voice stay in your account; you can turn off their share links at any time, and you can ask us to delete them by emailing support@kevv.ai.
Standard voice: videos narrated in a standard voice are voiced by Microsoft Azure OpenAI from the video script. No recording of your voice is used.

Keystory

What we keep: your voice sample (and a cleaned-up copy), stored privately in Cloudflare R2; the script you read and an automatic transcript of the sample, used to check that it is clear enough; and the date and version of the notice you agreed to when you saved it. You agree once, when you record or upload the sample; it then narrates your Narrated and Cinematic Tours without asking again, and you can choose the standard voice for any video.
Narrated Tours: your cloned voice is generated on our own servers in Microsoft Azure with an open-source text-to-speech model. The sample is not sent to an outside AI provider for these videos.
Cinematic Tours: when a Cinematic Tour uses your own voice, we send your sample to MiniMax, which creates a cloned voice from it, keeps that voice on its servers so later Cinematic Tours can reuse it, and reads your narration with it. We use MiniMax's mainland China service, so your sample and cloned voice are processed and stored in China.
Deleting it: in Settings → Voice, choose Delete (or record a new sample to replace it). We ask MiniMax to delete the cloned voice and the uploaded sample, then delete our stored copies. If the request to MiniMax fails, Settings shows the error and you can try again. We keep a record that the voice was removed, and videos you already made stay until you delete them. Samples have no automatic expiry while you keep them.

9 Google sign-in data

Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can sign in to Kevv and Keystory with Google or with a one-time link sent to your email address. Sign-in is handled by our authentication provider, Supabase. If you choose Google, Google shares only basic profile information with Supabase: your name, email address, and profile picture. Kevv and Keystory keep only your email address and a user ID from it. Neither product requests permission to read, send, or manage your Gmail messages, contacts, or calendar.

We use this information only to create and secure your account and to sign you in. We do not:

sell, rent, or lease Google user data to any third party;
use Google user data for advertising, market research, or building user profiles for ad targeting;
share Google user data with other users or any unrelated services;
train general-purpose AI or machine learning models on Google user data.

10 Email we send, and your mailbox

Kevv does not connect to your Gmail, Outlook, Microsoft 365, or any other mailbox, and neither does Keystory. We do not read your email and do not send email from your email account. Neither product provides an inbox or SMS messaging. We send email:

when you request a one-time sign-in link (sent by our authentication provider, Supabase);
for service and transactional messages: receipts, billing and security notices, and notices about your own work (for example, that a Keystory video is ready or that a client asked a question on your report, including the question);
for product updates, tips, and promotional messages about Kevv, Keystory and other Kevv AI Labs products, as described in our Terms; every such email has an unsubscribe link;
in Kevv, when you choose to send a client a link to one of your videos: Resend delivers it to the address you enter, and replies go to the email address on your Kevv account.

11 How we use the data

To run the Services: store your library, client list and uploads, run property search, render reports, share pages, PDFs, and videos, research news and draft scripts, and run the assistant. Kevv uses your uploads only to make and show your videos and does not use them to train our own AI models.
To show you which listings, reports, and videos your clients engaged with.
To process payments and keep your credit balance.
To detect and fix bugs, fraud, abuse, and rate-limit violations, and to secure accounts.
To email you, as described in Email we send, and your mailbox.
To improve the products, mainly from aggregated usage patterns.
To meet legal obligations and respond to lawful requests.

We do not sell your data and do not share it with advertisers.

12 Service providers (sub-processors)

These companies process personal information on our behalf to run the Services. They may use it only to provide their services to us.

Microsoft Azure — hosting, PostgreSQL databases, logs, and the GPU servers that create cloned-voice narration. Kevv runs in the United States (West US 2; database in West US 3) and also uses Azure Maps for maps, place search, and geocoding: your browser sends map searches to Azure Maps directly, with your IP address. Keystory runs in the United States (North Central US region). Data: all account and product data.
Microsoft Azure OpenAI — AI models from OpenAI and DeepSeek hosted by Microsoft (we do not send data to OpenAI or DeepSeek directly). In Kevv: the assistant (your messages, and the property, video, and page details the assistant needs, including a client's name and email address when you ask it to send a video), dictation (the audio you record, converted to text), video storyboards, scripts, and planning (listing facts and photos, and the photos and still frames from video clips you upload), standard-voice narration, news scripts, and news video storyboards and illustrations. In Keystory: every video (listing facts and photos for the storyboard and script; the narration text for Narrated Tours in the standard voice; your headshot, name, and company for the video cover) and report copy you generate (listing facts, your agent profile, and any client name and brief). These run as Microsoft "Global Standard" deployments, so Microsoft may process a request in any region where the model is available, including outside the United States.
MiniMax (mainland China) — AI video generation. Keystory Cinematic Tours: listing photos, camera directions, and the narration text, plus your voice sample when a Cinematic Tour uses your own voice (see Voice recordings and cloned voices). Kevv Cinematic property videos (videos with generated shots): the listing photos or photos you upload that a generated shot is made from, camera directions and the narration text, plus your voice sample when a Cinematic video uses your own voice, with no client information.
Supabase — sign-in for Kevv, Keystory, and REscript (Google or a one-time email link), including sending sign-in emails. Data: your email address, your Google name and profile picture if you use Google, and sign-in records such as times and IP addresses.
Google — "Sign in with Google"; distribution of the Chrome extension; and Google Fonts, which your browser loads from Google in Kevv (Google receives your IP address).
Stripe — Keystory subscription and credit-pack payments, invoices, receipts, refunds, and payment disputes. Receives your account email with your first purchase. We keep payment identifiers and entitlement records; Stripe processes your card details. Stripe would also process any paid Kevv service.
Cloudflare — DNS and edge delivery for kevv.ai, app.kevv.ai, and keystory.kevv.ai, and R2 file storage. Kevv: private storage for voice samples, your videos, and the photos and video clips you upload, and public storage for profile photos and files from earlier versions of Kevv. Keystory: a private bucket for voice samples and work-in-progress files, and a public bucket for listing photos, headshots, logos, legacy flyer images, and finished videos and their covers. Files in public storage can be opened by anyone who has their link.
Resend — email delivery. Kevv: the emails you send to clients (the client's email address, the video title, often a property address, the link, and your email address as the reply-to address). Keystory: product update and promotional emails, and notices to you about your own work (for example, that a video is ready or that a client asked a question on your report, including the question). Receives the recipient's email address and the message content.
Mapbox (Keystory) — address geocoding, route planning, and map images. Map images on report share pages load from Mapbox, which receives the viewer's IP address.
Tavily (Kevv) — web search for news research. Data: the search topics you or the assistant enter.
People Data Labs and BatchData (Kevv, until October 2026) — earlier versions of Kevv sent a new client's email address to People Data Labs to look up public professional information (such as job title, company, phone number, and professional profile links), and a seller or landlord client's property address to BatchData to look up public property records and owner contact information. Kevv no longer sends them any data; information already saved with a client has been deleted with the other removed client details (see Kevv features removed in October 2026).

Property listing information in Kevv comes from OneKey MLS through our listing data service. Kevv sends it search criteria and listing IDs, not your client records.

14 Data security

Encryption: data travels between your browser and our servers over HTTPS, and our databases and file storage are encrypted at rest by our cloud providers.
Isolation: your records are visible only to you; public pages show only what you choose to share.
Sign-in: Google sign-in and one-time email links are handled by our authentication provider. We never receive or store your Google or email account password, and sign-in session cookies are HttpOnly and Secure.
Access: access to production systems is limited to the people who need it to operate and support the Services.
Hosting: our servers run on Microsoft Azure in the United States.

No system is perfectly secure, and we cannot guarantee that your data will never be accessed without authorization.

15 Data retention & deletion

Keystory listings, reports, videos, and engagement events stay in your account until you delete them or close your account, with one exception: when your Free listing library is full, saving a new listing automatically deletes your oldest saved listing that you did not add by hand and that is not used in a report, legacy flyer, or video, and tells you which one it replaced. Pro libraries are not automatically cleared (see the Terms). When a listing is deleted, by you or to make room in a Free library, Keystory also deletes the photos it saved for that listing within a day, unless another of your listings or videos still uses them.
Kevv client list (names, content language and contact details) stays while your account is active and is deleted or anonymized within 90 days of account closure. Data from the features Kevv removed in October 2026, including information from earlier client lookups, is deleted as described in Kevv features removed in October 2026.
Kevv uploads stay until you delete them, the video project they belong to, or your account. A deleted upload is removed from storage within 30 days; videos you already made with it do not change, including photos from it shown on their share pages. Uploads that fail or are never completed are deleted automatically within 7 days. When you close your Kevv account, your uploads are deleted within 30 days of your request.
Kevv video records: the record of how each shot was made stays with its video. Studio usage records and share link activity stay while your account is active (share link activity is also deleted with its share link) and are deleted or anonymized within 90 days of account closure.
Account data stays while your account is active, plus up to 30 days after a deletion request to allow for recovery.
Voice: dictation audio is not stored. Voice samples are kept until you delete or revoke them (see Voice recordings and cloned voices).
Logs: server logs are kept for up to 90 days.
Legal holds: data may be kept longer when the law, a regulation, or legal proceedings require it.

Neither product offers account deletion in its settings yet. Email support@kevv.ai from the address on your account to request account deletion or a data export, and tell us whether it covers Kevv, Keystory, or both. Closing one product's account does not close the other unless you ask. We'll action it within 30 days.

16 Your rights & choices

If you're in the EU/UK (GDPR), California (CCPA/CPRA), or another place with privacy laws, you have the right to access, correct, port, or delete your data, and you may have the right to restrict or object to some processing. Wherever you live, you can:

ask for a copy of your data in a portable, machine-readable format (CSV or JSON);
ask us to correct or delete your data;
delete your cloned voice at any time in the product's voice settings;
remove our access to your basic Google profile in your Google Account settings;
unsubscribe from promotional emails (service messages such as security notices still arrive);
control cookies through your browser settings.

To exercise any of these rights, contact us at support@kevv.ai. We will acknowledge your request within 10 business days and fulfill verifiable requests within 45 days (extendable by another 45 days for complex requests, with notice to you); account deletion and export requests are actioned within 30 days. We will not discriminate against you for exercising your privacy rights.

17 California privacy rights (CCPA/CPRA)

This section applies to California residents and supplements the rest of this policy as required by the California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020.

Categories of personal information collected in the preceding 12 months:

Identifiers: name, email address, phone number, IP address, and account and user IDs.
Commercial information: the services you use, purchases, subscriptions, and credit activity.
Internet or electronic network activity: feature usage and interaction data on our sites, and engagement on the share pages you send.
Professional information: brokerage name, real estate license number, and professional role; and, for Kevv clients, professional and property-record information obtained from enrichment providers until October 2026.
Audio and visual information: dictation and, until October 2026, Kevv voice assistant audio (processed in real time, not stored), voice samples you choose to provide for your cloned voice, headshots, profile photos, and logos you upload, and photos and video clips you upload to Kevv, which can show people.
Inferences: for Kevv, until October 2026, property preferences and search criteria the assistant extracted from your notes and conversations, listing matches, and AI-written client summaries.

Right to know: you can ask what personal information we have collected about you, its sources, why we collected it, the categories of third parties we share it with, and the specific pieces of information.
Right to delete personal information we collected from you, subject to exceptions in the law (for example, completing a transaction, detecting security incidents, or complying with legal obligations).
Right to correct inaccurate personal information.
Right to opt out of sale or sharing: we do not sell your personal information and do not "share" it for cross-context behavioral advertising, so there is nothing to opt out of, but we will honor any such request.
Right to limit use of sensitive personal information: we use sensitive personal information only to provide the Services you request.
Non-discrimination: we will not deny you service, charge different prices, or provide a different quality of service because you exercised these rights.
Authorized agents: you may have an authorized agent submit a request; we will verify your identity and the agent's authority (for example, a signed authorization or power of attorney).

California residents may submit requests by emailing support@kevv.ai with the subject line "California Privacy Request." We will verify your identity before fulfilling a request and respond within 45 days.

18 Additional U.S. state privacy rights

If you live in Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, or another U.S. state with a comprehensive privacy law, you may have the right to confirm whether we process your personal data; to access, correct, or delete it; to get a portable copy; and to opt out of targeted advertising, the sale of personal data, and profiling in furtherance of decisions that produce legal or similarly significant effects. We do not sell personal data or use it for targeted advertising. To exercise these rights, contact support@kevv.ai. If you disagree with our response, you can appeal by contacting us again, or complain to your state's Attorney General.

19 Google API Services User Data Policy compliance

The use and transfer to any other app of information received from Google APIs by Kevv and Keystory will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

we use Google user data only for the purposes described in this policy and as permitted by the Limited Use requirements;
we transfer Google user data to third parties only when necessary to provide or improve user-facing features that are prominent in your use of the Services, with your affirmative consent, for security purposes (for example, investigating abuse), or to comply with applicable law;
we do not use Google user data to serve advertisements;
we do not allow humans to read Google user data unless we have your affirmative agreement for specific data, it is necessary for security purposes or to comply with applicable law, or the data has been aggregated and anonymized for internal operations.

20 Data breach notification

If a security breach affects your personal information, we will investigate promptly; notify you by email or a prominent notice in the Services without unreasonable delay and within the time limits required by law, describing what happened, the data affected, what we have done, and what you can do; notify regulators where the law requires; and take reasonable steps to limit the harm, such as ending compromised sessions.

21 Children

Kevv and Keystory are tools for real estate professionals. They are not directed at anyone under 18, and we don't knowingly collect data from minors. If we learn that we have collected data from a child, we will delete it. If you believe a child has given us personal information, contact support@kevv.ai.

22 International data transfers

Our servers are in the United States. If you use the Services from outside the United States, your data is transferred to, stored, and processed in the United States. Some service providers also process data in other countries: Microsoft may process AI requests in Azure regions outside the United States (see Service providers), and MiniMax processes Keystory Cinematic Tour photos, narration text, and own-voice samples, and Kevv Cinematic video photos (including photos you upload), narration text and own-voice samples, in mainland China, where it also stores the cloned voices it creates for both products. By using the Services, you acknowledge and consent to these transfers. We take steps to protect your data in line with applicable data protection laws.

23 Changes to this policy

If we change anything material, we'll update the version and dates at the top of this page, email the address on your account, and show a notice in the product or on this page at least 30 days before the change takes effect. Kevv may also ask you to accept the updated policy when you next use it. If you keep using the Services after the change takes effect, the updated policy applies; if you do not agree, stop using the Services before then.

24 Contact

Kevv AI Labs Inc., a Delaware corporation
1111B S Governors Ave STE 41494, Dover, DE 19904, US
support@kevv.ai

We aim to respond to all privacy inquiries within 10 business days.