Your captures never reach our servers.

Every screenshot, recording and edit stays in your browser's own storage, on your own computer. There is no bucket of ours with your work in it, and no server of ours that has ever held a frame of it. Two things can cross the network: the check that says what your licence allows, and — only if you connect one — your own cloud account, which your browser talks to directly.

What never leaves your device

• Screenshots. Captured, stitched, framed and exported by your browser. The canvas that draws them is the one in the tab you are looking at.
• Recordings. Recorded, edited and encoded to MP4, WebM or GIF on your machine. They live in your browser's Origin Private File System until you export or delete them.
• Microphone and camera. Used only while a recording you started is running, and only if you switched them on for it. Your browser shows its own indicator the whole time.
• Cursor movement during a recording. Positions and timings, so the editor can add zooms and click ripples afterwards — coordinates, never page text, form values or keystrokes. Saved next to the recording, on your device.
• Your settings. Backdrops, padding, watermark text, defaults. Kept in the browser's own extension storage.

What does cross the network

Two things, and both are about your licence rather than your work.

• The licence check. When the extension asks what your licence allows, it sends your licence key, an install id, your browser's user-agent string and the extension's version. The install id is a random value the extension makes up for itself — it names a browser so that seats can be counted, and it says nothing about you. We note the country each browser last checked in from, so you and your team owner can see where your licence is used.
• Your account. If you create one, we hold your name and email address, the licences issued to you, the browsers currently using them, and a record of what you have paid.

That is the complete list of what reaches us. No page content, no browsing history, no keystrokes, no analytics on what you capture — none of it is collected, because none of it is sent. The one other place your work can go is your own cloud, below, and only when you send it there.

If you connect your own cloud

On the Pro and Teams plans you can connect Google Drive (Dropbox and OneDrive are coming). Nothing about it touches a server of ours: your browser talks to Google directly.

• What is sent, and where. The screenshots and exports you save or share, into FramioCam/Photos and FramioCam/Videos in your own Drive. If you turn on Project Sync, your projects go to a FramioCam folder there too. Nothing is sent until you connect an account.
• What FramioCam can see in your Drive. It asks Google for the drive.file permission, which lets it open only the files it created — nothing else in your Drive. It also reads your email address, to show you which account is connected.
• Where the sign-in lives. The access token Google issues is kept in the extension's storage on your computer. It is never sent to us.
• Share links. When you share a file, anyone with its link can view it in your Drive. Delete the file there, or change its sharing, to take the link back.
• Turning it off. Switch off automatic uploads, or disconnect, in the extension's cloud storage settings. Revoke FramioCam's access entirely at myaccount.google.com/permissions. Files already in your Drive stay yours to keep or delete.

FramioCam's use and transfer of information received from Google APIs to any other app will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements. We do not use data from Google for advertising, we do not sell it, and no person at FramioCam reads it. Dropbox and OneDrive will follow the same rules when they arrive.

Payment

Paddle is the merchant of record. Card details go to them and never reach us; what we keep is the transaction they report — an amount, a date, a status and an invoice reference — so that your billing page can show you what you bought.

Why the extension asks for what it asks for

• activeTab, tabs — to capture the tab you are looking at and read its size and title, when you press capture.
• scripting, host access — to inject the small helper that scrolls a page for a full-page capture, and during a recording you started, the one that notes cursor positions.
• tabCapture, offscreen — to record what you chose after you press Record, and to keep the recorder alive while it runs. A tab recording is handled by the browser; choosing a screen or a window asks the browser for it, and the browser is what shows you the picker and the indicator. A screen recording captures whatever is on that screen, including windows that are not the browser — so it is worth a glance at what is on it before you start. It is recorded to your own machine either way, and none of it is sent to us.
• storage, unlimitedStorage — to keep your settings, your licence key and your captures on your own machine.
• downloads — to save a finished export to your Downloads folder.
• notifications — to tell you when a long capture or a recording has finished.
• contextMenus — to put capture and recording on the right-click menu, so a capture can be started without opening the popup.
• clipboardWrite — to put a finished screenshot on your clipboard, so it can be pasted straight away.
• identity — to sign in to your own Google Drive when you choose to connect it. Unused until you do.

Deleting things

Recordings and screenshots are yours to delete from the library, or by clearing the extension's storage — we cannot delete them for you, because we do not have them. For account data, write to us and we will remove the account, its licences and its activation records.

Changes

If this changes, the date at the top changes with it.

Asking us

Email support@framiocam.com.