BeamTake ("we", "us") is a service that turns long videos into short vertical clips and, when you ask it to, publishes those clips to social media accounts you connect. This policy explains what personal data we process, why, how long we keep it and how you can have it deleted.
The data controller is BeamTake, Houston/Tx, Katy, US. You can reach us at [email protected].
Data we collect
- Account data: email address, name and password. Passwords are stored only as an irreversible hash (scrypt). If you sign in with Google, we also receive your Google account ID and profile picture.
- Connected social accounts: platform user ID, display name, profile picture and an access token. Tokens are stored encrypted on our servers.
- Content: videos you upload or link to, the clips made from them, transcripts, clip titles and any logo you add to your brand kit.
- Support requests: messages you send from the dashboard, the page you were on and basic browser information.
- Usage and security logs: timestamps of actions, error logs, session data and IP addresses.
- Payments: our reseller Creem (see below) collects your payment and billing details and shares with us the transaction ID, amount, plan, country and email address. We never see or store your full card details.
How we use your data and why we are allowed to
- To provide the service (transcription, clip selection, vertical framing, captions, exports and scheduled publishing): necessary to perform our contract with you.
- To publish to your connected accounts, only on your instruction and at the time you choose: necessary to perform our contract with you.
- To answer support requests and show notifications: contract and our legitimate interest in helping you.
- To keep the service secure and working (monitoring, debugging, preventing abuse): our legitimate interests.
- To send product news and tips, only if you opted in at sign-up: your consent, which you can withdraw at any time.
- To keep financial records: legal obligation.
Access tokens are used only to publish the posts you scheduled and to show the connected account in your dashboard. We do not read your other content, collect follower data, use your data for advertising or sell it to anyone. We do not use your videos, transcripts or clips to train AI models.
Service providers
To transcribe speech, the audio track (not the picture) is sent to our speech recognition provider, Groq. To pick the best moments, the transcript text (not the video) is sent to our AI provider, Anthropic. If you use B-roll, only search keywords are sent to our stock footage provider, Pexels. Payments are handled by our reseller Creem. Emails are sent through our email delivery provider, and the service runs on our hosting provider's servers. Each of these providers processes data only on our instructions and under a data processing agreement.
International transfers
Some of our providers are located outside your country, including in the United States. Where personal data is transferred outside the European Economic Area or the United Kingdom, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses.
Platform data (Google, YouTube, TikTok, Instagram, Facebook, Threads, LinkedIn)
Google sign-in requests only the openid, email and profile
scopes. Connecting YouTube requests youtube.upload (to upload to your own channel) and
youtube.readonly (to show your channel name and picture). BeamTake's use of YouTube API
Services is subject to the YouTube Terms of Service
and the Google Privacy Policy. You can revoke
BeamTake's access at any time at
myaccount.google.com/permissions
(also at security.google.com/settings/security/permissions).
What we do with Google and YouTube data. We store your OAuth access and refresh tokens (encrypted), your channel ID, channel name and channel picture. We use them only to show which channel is connected and to upload the videos you choose, with the title, description and privacy setting you choose, at the time you schedule. We do not read, download or analyze your existing YouTube videos or data, we do not sell or share Google user data with anyone, we do not use it for advertising, and we do not use it to train AI or machine-learning models. Only the uploaded video you selected leaves our servers, and it goes to YouTube.
Limited Use. BeamTake'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.
Retention and deletion. Channel details are refreshed when you use the connection and are deleted together with the tokens when you disconnect YouTube from Connected accounts, revoke access in your Google account, or delete your BeamTake account. Stored YouTube API data is not kept for more than 30 days without being refreshed. You can also ask us to delete it by emailing [email protected].
Connecting TikTok requests user.info.basic and video.publish: used to show
which account is connected (user ID, display name, profile picture) and to post only the clip you choose,
with the visibility and settings you pick in the publish dialog. TikTok's
Terms of Service and
Privacy Policy apply. When you disconnect,
we revoke TikTok access and delete the tokens; you can also remove access in the TikTok app's settings.
Connecting a Facebook Page requests pages_show_list, pages_read_engagement and
pages_manage_posts from Meta: used to list the Pages you can post to (ID, name, profile picture)
and to publish only the clip you choose as a Reel on the Page you choose. Page tokens are stored encrypted;
when you disconnect, we revoke the Facebook permissions and delete the tokens. You can also remove access in
Facebook under Settings → Business integrations.
Connecting Instagram (Instagram Login, professional accounts) requests
instagram_business_basic and instagram_business_content_publish from Meta: used to
show which account is connected (user ID, username, profile picture) and to publish only the clip you
choose as a Reel on your account. No Facebook Page is needed. You can remove access in Instagram under
Settings → Apps and websites; when Meta notifies us, we delete the connection and tokens. We handle
Meta data deletion requests the same way.
Connecting Threads requests threads_basic and threads_content_publish from Meta:
used to show which account is connected (user ID, username, profile picture) and to publish only the clip you
choose, with the text you write, as a video post on your Threads profile. Tokens are stored encrypted. You can
remove access in Threads under Settings → Account → Website permissions; when Meta notifies us, we delete the
connection and tokens.
Connecting LinkedIn requests openid, profile and w_member_social: used to
show which profile is connected (member ID, name, profile picture) and to publish only the clip you choose, with
the text you write, as a public video post on your LinkedIn profile. We do not read your email address or your
connections. The access token is stored encrypted and is valid for 60 days; when you disconnect, we revoke LinkedIn
access and delete the token. You can also remove access in LinkedIn under Settings → Data privacy → Other
applications.
How long we keep data
- Files needed to re-render and edit a project (the audio track, the parts of the video the clips come from and, if you uploaded a file, the source file itself) are deleted automatically 30 days after processing finishes. After that you can no longer re-render or edit that project; the finished clips stay.
- Clips, transcripts and support conversations are kept while your account is open. You can delete clips from your dashboard at any time.
- Trials made without an account are deleted with all their files after 2 days if they are not moved to an account.
- When publishing to Instagram or Threads, the clip is briefly copied to a public URL and deleted immediately after publishing.
- When you disconnect an account, its access token is deleted from our database.
- You can delete your account from the dashboard at any time; see Data deletion. Payment records are kept for as long as tax and accounting laws require.
Cookies
We use only the cookies needed to run the service: a session cookie that keeps you signed in, a cookie that remembers a trial you started without an account, and a cookie that remembers your language. If we enable privacy-friendly analytics on our public pages, it is used only to count visits and does not track you across other websites.
Your rights
Depending on where you live (for example under the GDPR in the EU/UK), you have the right to access the personal data we hold about you, correct it, have it deleted, receive it in a portable format, restrict or object to certain processing and withdraw consent at any time. Most of this you can do yourself in the dashboard; for anything else, email [email protected] and we will respond within 30 days. You also have the right to complain to your local data protection authority.
Security
Access tokens are encrypted at rest (AES-based Fernet) and are never sent to the browser. Passwords are hashed irreversibly. All connections use HTTPS.
Children
BeamTake is not intended for children under 16, and we do not knowingly collect their data.
Changes to this policy
When we update this policy we publish the new version here and change the date at the top. If a change materially affects how we use your data, we will also let you know by email.
Contact
For questions or requests, open a support ticket from your dashboard or email [email protected].