Privacy Policy

Emaki is a Chrome extension made by Appzlr ("we", "us"). It autoscrolls web pages, captures screenshots of them and records your screen. This policy explains what data the extension handles, where it goes, and the choices you have.

Screenshots and page content

Screenshots, and the page content Emaki reads to measure and scroll the page or element you pick, are processed locally on your computer. They are never uploaded to Appzlr or anyone else, with two exceptions you choose: AI edits and share links (see below).

• With Emaki Pro, a capture opens in Emaki's editor at emaki.appzlr.com/edit. The editor page runs in your browser: the extension hands the image straight to that tab, and the page only sends it anywhere if you ask for an AI edit or create a share link. To do that, the extension keeps the last few captures in its own local storage.
• Images you open, drop or paste into the editor yourself stay in that browser tab too.
• Captures saved by the extension, and images and PDFs you save from the editor, go to your Downloads folder.
• Images you copy go to your clipboard.

Screen recordings, camera and microphone

Recordings are made and kept on your computer. They are only uploaded if you create a share link for one (see Share links below).

• Chrome asks you what to record (a tab, a window or your screen) each time, and shows that it's being shared until you stop.
• The microphone and camera are only used while you record with them turned on, after you allow them in Chrome's prompt. The camera bubble is shown by the extension on the page you're recording; that website can't access your camera through it.
• While you record, the video is saved in the extension's own local storage every second, so it isn't lost if the side panel closes. Only the last two recordings are kept there.
• When you record a tab, the extension notes where the pointer moves and clicks in that tab, how big the page is, when it scrolls, and where a field you type into is, but never what you type or what the page says. This lets the video zoom in on each click (auto-zoom) and lets a step-by-step guide find and mark each step. The note is kept with the recording in the extension's local storage and deleted with it. It is never uploaded: a share link uploads only the finished video, and a guide link only the step images, title and text you choose to share.
• Open in Emaki shows a recording at emaki.appzlr.com/video, and Make a guide opens it at emaki.appzlr.com/guide. As with the editor, the extension hands the video, and the note of your clicks for a tab recording, straight to that tab in your browser; the page only sends anything if you create a share link or ask for AI.
• Recordings you download go to your Downloads folder.

Step-by-step guides

A guide is made from a tab recording at emaki.appzlr.com/guide, in your browser. Each step's screenshot is taken from the video at the moment of a click, and the step's text is what you type (or what AI drafts, see below). Page text is never recorded.

• Guides, their step images, your text and your blur and other edits are saved in your browser's storage for this site (IndexedDB), not on Appzlr's servers. They stay until you delete them or clear this site's data. The site asks the browser to keep this storage so it isn't cleared to save space.
• With Emaki Pro, earlier versions of a guide are kept in the same storage, so you can go back to one.
• PDF and Markdown exports go to your Downloads folder.
• A guide is only uploaded if you share it as a link or ask for AI step text that Chrome can't write on this computer (see below).

AI edits and AI step text (Emaki Pro + AI)

