Privacy Policy

1. Who we are#

Clevera (“Clevera”, “we”, “us”, “our”) makes software that turns screen recordings, websites and the material you give us into narrated product videos, social clips and help articles.

Clevera is operated by Clevera Teknoloji AŞ, Yenişehir Mah. Kardeşler Cad. 7/2, Sivas, Türkiye.

Email: team@clevera.ai

We protect personal data under the laws that apply to us. These include:

• the EU General Data Protection Regulation (GDPR)
• the UK GDPR
• the Turkish Personal Data Protection Law No. 6698 (KVKK)
• the California Consumer Privacy Act as amended by the CPRA

We have not appointed a Data Protection Officer or an EU/UK representative.

2. Scope#

This Policy covers:

• clevera.ai, including our free tools at clevera.ai/tools
• the Clevera web app at app.clevera.ai
• our desktop recorder for macOS, Windows and Linux, and our browser extension for Chrome (see section 4.5)
• shared video pages and embeds
• our documentation, support and sales channels
• any other Clevera service that links to this Policy

It does not cover third-party sites or services, including those you connect to Clevera.

3. Our roles: controller and processor#

Controller. We are the controller for:

• your account
• billing and usage data
• security and login data
• our website, including the free tools (see section 8)
• marketing
• support conversations

Processor. For content you or your team put into Clevera, we act as a processor (or “service provider”) on your instructions. This “Customer Content” includes recordings, uploads, website captures and generated videos, articles and audio. Our Data Processing Addendum (DPA) governs this processing and is available on request.

If your employer or another organization gave you access to Clevera, that organization controls the Customer Content in its workspace. Direct requests about that content to them.

4. What we collect#

4.1 Information you give us#

• Account and profile:

  • name and email
  • password (stored only as a one-way hash)
  • profile photo and timezone
  • your marketing-email preference
  • two-factor authentication settings

• Team and workspace:

  • team name and logo
  • members, invitations and roles
  • brand kits, logos and project settings
  • single sign-on (SSO) configuration, if you set it up

• Billing:

  • plan, seats, credit balance and usage
  • invoices, and answers to cancellation surveys

  Our payment provider and Merchant of Record, Lemon Squeezy, collects your card details. We never see or store full card numbers.

• Support: messages, contact email and attachments you send through in-app chat or email.

• Keys and connections you add:

  • your own ElevenLabs API key, if you choose to use it
  • OAuth tokens for integrations you connect, such as Notion, Confluence, GitHub, GitLab, Bitbucket, ClickUp, Google Docs, Help Scout, GitBook, ReadMe or WordPress
  • the account details and access tokens of video platforms you connect to publish videos, such as YouTube, TikTok or Google Drive (see section 17.1)

  We store these encrypted.

4.2 Customer Content#

• Recordings:
  • screen video
  • camera video and microphone audio, if you turn them on
  • interaction data from the recording: clicks, scrolls, key presses, cursor movement and, where the recorder captures it, text typed during the recording. Our Chrome extension collects no interaction data: it records only video and sound (see section 4.5).
• Materials: images, videos, audio, PDFs, YouTube links and website links you attach.
• Website captures: pages, text, images and logos collected from websites you ask us to research or film (see section 7).
• Generated output:
  • scripts and narration
  • voice-over audio and captions
  • AI avatar videos and AI-generated images
  • videos and social clips, including the code our AI writes to render them
  • articles and translations
• Assistant conversations: instructions you give the in-app video assistant.
• Desktop app and Chrome extension logs you choose to send us when reporting a problem.

4.3 Information collected automatically#

• Login and security data. When you sign in, we record:

  • your IP address and browser user agent
  • an approximate location derived from the IP: country, region and city, plus the network provider

  We use this to detect sign-ins from new devices, send verification codes and protect your account.

• Device and log data: IP address, browser and operating system, app version, timestamps, errors and performance events.

• Usage data:

  • features used and jobs run
  • credits consumed
  • rendering diagnostics, such as browser and graphics capability, used to choose how a video is rendered

• Fraud and abuse prevention. For the Free plan and referral program we keep:

  • keyed hashes of a random device identifier stored in a cookie
  • keyed hashes of the network block (/24) of your IP address
  • your email domain

  We use these to limit repeated free accounts and referral abuse. We do not store the raw values for this purpose.

• Shared-video views. When someone watches a video you shared or embedded, we record the device class (desktop, mobile or tablet) and the country. We do not store viewers’ IP addresses for this.

4.4 Information from third parties#

