Privacy policy: we don't sell your information or train AI on your photos.
Updated 10 November 2026
Viara Studio is operated by Viara Studios, 9631 79 St, Edmonton, Alberta. This policy follows Canada's PIPEDA and Alberta's PIPA, in plain words.
What we collect
- Account details: your email, name, brokerage, phone, board, headshot and brand kit, which you give us to put on your outputs.
- Listing content: the photos you upload, listing facts you type, and everything the studio makes from them: staged versions, videos, scripts, captions, exports.
- Campaigns: your answers to a campaign's questions, the posts we write from them, and when each is to go out. If you ask us to email you each post, we send a reminder on its day. The link in it opens that post's page for seven days without signing in, and a second link pauses the campaign's emails for fourteen. Our database keeps only a one-way code of each link, never the link itself, and deletes the code a month after the link stops working; the link itself is held by the email that carries it and by the background job that sends it (Resend and Inngest, under Where it lives). The page shows that post's words and photo to anyone who has the link, and notes when you tell us you posted, moved or skipped the post. Once a week, on Monday morning, if something of yours went out or was shared in the week before, we email you one question: did anyone get in touch because of your posts? Your answer, and the line you may add after a yes, stay with your account and are not shown to anyone else, your team included; they are used for the count on your campaign cards and for nothing else. The link in that email opens the question for seven days without signing in, and is held the same way as the others. The email also has a link that stops it, which works for a year without signing in, and a switch in Settings, under Profile and brand kit, does the same; once you stop it we send no more of it, and we keep one row that says so. The photos you send for a campaign are ones you took on your phone, so they may show you, your clients or a place. Your phone writes where it was taken, and what camera it was, into each file; we remove that, and everything else it wrote, when we make our copies, and we delete the file you sent as soon as we have them (within two days, if your connection drops on the way). They are kept in your own folder of our storage, are sent to no AI model, and go to the accounts you connect only on the post that uses them. A photo of a client is used only if you ticked their yes. They are deleted with the campaign. A short video you add to a post you chose to film is treated the same way. Your phone writes where and when it was filmed, and what phone it was, into the file's tags; we copy the picture and the sound, as they are, into a new file that has none of those tags, keep it only if none is left in it, and delete the file you sent as soon as that is done (within two days, if your connection drops on the way). It is kept in your own folder of our storage, is sent to no AI model, goes to the accounts you connect only on the post that uses it, and is deleted with the campaign. The page of a post that we email you shows the card's lines and our words for it, never the video.
- Connected accounts: the platform, handle and an identifier for each social account you connect. Access tokens are held by Zernio, not by us.
- Usage and billing: which features ran on which listing and what they cost us, your plan, and Stripe's customer and subscription identifiers. We never see your card number.
- Help conversations: what you ask Kiki, the studio's help chat, and what she answers, and any problem report you send us, with the page you were on, your browser and the errors the page showed. We keep them with your account, to help you and to improve the guide she answers from. On the public site and the sign-in pages, Kiki answers visitors too: we keep what a visitor asks and her answers, with the page and a one-way code made from the connection's IP address, which limits how much one connection can ask. They are not connected to an account.
- Technical: server logs with IP addresses and timestamps, kept for security and debugging.
- Visits to the public site: counted by Google Analytics and by Vercel, and reported to Meta by its Pixel, as set out below. We do not connect a visit to your account. The pixel's identifiers from the browser an account is made in are kept with it until its address is confirmed, to tell Meta that an account was opened, and we do not tell Meta whose.
Why we use it
To make the outputs you ask for, to answer your questions about the studio, to bill you, to send you the messages the product needs (sign-in links, a render finishing, a lead arriving), and to keep the service secure. On the public site we count visits, to see which pages are read and how people find them, and we tell Meta which pages were visited, and when a visit ended in an account whose address was confirmed, to measure our advertising on Facebook and Instagram and to choose who is shown it. We do not sell personal information and we do not use your photos to train models.
Where it lives
We keep your account, your listings and your files in Canada, in Supabase's ca-central-1 region, and videos render in AWS's Canadian region. Some processing happens outside Canada with the services below, which act as our sub-processors under contract, except the mail, map, neighbourhood and search services at the end of the table: those work under their own terms. The mail services, ImprovMX, Gmail and Microsoft 365, carry and hold the email you send us, Kiki's problem reports among them; the map, neighbourhood and search services are sent only a listing's address, its position on the map, or the web address of a page you have published. What a service is sent is handled where that service is, and some of it is kept there: the table says what each one is sent, and what Fish Audio, Zernio, Stripe, Resend, Inngest, Railway, ImprovMX and Gmail hold.
When a photo is staged, retouched or turned into a clip, it is sent to the AI provider that does the work. The provider keeps the photo, and the picture or video it makes from it, only as long as it needs to: to do the work, to hand back the result and to guard against misuse. Then it deletes them, under its own terms. A script, a caption, a description or a question to Kiki is sent to an AI provider as text, and kept under that provider's terms. A question to Kiki and a rewrite by Improve with AI go only to hosts that OpenRouter lists as neither storing what they are sent beyond the request nor training on it. With a question to Kiki in the studio goes what she is told about your account to answer it: your name, your plan, the page you are on, your listings' addresses, your connected social accounts and your recent failed jobs. A visitor's question on the public site goes with the page it was asked on, and nothing else.
| Service | Location | What it does with your data |
|---|---|---|
| Supabase | Canada (ca-central-1) | Database, sign-in, and storage of your photos, videos and exports |
| Vercel | United States, with a global edge network | Hosting the web app and running its server code |
| Amazon Web Services | Canada (ca-central-1) | Rendering videos and carousel stills (Remotion on AWS Lambda) |
| OpenRouter | United States | AI text, vision, image, video and music generation: room recognition, staging, scripts, captions, the posts of a campaign (written from your answers to its questions, which can name people and places, your name, brokerage, province and sign-off, any phone number or email address you choose to show in a post, and up to three of your own posts as a sample of your voice; never a photo or a video), motion clips, music, and the answers of Kiki, the studio's help chat |
| fal | United States and other countries | Motion clips: the tall camera moves (push in, pull back, close in on a detail, and the drifts) are made by H3 Max, fal's own version of MiniMax's H3 model, on fal's servers. fal keeps neither the photo nor the clip beyond the request, and deletes the clip an hour after it is made |
| Fish Audio | United States | Narration: the script is sent as text and returned as audio. If you clone your voice, the recording you make is sent too, with your name as you read it in the consent statement, and Fish Audio holds the cloned voice, private to our account, until you delete it. Fish Audio's terms let it use what it is sent to develop its models |
| Zernio | United States | Publishing to social platforms; holds the access tokens of the accounts you connect, and the pictures and videos of a post while it is published, including a photo or a video you took for a campaign, for up to seven days |
| Stripe | United States, with Canadian entities | Payments, invoices and tax; your card is entered on Stripe's pages, never on ours. Stripe holds your billing records: your name, email and billing address, your payment method and your invoices, and your payout details if we pay you a referral share |
| Resend | United States | Transactional email: sign-in links, render notices, lead notifications, the notice before your leads are deleted (with a copy of them attached), the reminders for the campaign posts you share yourself (the title of the campaign and of the post, and links to the post's page, with no photo in them), the question we may email you on Monday about how last week went (a link to a page of two buttons, naming no campaign), and the problem reports you send us from Kiki. Resend holds each message it sends, with its recipient and its content, for 30 days |
| Inngest | United States | Scheduling background jobs; holds each job's instructions and the results of its steps, such as listing facts, addresses, scripts and captions, and the links the campaign reminders and the Monday question carry |
| Railway | United States | Running the jobs that need video tools: preparing the video and audio you upload or record for the editor, making and checking AI motion clips, and taking what a phone wrote into a short video you add to a campaign's post (the place, the time, the phone) out of it, which holds the file you sent for the seconds that takes and then deletes it |
| PostHog | United States (PostHog Cloud US) | Counting the steps agents take, from opening an account, confirming its email and saving the profile to creating a listing, ordering a video or starting checkout: each is sent from our server with your account's internal identifier and the step's details, which are the internal identifiers of the listing, post or campaign, the studio page it happened on, whether it came from a phone, a tablet or a computer, and the options chosen, such as the province, format, style or a count. Your name, email, address, photos and text are not sent, nor your browser's own description of itself, and nothing is sent from your browser |
| ImprovMX | France and the United States | Receiving the email sent to our viarastudio.ca addresses, the problem reports you send from Kiki among them, and forwarding it to our inbox. ImprovMX holds a message only until it is forwarded, and a log of each one's sender, recipient and subject for seven days |
| Gmail | Google's data centres, which it lists as the United States, Chile, Belgium, Finland, the Netherlands, Taiwan and Singapore | Our inbox: the email you send us and the problem reports from Kiki, with the conversation and what the page showed. Gmail holds them until we delete them |
| Microsoft 365 | Canada, where Microsoft keeps the mail of a Canadian organization | Our info@viarastudio.com mailbox: the email you send to it, refund requests among them. Microsoft holds them until we delete them |
| Google Maps Platform | Google's data centres, which it lists as the United States, Chile, Belgium, Finland, the Netherlands, Taiwan and Singapore | Placing a listing on the map: its address is sent when the listing is saved, and its map position to work out the drive and transit times to downtown for its page. Showing Google's map on a listing page that has no drawn map: the visitor's browser loads it from Google, with the listing's address or map position and the page's web address (for a draft, only the site's). Google sees the visitor's IP address, as any site a browser loads from does |
| OpenStreetMap (Nominatim) | United Kingdom, the Netherlands, Ireland and the United States | Placing a listing that has no map position yet, and naming its neighbourhood: its address and map position are sent |
| Overpass.ch | Germany, and its operator is in Switzerland | Finding the parks, shops, transit stops and streets around a listing for its page: its map position is sent |
| Walk Score | Not stated; Walk Score is a Redfin company in the United States | Scoring how walkable a listing's neighbourhood is, for its page: its address and map position are sent. Showing the score on a listing page: the visitor's browser loads Walk Score's logo from it, and it sees the visitor's IP address |
| IndexNow | Not stated; it passes what it is sent to the search engines that take part, among them Microsoft Bing, Naver, Seznam.cz, Yandex and Yep | Telling search engines that a listing page or your agent page was published, changed or taken down: the page's web address, which carries the listing's street address, is sent |
To ask how any of them collects, uses, discloses or stores your information, write to our privacy contact at privacy@viarastudio.ca.
How long we keep it
Listing content stays while your account is open, so you can re-render and re-post. Remove a photo in the studio and the photo, every version made from it and their files are deleted from storage. A listing can only be archived in the studio, which hides it from your list and deletes nothing; to have a listing and everything made from it deleted, write to privacy@viarastudio.ca. Close your account (in the studio, Settings, Profile, Close account) and everything is deleted within 30 days, except the invoices and payments Stripe keeps for tax and accounting, and backups that age out within 35 days. If you set up payouts, your payout account at Stripe stays there. If you earned referral shares, the record of shares paid to you may stay too, for tax. If a photographer referred you, the record of the share your payments earned them stays too, for tax and accounting, without your name or account. Our sign-in limits keep your email address, with when a sign-in code was last sent to it and any wrong passwords tried since your last sign-in. We also keep a one-way code made from the account's email address and use it only so that a new account made with that address does not get all of the free trial again. We never use what we keep to contact you. A team invite, or a photographer's delivery you never claimed, stays with the account that made it, with your email address on it. While your account is open, a lead sent to you from a listing page is kept for 24 months, and emailed to you first, as Leads and CASL below says.
Your rights
You can see, correct, export or delete your personal information, and withdraw consent for anything optional, by writing to privacy@viarastudio.ca. We answer within 30 days. If you are not satisfied, you may complain to the Office of the Privacy Commissioner of Canada or the Office of the Information and Privacy Commissioner of Alberta.
Visits to the public site
The public site, the pages you can read without signing in, uses Google Analytics to count visits. It records which pages were read and how far down, links followed to other sites, whether the sign-in form was started or sent, the site that sent you, your device and browser, and roughly where you are. It does not record what you type. Google processes this in the United States, and explains how it uses information from sites that use its services.
Its advertising features are switched off. Google Analytics is not loaded in the studio or on listing pages, and it is not loaded at all if your browser sends a Global Privacy Control or Do Not Track signal. Google also offers an add-on that blocks it on every site you visit.
Vercel, which hosts the site, counts visits to the public site as well, with its Web Analytics. It records which page was opened, the site that sent you, your browser, operating system and kind of device, and the country you are in. It sets no cookie and keeps nothing in your browser: a visit is told from the next by a code made from the request, which Vercel discards after a day. It is not loaded in the studio or on listing pages.
The public site also carries the Meta Pixel, which reports each page you open there to Meta, the company behind Facebook and Instagram. It is there for our advertising: to see whether an ad led to a visit, and to show our ads to people who have visited, or to people like them. Meta receives the address of the page and of the page that sent you, when you opened it and how long it took to load, your IP address, your browser, device, screen size and time zone, and an identifier the pixel keeps in a cookie. If you arrived by a link from one of Meta's apps, such as Facebook, Instagram or WhatsApp, it also receives the identifier Meta put on that link. If you use Facebook or Instagram, Meta can connect the visit to your account there. The pixel is set to report page views only: it does not record what you click or what you type. Meta handles this in the United States and other countries, and uses it as its privacy policy describes.
The Meta Pixel is not loaded in the studio or on listing pages, and it is not loaded at all if your browser sends a Global Privacy Control or Do Not Track signal. If you have a Facebook or Instagram account, Meta's Activity off Meta technologies setting shows what sites have sent it about you, and lets you disconnect it from your account.
When an account is made from a browser that holds the pixel's cookie, our server tells Meta that as well, once the account's email address is confirmed, so an ad can be judged by the accounts it brought and not only by the visits. Until then, our server keeps the pixel's identifiers from that browser's cookies with the account, and it removes them when the address is confirmed; an account whose address is never confirmed keeps them for as long as the account is kept. Meta is sent that an account was opened, when, and from which browsers: those identifiers, and the browser and device and the IP address of the browser the address was confirmed in, as that browser names them. It is not sent your email address, your name or anything else of your account. As with a visit, Meta can connect it to your Facebook or Instagram account if you use them. Nothing is kept or sent if the browser the account was made in does not hold the pixel's cookie, and nothing is sent if either browser sends a Global Privacy Control or Do Not Track signal.
Cookies
The studio sets cookies for your sign-in session and, while you connect Facebook or LinkedIn, one that holds that platform's sign-in for up to 15 minutes until you pick the Page or account. Signing up with a password sets one more, which holds that password sealed so that only our server can read it, for up to 24 hours or until you confirm your address in that browser; it is never sent to anyone else. It loads no analytics or advertising scripts in your browser. On the public site Google Analytics sets two, named _ga and _ga_90J48W0FBE, to tell one visit from the next. They last up to two years after your last visit, unless you clear them. The Meta Pixel sets one, named _fbp, which holds the identifier Meta receives with each page view, and a second, named _fbc, if you arrived by a link from one of Meta's apps or one that carries Meta's click identifier. They last up to 90 days after your last visit, unless you clear them. The pixel also keeps a note in your browser's storage of the kind of site that last sent you, and of the links from Meta's apps you arrived by.
The public site and the studio share one address, so those cookies stay in your browser while you use the studio, and Meta's two are set for every viarastudio.ca address, listing pages among them. Our server reads Meta's two on one occasion, when an account is made, keeps them with the account until its address is confirmed, and then passes them on to Meta as set out above. Nothing else in the studio or on a listing page reads them or sends them to Google or Meta.
Leads and CASL
On listing websites, anyone who sends you a lead sees a consent line and we store the exact wording they agreed to. We never email a lead without that record. The only message we send a lead is one confirmation in your name, sent if you have turned it on. It tells them how to withdraw their consent: by replying to it, or by contacting you directly. A lead is deleted 24 months after it arrives, with the coach's reminder to follow it up. 30 days before, we email you a list of the leads about to go, with a copy attached to keep, and a lead goes only 30 days after that email. If it cannot reach you, the lead is kept until it can.
Changes
We post every change to this policy here, and the date at the top of the page says when it last changed. When a change is significant, we will also let you know in the studio or by email.