When you ask the editor for an AI edit, it sends the area of the image you selected (or the whole visible image if you didn't select one) and the instruction you typed to emaki.appzlr.com/api, which passes them to Google's Gemini API to be edited by Google's Nano Banana image model, and returns the result to your browser. Annotations you drew are not sent. Appzlr does not store the image, the result or your instruction; we only count how many AI edits you've used this month. Google processes the request under the Gemini API terms. Nothing is sent until you run an AI edit (Edit area, Edit whole image or Edit cropped image).

When you ask for AI step text in a guide, the text is written on this computer when Chrome supports it, by Chrome's built-in AI model: nothing is sent and it doesn't count as an AI use. Otherwise the guide page sends each step's screenshot, with the clicked spot marked, along with what the guide is for (if you filled it in) and your language, to emaki.appzlr.com/api, which passes them to Google's Gemini API and returns a title and note for each step. Appzlr does not store the images or the text; we count one AI use for the guide and, for an hour, keep a note of which draft it is, so the rest of that guide's steps aren't counted again. Nothing is sent until you ask for step text.

The recorder and video tools on this site

The screen recorder, the teleprompter and the video tools at emaki.appzlr.com/tools run in your browser. They don't need an account.

• Recordings are made in your browser and kept in its storage for this site (IndexedDB) while you record, so a closed tab can be recovered. Only the last two are kept there. They aren't uploaded unless you create a share link.
• Trimming and converting to MP4 or GIF happen in your browser with its built-in video encoders. Videos you open from your computer stay in that tab unless you create a share link.
• Your teleprompter script and recorder settings are remembered in this browser (localStorage) and never sent anywhere.
• Your browser asks before the site can use your camera, microphone or screen, and shows while it does.

Share links (Emaki Pro)

When you press Create link under a recording or video on this site, that video (the part you chose, as an MP4) is uploaded the same way as an image below, up to 95 MB, and deleted when the link expires or when you delete it.

When you press Create link, after a capture in the extension or in the editor's Share as a link, that one image (with any edits you made) is uploaded to emaki.appzlr.com/api, which stores it with Cloudflare R2 and gives you a link of the form emaki.appzlr.com/s/…. Anyone who has the link can view and download the image; it is not listed or indexed anywhere. We store the image, your account id, its size and when it expires; not the page's address or title. The link stops working after the time you picked (1, 7 or 30 days) and the image is deleted then, or straight away if you press Delete link. Nothing is uploaded unless you create a link.

When you share a step-by-step guide, its step images (with your blur and other edits), its title and each step's title and note are uploaded the same way, and served as a page at emaki.appzlr.com/s/…. You pick 1, 7 or 30 days, or to keep it until you delete it; a kept link stays up until you delete it, from the guide or from your account page. Update link replaces what the link shows with your latest version and deletes the images it no longer uses. The note of where you clicked is never uploaded.

No analytics or tracking in the extension

The extension contains no analytics, advertising or tracking code, and it does not record your browsing activity.

Google Analytics on this website

The public pages of emaki.appzlr.com, such as the homepage, the how-to guides, the free tools and these policies, use Google Analytics 4 to count visits and see which pages and sites bring people here. When you open one, your browser sends Google the page address (without anything after #), the site that linked you here, your browser, device, screen size and language, and your IP address, from which Google works out your approximate region. Google Analytics never sees your screenshots, recordings or guides, and we don't use it for advertising.

The pages that open your own work or your account don't load Google Analytics: the screenshot editor, your recordings, step-by-step guides, sign-in, your account, checkout and the page shown when you remove the extension. Google's handling of the data is covered by Google's privacy policy. You can turn it off with an ad or tracker blocker, or with Google's opt-out add-on.

When you remove the extension, Chrome opens a page on emaki.appzlr.com asking why, with the extension's version number in its address. Answering is optional. If you answer, we store the reason you pick, anything you type, that version number, your browser's name (Chrome or Edge) and the date, and nothing that identifies you: no account, IP address or other browser details. To stop the same answer being sent over and over, we briefly keep a scrambled (hashed) form of your IP address for an hour. We use the answers only to improve Emaki.

Settings stored on your device

Your settings, such as scroll speed, direction, looping, the pause between shots, overlap and what happens after a capture, are saved in Chrome's local extension storage. They stay in your browser. Removing the extension deletes them. Files in your Downloads folder stay until you delete them.

Your Appzlr account (optional)

You can use Emaki without an account. An account is only needed for Emaki Pro.

• Email address. When you sign in, your email address is stored in Appzlr's account database, hosted on MongoDB Atlas. We use it to sign you in and to link your Pro subscription to you.
• Sign-in. Sign-in is handled by Google Firebase Authentication. If you continue with Google, Google tells us your email address and name. If you use an email and password, Firebase stores the account with your password hashed (we never see it) and sends the verification and password-reset emails. Firebase keeps your Firebase user ID, email address and sign-in times.
• How you found us. When you create an account, we record the website that sent you to emaki.appzlr.com (for example chatgpt.com or google.com), any utm_ tags in that link, the first page you opened and when. We use it only to count which places bring us new customers. It is never shared or sold, and it is not recorded for accounts that already exist.
• Display name. Optional, if you choose to set one on your account page.
• Session tokens. After you sign in, the extension stores sign-in session tokens in its local storage so you stay signed in, and caches your Pro status.
• Signed-in devices. For each session we keep the type of app, the browser's user agent, the IP address and when it was last used, so you can review your devices and sign them out from your account page.

Cookies on this website

When you sign in on emaki.appzlr.com, the site sets one cookie to keep you signed in. It is HttpOnly, only sent to the sign-in service at emaki.appzlr.com/api/v1/auth, and never used for tracking or analytics. The public pages that use Google Analytics also set its _ga and _ga_* cookies, which give your browser a random ID so repeat visits are counted once. They last up to two years. The site has no other cookies.

Until you create an account, the site keeps the website that sent you here, any utm_ tags and the first page you opened in your browser's local storage, so it can be added to your account when you create it. It never leaves your browser unless you sign in, is deleted from your browser once you do, and expires after 90 days.

Payments

Emaki Pro subscriptions are sold and processed by Paddle, our Merchant of Record. Checkout happens on emaki.appzlr.com in Paddle's secure checkout. Your card and billing details go to Paddle; they never reach the extension or Appzlr. Paddle tells us the status of your subscription (for example, trial, active, past due or canceled) so we can turn Pro on. Paddle's handling of your data is covered by Paddle's privacy policy.

When you open checkout, we note the plan you chose, whether it included a free trial, and which Pro button brought you there (for example, the editor or share links), so we can see which features people subscribe for. It is kept with your account for about a year.

When the extension connects to the internet

The extension contacts emaki.appzlr.com/api only to sign you in, to check your Pro status and to upload a screenshot when you press Create link. If you never sign in, it makes no requests to Appzlr. (The page Chrome opens when you remove the extension is a normal web page, described above; it only sends anything if you answer its question.) It never sends page content or your browsing history, and it only sends a screenshot when you create a share link for it.

How long we keep data

• Sign-in sessions expire after 60 days of inactivity. Signing out ends the session right away.
• Your monthly AI use count (AI edits and AI step text) is kept for about two months, then deleted.
• A share link is deleted when it expires or when you delete it. A guide link you chose to keep stays until you delete it.
• Answers to the question shown when you remove the extension are kept for two years, then deleted.
• Your account and email address are kept while you have an account. To delete your account, email capture@appzlr.com from the address you signed in with and we will delete it. Paddle may keep billing records it is required to keep by law.

We don't sell your data

We don't sell or share your data, and we don't use it for advertising. We only share what is needed to run the service with the providers named above: Cloudflare (runs emaki.appzlr.com and stores share links in R2), MongoDB Atlas (account database), Google Firebase Authentication (sign-in), Google's Gemini API (AI edits and AI step text), Google Analytics (visits to the public pages) and Paddle (payments).

Why the extension needs its permissions

• Access to all sites (<all_urls>), activeTab and scripting: to scroll the page or the element you pick on whatever site you're reading, highlight it while you choose, and capture the visible part of the tab.
• downloads: to save your screenshots, images, PDFs and recordings.
• storage and unlimitedStorage: to remember your settings, keep you signed in, keep large captures until the editor tab has read them, and keep recordings safe while they're made.
• sidePanel: to show the controls in Chrome's side panel.

Limited use

Emaki's use of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Changes

If this policy changes, we will post the new version on this page with a new date.

Contact

Questions about this policy or your data? Email capture@appzlr.com.

Back to Emaki