FRISO Versão em português back to FRISO

FRISO · Terms and privacy

This is a courtesy translation. The Portuguese version is the one that applies; if the two differ, it prevails.

Terms of use

updated on November 7, 2026

This is a courtesy translation. The binding text is the Portuguese version of these terms. If the two differ, the Portuguese version prevails.

Who offers the service (identification required by Brazilian Decree 7.962/2013): FR Visuals (50.564.188 FELIPE RISALLAH VILLELA NASCIMENTO, sole proprietor) · CNPJ 50.564.188/0001-79 · Rua Doutor Dario Marinho, 14, Bosque das Acácias, Campos dos Goytacazes, RJ, Brazil, ZIP 28016-050 · contact contact@frvisuals.com.br · replies within 5 business days. What it is: FRISO is a creative space that runs in the browser. It is home to References (with boards in grid or moodboard view), Projects (projects, tasks, ideas and brands), Files, Motion, Animated logo, Layout, Assets, Lettering and the Feed.

1. What you accept

Using FRISO means accepting these terms. If you don't agree, don't use it. You must be 18 or have the authorization of whoever is responsible for you.

2. Account

3. What is yours

4. The Feed and the community

4-A. The reference library

What it is. FRISO References is a public library of images, videos and links that people who use FRISO choose to show. It exists to discover references and to reach whoever made each work. Every item always shows the author's credit (when known) and the link to the original.

A reference does not go into a piece. What is in the reference library and in the Feed, and what you keep in a board from a link, a website, Discover or the Feed, is other people's work. In FRISO, it is there to inspire and to guide the direction of a piece (the palette, the rhythm, the grid), and it never goes into the piece: not as a photo, not as a background, not cut out. As material for a piece, FRISO only accepts a file you uploaded yourself, after you state it is yours or that you have permission from whoever made it. Not even with that statement does someone else's reference go into a piece. FRISO's AI and your own AI, when they work in FRISO, follow the same rule.

Who uploaded is not shown. The library is not a social network: your name and your @ do not appear on what you make public. The exception is the one you choose: a public board you sign shows "by @name" and leads to your page in the community (friso.id/@name), with the boards you signed and the scenes that made it into the Feed. Removing the signature works right away: the board stays public, without your name. A single reference stays unnamed, always. FRISO keeps who uploaded each item for review, to answer a report and to comply with the law, and only hands that information to third parties under a court order. Not being shown does not change responsibility: whoever uploads remains responsible for what they uploaded.

Public or private, always said beforehand. Everything you keep is either public or private, and the screen says which before you save it, with a word and an icon (a globe for public, a lock for private). Each collection has a default, written at its top, and you can change it whenever you want, for the whole collection or a single item. Today's defaults: a new collection starts public; a collection linked to a client project starts private; a link pasted into a public collection goes in public. Making something public is declaring that you hold the rights: a file you upload as public is recorded as yours (the work is yours or you have permission from whoever made it), with no separate question; the screen says so next to the public choice. Saving into a public collection makes it public. The first time something of yours becomes public, FRISO explains all this and asks for your confirmation.

What you guarantee when making something public. By making an item public, you guarantee that:

  1. the work is yours, you have permission from whoever made it, or the item points to the original posted by the author, with the credit they gave;
  2. you did not remove a watermark, signature, credit or link from the item;
  3. the item does not show a person without their permission, nor anyone's personal data;
  4. the item is not illegal, offensive or misleading.

Your statement is recorded (which item, when and which version of this text you saw).

The license you give FRISO. You still own what is yours. By making an item public, you allow FRISO to keep a reduced copy and show it in the library, with the credit, only to operate the service: display, reduce, organize, search, suggest and protect. FRISO does not use what you publish in ads or marketing without the author's permission, does not place ads over someone else's work, and does not use what people save or publish to train artificial intelligence. The license ends when you take the item out of public or delete your account (the copies leave the library; what the law requires is kept for the legal period).

Saving and downloading. Saving someone else's reference keeps the link to the original in your collection, with a preview made by FRISO (the reduced cover and, when the page publishes the video as a file, a clip of up to 5 seconds, without sound), never their file. Video from a platform that does not allow downloading (YouTube, Instagram, TikTok, Vimeo and similar) keeps only the cover. The preview never goes into a piece and has no download button. FRISO only offers to download the file of an item that is yours (or freely licensed, or whose author allowed it).