• Google sign-in: if you sign in with Google, we receive your name, email and profile photo.
• SSO: if your organization uses single sign-on (SAML or OpenID Connect), your identity provider sends us your identity attributes.
• Brand logos: public logo files from Brandfetch for a website domain you or your content name.
• Payment status: subscription and payment status from Lemon Squeezy.

4.5 The Clevera Chrome extension#

Our Chrome extension records your screen and uploads the recording to your Clevera workspace, where Clevera turns it into videos, guides and articles. That is all it does.

• What it records. The browser tab, window or screen you choose, only after you press Start and only until you stop. Your microphone and camera are optional, and Chrome asks your permission before the extension can use them. The extension records video and sound only: it does not collect your clicks, scrolling, key presses or typed text. The recording becomes Customer Content in your workspace.
• The name of the recorded tab. The extension shows the title of the tab you record, or its address if it has no title, in its own panel and keeps it on your computer with the local copy. It does not send page titles or addresses to Clevera: we only learn whether you recorded a tab, a window or your screen. The extension does not collect your browsing history.
• A local copy until the upload is confirmed. While you record, the extension saves the recording on your computer, in the extension’s own storage. It deletes this copy once Clevera confirms the upload, or when you delete the recording. If an upload fails, the extension keeps the recording and asks you to try again or delete it. A kept recording is deleted after 7 days, and the extension tells you before that happens.
• Upload. The recording is uploaded over an encrypted connection to Clevera’s storage at Amazon Web Services (see section 11).
• Sign-in. After you sign in, the extension keeps your email, the workspace you record to and the tokens for your Clevera session in Chrome’s storage on your computer. The tokens are sent only to Clevera at app.clevera.ai.
• Diagnostic logs. Logs leave your computer only when you press Send logs in the extension’s settings. Sign-in tokens are removed from them first.
• What it does not do. The extension has no ads and no analytics, and it reads nothing from the pages you visit. It connects only to Clevera and to the storage Clevera provides for your upload.
• Removing the extension. Removing it from Chrome deletes what it stored on your computer, including any recording that has not finished uploading. Recordings already in your workspace stay there until you delete them (see section 14).

Chrome Web Store User Data Policy. Clevera’s use of information received from the Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use this information only to provide the extension’s single purpose: recording your screen and turning the recording into content in your Clevera workspace. We transfer it only to the providers in section 11 that help us do this, or where the law requires it, as section 10 describes. We do not sell it, use it for advertising, or use it to determine creditworthiness or for lending.

5. How we use data and our legal bases#

We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you.

Our Free-plan abuse checks can flag an account automatically. A person reviews any flag before an account is restricted for that reason.

6. AI processing#

Clevera uses AI models from third-party providers to understand your material and generate your output. This covers watching recordings, reading pages and documents, writing scripts, generating narration and presenters, directing and coding video scenes, transcribing speech and translating.

To do this, we send the relevant Customer Content to the providers listed in section 11. Depending on the job, that can include recording frames or video, audio, text and images.

• No model training. We do not use your Customer Content to train AI models. We use these providers under commercial API terms that do not allow them to train their models on it.
• Limited provider retention. Some providers keep API inputs and outputs for a short period, typically up to 30 days, to detect abuse, and then delete them. Video files we upload for analysis are deleted from the provider within hours of the job.
• Your own keys. If you connect your own ElevenLabs key, narration text goes to ElevenLabs under your own account and its terms.
• Review your output. AI output can be inaccurate. You should review it before publishing.

7. AI website research and “Record with AI”#

When you give Clevera a website link, an AI agent may visit the site in a cloud browser run by our provider Browser Use. It reads and films the pages so we can understand the product and show it in your video. We collect page text, images, logos and a video of the browsing session. This becomes Customer Content.

• Public research. Research runs are instructed not to sign in, submit forms or make purchases.
• Signing in to your app. If you ask the agent to film a part of your product that requires a login, you may give it credentials. We use them only for that run and never include them in the AI model’s prompt. We hold them encrypted only while the job runs, then discard them.
• “Remember my sign-in.” If you turn this on, the browser session’s cookies are kept in a saved browser profile at Browser Use, so you don’t have to sign in again. Saved sign-ins are deleted:
  • after 30 days without use
  • when you remove them
  • when you delete your account

You must have the right to let Clevera access any account or website you point it at. See our Terms of Service.

8. Free tools#

Our free tools at clevera.ai/tools work without an account. We are the controller for the data they process.

Please do not submit personal data, confidential information or other sensitive data to the free tools.

8.1 Tools that run in your browser#

Our media tools and calculators process your files on your own device. File content is never uploaded. When you use one, your browser sends us only a usage record: which tool, your language, the action (for example, a download) and, if you accepted cookies, your visitor id (cl_vid).

8.2 AI tools#

