Privacy Policy
Last updated: October 8. 2026
Contents
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 Odise Studio, 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
the Clevera web app at app.clevera.ai
our desktop recorder for macOS, Windows and Linux, and our browser extension
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
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
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
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 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.
5. How we use data and our legal bases
Create and run your account and workspace; provide the features you use, including AI generation
Contract
Process Customer Content on your instructions
Contract (and your organization’s instructions under the DPA)
Billing, credits, invoicing, tax and accounting
Contract; legal obligation
Account security, new-device verification, fraud and abuse prevention, Free-plan and referral limits
Legitimate interests (keeping the service and accounts safe)
Support, including AI-drafted replies that our staff review
Contract; legitimate interests
Service emails (verification, security, billing, job status)
Contract
Product news and marketing emails
Consent (unsubscribe at any time)
Measuring reliability and performance and improving the product
Legitimate interests
Complying with law and responding to lawful requests
Legal obligation
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 10. 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. Cookies and similar technologies
The Clevera app uses these cookies:
Session cookie
Keeps you signed in
Up to 7 days
XSRF-TOKEN
Protects forms against cross-site request forgery
Session
Remember-me cookie
Keeps you signed in if you choose “Remember me”
Until you sign out
clevera_ref
Remembers which referral link brought you to Clevera
60 days
clevera_did
Random device identifier used for Free-plan and referral abuse prevention
2 years
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.
The clevera.ai marketing site does not use third-party analytics, advertising or marketing platforms. Marketing emails and the site are run by Clevera.
9. Sharing and disclosures
We share personal data only:
With sub-processors and service providers that help us run Clevera (section 10), 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.
10. Sub-processors
We use the following providers to deliver Clevera:
Amazon Web Services
File storage (S3), content delivery (CloudFront), server rendering (Lambda), email delivery (SES)
Customer Content, account email, generated output
US; EU (Sweden)
Hetzner
Application servers and database, managed with Laravel Forge
All service data
EU (Germany)
Google (Gemini API, Cloud Text-to-Speech)
AI analysis of recordings, websites and materials; script writing, translation and narration; image generation; support-reply drafting
Customer Content, support messages
US
Anthropic
AI models (Claude) that write and direct videos and social clips, and the in-app assistant
Customer Content, assistant messages
US
OpenAI
Speech-to-text transcription and captions; AI models; the model that drives website research
Recorded audio, narration, Customer Content, website pages
US
Browser Use
Cloud browser for AI website research and “Record with AI”
Website URLs, pages visited, credentials you provide for a run, saved sign-in cookies
US
HeyGen
AI avatar (avatar) videos, presenter voices, music and sound-effect search
Narration text and audio, scripts
US
Brandfetch
Fetching public brand logos
Website domain names
US
Lemon Squeezy
Payments, invoicing and tax (Merchant of Record)
Billing contact and payment data
US
Slack
Internal notifications to our team, including sign-ups, failed jobs and support messages
Name, email, support message content
US
ipgeolocation.io
Approximate location of sign-ins for account security
IP address
US
Tiptap
AI writing assistance and document export in the article editor
Article text
US
Laravel Nightwatch
Application monitoring and error tracking
Technical logs that may include user identifiers
US
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, and publishing integrations such as Notion, Confluence, GitHub, GitLab, Bitbucket, ClickUp, Google Docs, Help Scout, GitBook, ReadMe and WordPress.
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).
11. 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.
12. 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.
13. Data retention
Customer Content (recordings, materials, generated videos and articles)
While your account is active, or until you delete it
Items you move to trash
Permanently deleted after 7 days
Recordings not used in any video
Deleted after 15 days
Video files sent to AI providers for analysis
Deleted from the provider within hours
Saved browser sign-ins
30 days without use, or until you remove them
In-app notifications
30–180 days
Support attachments
2 years
Application logs
About 14–30 days
Login and security records
12 months
Billing records and invoices
As long as tax and accounting law requires
Marketing preferences
Until you unsubscribe or close your account
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.
14. 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.
15. Children
Clevera is a business tool and is not directed at children. You must be at least 18 to create an account.
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.
16. 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. 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.
18. Contact us
Odise Studio (Clevera)
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.