Review, afterwards. FRISO does not approve anything before it goes live. A team reviews what became public and what was reported, and may keep, feature, hide or warn whoever published it. Hiding takes the item out of public right away, without deleting your private copy.

Reports. Anyone, with or without an account, can report an item at /report or through each item's "report" link, including the author of a work published without permission ("yours? claim it"). FRISO reviews it, takes down what is upheld and answers whoever reported it.

Official copyright contact. Notices of copyright, image or trademark infringement can also be sent by e-mail to contact@frvisuals.com.br. For a quick review, include the item's address on FRISO, the original work (or its link), who holds the right and a contact for the reply.

Repeat infringement. Whoever accumulates 3 upheld copyright reports within 12 months loses the right to publish in the library. The account and what is private remain.

5. Support and how to complain

6. Plans and payment

7. Artificial intelligence

8. What is not allowed

8-A. What you store and share

FRISO's cloud (files, attachments, share links and approval links) only takes what you have the right to store and to share and what the law allows. This applies to what stays private and to what you send by link. Never, under any circumstances:

How we act. FRISO does not look at your private files day to day. Anyone can report a link or a file through the Report button shown on every shared link, or through the report page (/report). When there is a report or a clear sign of something on the list above, we may review the reported file, take the link down, delete the file, suspend or close the account, and keep the records the law requires. Court orders and requests from competent authorities are handled as the law provides (Brazil's Marco Civil da Internet). Whoever stores and shares is responsible for what they store and share.

9. Beta and availability

10. Liability

11. Termination

12. Changes to these terms

If they change in a relevant way, we notify you by e-mail or in the app 30 days in advance. Continuing to use FRISO after that counts as acceptance.

13. Law and jurisdiction

These terms follow Brazilian law, including the Consumer Defense Code (Law 8.078/1990), the Internet Civil Framework (Law 12.965/2014) and the LGPD (Law 13.709/2018). The courts of Rio de Janeiro are elected; if you are a consumer, you may sue in the courts of your own domicile, as the law guarantees.

If any clause is found invalid, the others remain in force. And no clause here limits a right that consumer law gives you.

Cancellation, withdrawal and refunds

updated on November 7, 2026

This is a courtesy translation. The binding text is the Portuguese version of this policy. If the two differ, the Portuguese version prevails.

In one sentence

You subscribe when you want, cancel by yourself whenever you want, have 7 days to withdraw and get everything back and, once there is an annual plan, get back the months you didn't use. All inside FRISO itself, without asking anyone.

1. How to cancel

2. What happens after you cancel

3. Withdrawal: 7 days (art. 49 of the Brazilian Consumer Code)

4. Annual plan: changed your mind mid-year

There is no annual plan yet: today the plans are monthly. Once there is one, this is what applies:

5. Refunds outside the 7 days (monthly plan)

6. Before you pay, you see

As required by Brazilian Decree 7.962/2013, before confirming the subscription the following appears clearly:

After paying, a receipt arrives by e-mail (through Stripe), with the amount, the plan and the date of the next renewal.

7. Price changes

Prices may change. We notify you at least 30 days in advance by e-mail and in the app, and the new amount only applies from the following renewal: that leaves time to cancel first if you don't want to continue. Whoever subscribed at the launch price keeps that price while the subscription stays active.

8. Support

contact@frvisuals.com.br, reply within 5 business days. It is the same channel for questions, cancellation, refunds and any problem with your data.

Privacy policy

updated on November 7, 2026

This is a courtesy translation. The binding text is the Portuguese version of this policy. If the two differ, the Portuguese version prevails.

Who processes the data (controller): FR Visuals (50.564.188 FELIPE RISALLAH VILLELA NASCIMENTO) · CNPJ 50.564.188/0001-79 · Rua Doutor Dario Marinho, 14, Bosque das Acácias, Campos dos Goytacazes, RJ, Brazil, ZIP 28016-050 · contact@frvisuals.com.br. Data protection officer (DPO): Felipe Risallah, at the same e-mail. Reply within 15 days, as the LGPD (Brazil's data protection law) requires.

Google user data (Sign in with Google)

FRISO lets you create an account and sign in with your Google account. This section explains exactly what FRISO receives from Google, what it does with it, and how you can remove it.

What we access. When you choose Continue with Google, Google asks you to share only your basic profile (the openid, email and profile permissions). FRISO receives:

FRISO does not request access to Gmail, Google Drive, Google Calendar, Contacts, YouTube or any other Google service. It cannot read, send, create, change or delete anything in your Google account.

How we use it. Only to:

We do not use Google user data for advertising, we do not sell it, we do not use it to build profiles, and we do not use it to develop, improve or train artificial intelligence or machine learning models, ours or anyone else's.

How we store and protect it. The data is kept in FRISO's sign-in database, run by Supabase (in the São Paulo region whenever available), encrypted in transit (HTTPS/TLS) and at rest. Each account can only read its own data. FRISO does not keep Google access or refresh tokens on its servers and does not use them to call any Google API.

Who we share it with. No one, except the providers that run the service on our behalf and under contract: Supabase (sign-in and database), Cloudflare (hosting), Resend (to deliver e-mails to your address), GitHub (the encrypted daily backup) and, only if you subscribe to a paid plan, Stripe (payment). We also disclose data when the law or a court order requires it. Google user data is never transferred to advertisers, data brokers or AI providers.

How long we keep it, and how to delete it. We keep it while your account exists. You can delete your account at any time in Account › Profile › Delete my account, or by writing to contact@frvisuals.com.br. Deleting the account removes your Google data from FRISO's active database right away; the encrypted backup copies expire within 30 days. You can also remove FRISO's access to your Google account at https://myaccount.google.com/connections. That stops future sign-ins with Google, but does not delete your FRISO account by itself.

Limited Use. FRISO'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.

Contact. FR Visuals (CNPJ 50.564.188/0001-79), Rua Doutor Dario Marinho, 14, Bosque das Acácias, Campos dos Goytacazes, RJ, Brazil, ZIP 28016-050 · contact@frvisuals.com.br. We reply within 15 days.

The principle

Your photos and videos stay on your computer, unless you save to your account or upload them to Files. FRISO draws everything in your browser: the preview, the video, the PNG and the After Effects file. When you use Save to account, the photos of that project go up to FRISO's cloud (Cloudflare R2), in a private folder that only your account can read, within the space of your plan.

While you are signed in, your work is also kept in your account. Your boards, projects, tasks, ideas and notes, brands (with the fonts you uploaded), Layout carousels, pieces and campaigns are saved to your account, with the attachments and audio of your projects, with their images, videos and fonts, in a private folder that only your account can read, so they open in any browser where you sign in. Everything stays saved in your browser too. The first time, FRISO tells you and keeps a backup copy in the browser. You can turn this off on the account page (Saved to account).

Only what you ask for leaves the browser, and the interface says so at that moment. The exceptions are the Meta pixel and Microsoft Clarity, which measure our ads and the page and have their own rules (see How we know an ad worked):

WhatWhere toWhen
The text of your conversationAnthropic (Claude), straight from your browserwhen you connect your own key in the Assistant
The text of your conversation and the state of the open piece (without the photos)FRISO, and from there to Anthropic (Claude)when you use FRISO's AI in the Assistant (with Free's test credits or your plan's credits)
The photos of a projectCloudflare R2 (the account's cloud), in private storage only your account can readwhen you use Save to account
Your work (boards, projects, tasks, ideas, notes, brands and uploaded fonts, carousels, pieces, campaigns, Motion scenes without the photos), with its attachments, audio and filesSupabase (the account database) for the work and Cloudflare R2 (the account's cloud) for the files, in a folder only your account can read, and people you invite by e-mail, to view or, in a shared project, to editwhile you are signed in with the cloud on (the default; turn it off on the account page)
The project text you ask the Assistant to read (brief, tasks, ideas)FRISO, and from there to Anthropic (Claude)when you use the AI Assistant in your projects (with Free's test credits or your plan's credits); without credits, the Assistant works by rules and does not send your text
When the Assistant can't do a request: the tool, the kind of request and the general reason, without your text (only words from a closed list, like “task” or “animate”), without names and without linking it to your accountFRISO (Supabase)while you are signed in, so we know what the Assistant is missing and it improves with use
The reduced public copy of an image you made publicFRISO, and from there to Cloudflare's AI (Workers AI), which describes in words what the image shows, to relate it to other references and to flag for review anything that looks adult or illegal, which leaves the public library until someone on the team reviews it (no AI is trained on it)when the item becomes public in the reference library
What you authorize your own AI to read and changeyour AI's service (Claude, ChatGPT and others), through the MCP connectiononly after you turn the connection on; turn it off in the account
Your voice, when you dictate a noteyour browser's dictation service (in Chrome, Google)when you use dictation; the recorded audio stays in your browser and, with the cloud on, in your account
The reduced copy of what you make publicCloudflare (R2), at a public addresswhen you make an item public in the reference library
Your e-mail and the message subjectResend (e-mail delivery)when FRISO sends you an account e-mail
The image description (and the chosen reference)Magnificwhen you generate an image with AI
The address of a pasted linkthe link's site, through our server, only to fetch the title and coverwhen you paste a link in the Moodboard
The scene (without photos)FRISOwhen you send a scene to the Feed
E-mail and profileSupabase (the account database)when you create an account
The sign-in requestGoogle, which returns your name and e-mail to FRISOwhen you choose to sign in with Google
The request for the engine files, with your IP (never your audio or your photo)Hugging Face (voice engine), jsDelivr and Google (separating a person from the background)the first time you use those features: the engine is downloaded and runs in your browser
Payment dataStripewhen you subscribe to a plan

What we store

Without an account: nothing on our server. Your work stays in your browser's storage (localStorage and IndexedDB), and disappears if you clear the browser's data. The app warns about this and offers saving to a file.

With an account: e-mail; the name, @, bio, site and language you write; your profile photo, if you add one (a small version, shown to your team and to whoever opens one of your links); the recipes of your scenes (motion, without photos); the JSON of your projects, which includes the list of names of the files you used, so the project can ask for the same media back (their content never goes up this way); with the cloud on, your work in the tools and its files (see above), and who you shared each item with (their e-mail); the subscription state (plan, status, renewal date, Stripe identifiers). Never your card number.

Access logs: Cloudflare keeps server logs (IP and browser) for a short period, like any host, for security and operations.

What your AI did: every change your AI makes through the MCP connection is recorded in your account: which AI it was (the name it gives itself), the request it sent (up to 300 characters), the before and after of each item and the date, so you can see it and undo it. The screen shows the last 30 days; the record stays until you delete the account, and only your account can read it.

Beta report: what you write in the "beta" badge only leaves when you send it, copy it or open the e-mail, and it is kept for the FRISO team to read; it goes with technical data (version, page, browser, screen, project numbers and the tab's latest errors), never with the content of your project.

News list: the e-mail, the language and the suggestion you write in the form, until you ask to leave.

Anonymous site visits: to know how many people arrive and from where, the site notes each page viewed, on our own server, with no cookie and nothing that says who you are: the page, the time, where the visit came from (the referring site, or the campaign and ad in the link), the country, the language, whether it is a phone and whether an account is open (just yes or no). We do not keep your name, e-mail, account, IP or the full address. Pages from the same tab are linked by a code that is born and dies with that tab. If you refuse cookies, that code is not sent and each page counts alone; in Europe it is only used after you accept. Everything is deleted within 90 days.

How the page is used (Microsoft Clarity): on the home page and the account page, Microsoft Clarity records how the page is used (where people scroll, tap and stop), so we can improve it. E-mail, password and code fields are hidden: Clarity does not see what you type. Until you accept cookies it works without cookies; once you accept, it uses its own cookies to link visits from the same browser. The campaign and ad you came from and the page language go with it. What Microsoft does with this data follows its own policy (https://privacy.microsoft.com).

Anonymous usage statistics: to know whether FRISO works, the site notes a few events, with nothing that says who you are: that a page opened, that the first photo came in, that the first thing was made in a tool, which ready-made scene was picked, the type of file exported (for example "mp4 video") and the sentence of an export error. When a page opens, it also notes whether this browser had opened FRISO on another day, only yes or no: for that, the browser keeps the day of the first visit, and that day never leaves it. No account, e-mail, cookie, file name, photo or text of yours goes with it. What links these events within a visit is a random code that only lives in that tab and disappears when it closes. Nothing is noted outside the published site.

The reference library (what becomes public)

Meetings recorded in a project (Pro)

Client approval (Pro)

Legal basis (LGPD)

Who we share with

Only with those who make the service work: Supabase (database and login), Cloudflare (hosting, the account's cloud and the public copies in the reference library), Stripe (payment), Resend (e-mail delivery), GitHub (keeps the daily encrypted database backup for 30 days) and, when you use them, Google (sign in with Google), Anthropic and Magnific, and Microsoft (Clarity, on the home and account pages). Your own AI, when you turn on the MCP connection, is a service you chose and signed up for: what it receives follows its own policy. To measure our ads, Meta receives the pixel events and, for people who arrive through one of its ads, the notice that the account was created (see below). We don't sell data, and apart from the pixel and Clarity there is no advertising and no third-party tracker in the app.

For how long

As long as the account exists. Once you delete the account, we delete the profile, the scenes and the projects within 30 days, except what tax law requires us to keep (payment records). Scenes you published in the Feed may stay there, with your name, until you ask for removal. What was deleted from the database leaves the backups within 30 days.

In Files, what you put in the Trash stays visible to you for 30 days. After that, or when you use "Delete permanently", it leaves your account and stops counting against your space, but it stays stored for safety until 90 days have passed since it went to the Trash. Then it is really deleted. During that time no one sees or uses it, and you can ask for it back at contact@frvisuals.com.br. Deleting the account deletes all of this too, without waiting for the 90 days.

International transfer

Supabase, Cloudflare, Stripe, Resend, GitHub, Google, Anthropic, Magnific, Microsoft and Meta are outside Brazil, so the data that passes through them leaves the country. The LGPD allows this when there are contractual protection clauses with the provider and when it is necessary to perform the contract with you, which is the case. FRISO's database is created in the São Paulo region whenever the provider offers it.

Automated decisions

We don't use your data to decide anything about you automatically, or to score you. Measuring ads with the Meta pixel depends on your consent, and the notice of an account created from an ad is explained in How we know an ad worked.

Security

The measures are described under Security, on this same page: your work stays in your browser (and, if you save to the account, in a private folder of your account), the password is stored only as a hash by Supabase (never in plain text), the database has row-level security, payment belongs to Stripe and everything travels over HTTPS. In the event of a relevant incident, we notify you and the ANPD (Brazil's data protection authority).

Your rights

At any time, you can (art. 18 of the LGPD):

Just write to contact@frvisuals.com.br. We reply within 15 days. If you are not satisfied, you can complain to the ANPD.

Connection records (Internet Civil Framework)

Brazil's Internet Civil Framework requires keeping application access records for six months. We keep the date, the time with time zone and the IP of whoever publishes in the reference library and whoever reports, and use them only for security and court orders, never for marketing.

Cookies

FRISO uses browser storage to keep your work and your preferences, and a Supabase session cookie when you sign in to the account.

To measure our ads, we use the Meta pixel, which stores Meta cookies in your browser (for example _fbp). In every country, it only loads after you accept in the cookie notice. If your browser sends the "do not track" signal (Global Privacy Control), that counts as a decline and the notice does not even appear.

Your choice is stored in your browser. To change your mind, open the cookie preferences.

When you delete the account

Everything that is yours here disappears: profile, scenes, projects, the work kept in the account (boards, tasks, ideas, brands, attachments and audio), your public references, credits and the photos and files you may have uploaded to the cloud: the files leave storage before the account is deleted. If the photos cannot be deleted at that moment, the account is not deleted and you are told, instead of orphan files being kept with no owner.

Two things don't disappear at the same instant, and the reason is legal: the payment history at Stripe (their tax obligation) and the scenes you may have published in the Feed, which are removed on request.

How we know an ad worked

When you reach FRISO through a campaign link, we store in your own browser the name of that campaign and ad (for example meta/paid/launch/video-1) or the site that referred FRISO, and the date. If you create an account, that line is kept in the account, along with the page you came in through and the address of the site that referred FRISO (without the search part of the address); if you subscribe, it goes along with the subscription in Stripe.

We also use the Meta pixel (Facebook and Instagram). It tells Meta when you open a FRISO page, open the plans page, make your first change in a tool, tap download without being signed in, create an account, click to subscribe, subscribe or export for the first time. With it go the page address (never with the sign-in data: when the address carries it, the pixel waits until it is gone), the tool and the file type, the campaign you came from, the plan and the amount when it is a subscription, and the technical data the pixel collects (browser, IP and Meta cookies). Your name, your photos, your videos and anything from your work do not go. Meta uses this to tell us how many accounts and subscriptions each ad brought, and may link these visits to your Meta account, under its own privacy policy.

Our server also tells Meta directly (the Conversions API) about two things: the account being created and the subscription. If you accepted cookies, this applies wherever you came from. This keeps the measurement from being lost when the browser blocks the pixel. With it go your e-mail and your account number in scrambled form (a SHA-256 hash: Meta does not receive the e-mail as text, it can only compare it with what it already has; if you sign in with Google, the e-mail does not go, only the account number), the campaign you came from, the plan and the amount paid, Meta cookies, the browser and, for the new account, the IP.

When you create an account, FRISO tells Meta (Instagram and Facebook) that an account was created, even without cookie consent, to measure our ads and help Meta show them to people interested in creating. Only this goes: your e-mail in scrambled form (a SHA-256 hash; if you sign in with Google, the e-mail does not go), your account number in scrambled form, the browser and IP at sign-up and, if you came from an ad, the click identifier (the fbclid that Meta itself adds to the link), the campaign and the ad; if you subscribe, also the subscription, the plan and the amount. Without consent, no cookie is read or set for this, and nothing from your work goes with it. If your browser sends the "do not track" signal (Global Privacy Control), nothing is sent, and you can ask us to stop at any time at contact@frvisuals.com.br.

The pixel only loads if you accept in the cookie notice, in every country. You can change your mind at any time in the cookie preferences, at the foot of the pages and in the help (?) of the tools: after you decline, nothing else is sent. All of this serves one question only: does this ad pay for itself?

What Meta does with this data follows its own policy. To see and adjust the ads you get on Facebook and Instagram, use the ad settings of your Meta account (https://www.facebook.com/adpreferences).

You can delete the campaign line by clearing the site data in your browser, and ask us to remove that line from your account or subscription through the contact e-mail.

Children

FRISO is not intended for people under 18.

Changes

We notify you in the app when this policy changes in a relevant way.

Security

updated on November 7, 2026

This is a courtesy translation. The binding text is the Portuguese version of this page. If the two differ, the Portuguese version prevails.

The design that protects the most: the work is born here

FRISO draws everything in your browser: preview, video, PNG and the After Effects file. Without an account, nothing leaves your browser. What doesn't exist on the server can't leak from the server.

With your account open, your work is also kept in the account: boards, carousels, brands (with the fonts you uploaded), pieces and campaigns are saved with their images, videos and fonts, in a private folder only your account can read. You can turn this off on the account page. The photos of a Motion project only go up when you use Save to account. The details of each item are in the Privacy Policy.

Signing in

Login is by e-mail link, Google or e-mail and password. The password goes from your browser straight to the sign-in service (Supabase), which only keeps a cryptographic digest of it: FRISO never sees or stores your password. Anything that depends on your e-mail (an invitation to view a board, for example) only works once the e-mail is confirmed. The session stays in your browser and you can sign out whenever you want.

Each person only sees what is theirs

The database (Supabase/PostgreSQL) has row-level security enabled on every table: profile, scenes, projects, the work in the cloud, credits and subscription only answer to their owner. Cloud files live in a folder only your account can read; people you invite by (confirmed) e-mail can view, or edit when you allow it in a project. The service account, which bypasses those rules, exists only inside server functions and never reaches the browser.

Once a day, the database gets an encrypted backup, kept for 30 days.

Payment

Stripe does the processing. FRISO never sees or stores card numbers. What changes your plan is a signed notification from Stripe, checked by cryptographic signature before anything else, and the browser cannot write its own plan.

AI

The reference library

What you make public becomes a reduced copy, made by FRISO, with the credit of the original. It is removed when you take it down, when the team takes it down (after a report or in review) and when you delete the account. To comply with Brazil's Marco Civil da Internet, we keep the date, time and IP of whoever publishes and whoever reports for 6 months, and then delete them.

Transport and headers

Everything over HTTPS, and the browser is told to only talk to FRISO that way. The site sends security headers: X-Frame-Options (nobody can embed FRISO in an iframe), X-Content-Type-Options, Referrer-Policy, origin isolation, plugins blocked, and the browser permissions closed (camera, location and payment off; the microphone only for voice notes and meeting recording, which also hears the tab or screen audio when you share it).

What you can do

If something happens

Found a flaw? Write to contact@frvisuals.com.br: we reply within 5 business days, fix it and notify whoever was affected. In the event of an incident involving personal data, we follow the LGPD: we notify the people affected and the ANPD, saying what happened, what was affected and what we did.

What doesn't exist yet (and we say so)