Our AI tools are the text generators, Screenshots to Guide, the screenshot redactor’s optional AI detection, Video to Guide and the subtitle generator. They send your input to our server, which passes it to an AI provider and returns the result to your browser.

• What is sent. The text, images or video you submit, or the YouTube link you give. Before images are uploaded, your browser removes photo metadata such as EXIF data and GPS location. For subtitles, your browser extracts the first 3 minutes of audio and sends only that.
• Who processes it. By default, Google’s Gemini API, on a paid tier under which Google does not use the input to train its models. Gemini processes all images, video and audio. For a YouTube link, Google fetches the video itself. For text tools, we may use OpenAI instead. Before processing a YouTube link, our server asks YouTube’s public oEmbed service whether the video is public.
• Network and bot checks. Requests to the free tools pass through Cloudflare. AI tools use Cloudflare Turnstile to check that you are not a bot. Turnstile receives your IP address and may set Cloudflare cookies.
• PDF downloads. When you click “Download PDF”, your browser loads fonts from jsDelivr, which receives your IP address.

8.3 What we keep#

• We don’t keep your input or the result, only a record that the tool ran. We process your input in memory and return the result in the response. We do not save or log your input, uploads or results. Results exist only in your browser tab until you copy or download them. They have no shareable link.
• Run and usage records, without content. For each run we keep the tool, the outcome, the amount of AI processing used and its cost, the size of the input, your country and language, and a visitor hash. The hash is made from your IP address and browser user agent with a salt that changes daily. If you accepted cookies, we also keep your visitor id (cl_vid), which can be linked to a Clevera account you create later. We keep run and usage records for 90 days.
• Abuse prevention. We do not store raw IP addresses for the free tools. Usage limits and blocks use a keyed hash of your IP address or network. A block for repeated refused requests lasts 24 hours.
• Error logs may contain an AI provider’s error message, but not your input.
• AI providers. Google, and OpenAI when we select it, process your input under their paid API terms. They do not use it to train their models, but they may keep it for a limited period to detect abuse, and then delete it, as section 6 describes.

8.4 Legal basis#

We run the free tools, secure them and prevent abuse on the basis of our legitimate interests in providing the tools and keeping them safe. We set the cl_vid visitor id and run Google Analytics only with your consent.

9. Cookies and similar technologies#

9.1 The Clevera app#

The Clevera app uses these cookies:

These cookies are strictly necessary for security, fraud prevention or features you ask for. The app does not use advertising cookies or third-party analytics cookies.

Our app loads fonts from Google Fonts, which means your browser sends your IP address to Google when the page loads.

9.2 Our website and free tools#

Our website at clevera.ai, including the free tools, uses these cookies and similar technologies:

We do not set cl_vid if your browser sends a Global Privacy Control or Do Not Track signal.

9.3 Website analytics#

We measure how our website is used in two ways:

• Our own statistics. Page views, clicks on buttons and links, how far you scroll and how long a page is in view. These go to Clevera. Without your consent they are anonymous: we recognise a visit only by a hash of your IP address and browser user agent, with a salt that changes daily.
• Google Analytics 4, run by Google, with Google Consent Mode. Until you accept cookies, it sets no cookies and sends Google only cookieless signals, which still reach Google from your IP address. If you accept, it sets its cookies and measures your visit.

You can accept or reject these cookies in our cookie banner. To change your choice later, clear this site’s data in your browser, and the banner asks again.

10. Sharing and disclosures#

We share personal data only:

• With sub-processors and service providers that help us run Clevera (section 11), under contracts that limit their use of the data.
• With people you choose:
  • team members in your workspace
  • viewers of videos you share or embed
  • integrations you connect and publish to
• With Lemon Squeezy, our Merchant of Record, which processes your purchase and handles tax under its own privacy policy as an independent controller.
• For legal reasons: to comply with law, enforce our terms, or protect the rights, safety and property of our users, the public or Clevera.
• In a business transfer, such as a merger, acquisition or sale of assets, subject to this Policy.

We do not sell personal information. We do not “share” it for cross-context behavioral advertising, as those terms are defined under the CPRA.

11. Sub-processors#

We use the following providers to deliver Clevera:

We may update this list. Customers under our DPA will be notified of material changes as the DPA describes.

Not sub-processors. Services you connect yourself act on your instructions and under their own terms, not as our sub-processors. These include ElevenLabs with your own key, publishing integrations such as Notion, Confluence, GitHub, GitLab, Bitbucket, ClickUp, Google Docs, Help Scout, GitBook, ReadMe and WordPress, and the video platforms you connect to publish videos (section 17.1).

Map scenes. If you add a map to a video, the place names you type are looked up using the public Photon geocoder (Komoot / OpenStreetMap).

12. International transfers#

We are based in Türkiye, and our providers process data mainly in the United States and the European Union. When personal data leaves the EEA, the UK or Türkiye, we rely on appropriate safeguards. These include:

• adequacy decisions, such as the EU–US Data Privacy Framework where the provider is certified
• the EU Standard Contractual Clauses and the UK Addendum
• for Türkiye, the standard contracts required under KVKK

We also apply measures such as encryption in transit and access controls.

13. Security#

We protect data with:

• encryption in transit (TLS)
• encryption of secrets and connection tokens at rest
• short-lived signed links for media
• two-factor authentication and new-device verification
• role-based access
• signed webhooks
• isolation of the components that visit websites on your behalf

Details are on our Security page.

No system is perfectly secure. If you believe your account or data has been compromised, contact team@clevera.ai right away.

14. Data retention#

When you delete your account:

• We cancel your subscription and revoke your access tokens and saved sign-ins.
• We anonymize your support history.
• We permanently delete the teams you own, with their recordings, videos and files, shortly afterwards.
• Data in backups expires after 7 days.
• We may keep limited records where the law requires it or to resolve disputes. Examples are invoices and fraud-prevention hashes.

15. Your rights#

Depending on where you live, you may have the right to:

• access your personal data
• correct it
• delete it
• receive a portable copy
• restrict or object to processing
• withdraw consent at any time

Withdrawing consent does not affect processing that happened before.

• Marketing emails: unsubscribe using the link in any email or in your account settings.
• Making a request: email team@clevera.ai. We may need to verify your identity. We respond within the time the law requires, usually within one month.
• Workspace content: if your request concerns Customer Content in an organization’s workspace, we will refer you to that organization.
• Complaints: you can complain to your data protection authority. Examples are an EU supervisory authority, the UK ICO, or the Turkish Personal Data Protection Authority (KVKK).
• California residents: you have the rights to know, access, correct and delete your personal information, and to limit the use of sensitive personal information. We do not sell or share personal information, and we will not discriminate against you for exercising your rights. An authorized agent may make a request for you.

16. Children#

Clevera is a business tool and is not directed at children. You must be at least 18 to create an account or use our free tools.

We do not knowingly collect personal data from children. If you believe a child has given us personal data, contact team@clevera.ai and we will delete it.

17. Third-party links, integrations and embeds#

Clevera links to and integrates with third-party services, and lets you embed and share videos on other platforms. Those services’ own privacy policies apply to your use of them.

17.1 Connected video platforms#

You can connect your own accounts on video, social and storage platforms and send videos you made in Clevera to them. Today these are YouTube, Vimeo, Wistia, TikTok, Instagram, Facebook Pages, LinkedIn, X, Threads, Google Drive, Dropbox and OneDrive.

What we receive and keep. When you connect an account, we keep:

• the account’s id, name or username, and profile picture (for TikTok: your open_id, display name and avatar)
• the access and refresh tokens the platform gives us, or the API key you paste for Wistia, stored encrypted
• for each video you send: the ids and links the platform returns, and the status of the upload

We do not read your other videos, posts, files, messages or followers. On Google Drive, Dropbox and OneDrive, Clevera can only see the files and folders it created.

How we use it. Only to show you which account is connected and to send the videos you approve. Nothing is sent until you click Send. The text that goes with a video is written by AI from your video and shown to you before you send it (see section 6). We do not sell this data, share it, use it for advertising, or use it to train AI models.

Revoking access. Disconnect the account in Clevera under Integrations. We then revoke our access at the platform, where the platform allows it, and delete the tokens. You can also remove Clevera in the platform’s own settings. When a platform tells us you removed Clevera there, we disconnect the account automatically.

Deleting your data. To have us delete the platform account data we hold, email team@clevera.ai or follow our data deletion instructions. We delete it within 30 days of your request.

YouTube. Clevera uses YouTube API Services to upload the videos you send to your YouTube channel and to show your channel’s name and picture. By connecting YouTube, you agree to be bound by the YouTube Terms of Service. Google’s handling of your data is described in the Google Privacy Policy. You can revoke Clevera’s access at any time in your Google security settings.

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

18. Changes to this Policy#

We may update this Policy as Clevera or the law changes. We will post the new version here with a new “Last updated” date. If the changes are material, we will tell you by email or in the app before they take effect.

19. Contact us#

Clevera Teknoloji AŞ
Yenişehir Mah. Kardeşler Cad. 7/2, Sivas, Türkiye
Email: team@clevera.ai

To request our Data Processing Addendum or the current sub-processor list, email team@clevera.ai.