Layerflow
Back to Layerflow

Privacy Policy

Last updated: 14 October 2026

Who operates Layerflow

Layerflow is operated by Seth-Moses Ellermann, Pfauengasse 8/22, 1060 Wien, Austria. Contact us at support@layerflow.app for privacy questions or requests.

This policy covers layerflow.app and its cloud video editor. Layerflow stores project media on servers and sends selected content to AI providers when you request processing.

Information we process

We process your name, email address, email verification status, account and workspace membership, sign-in sessions and security metadata. Projects contain uploaded footage, images, audio, scripts, captions, speaker references, generated media, editing instructions and saved brand assets. Files may contain the voices, images and personal information of other people.

Subscription and usage records include your selected plan, customer and payment identifiers, credit grants, reservations and charges. Payments are handled through Stripe Managed Payments and Link. Payment details are entered in Stripe’s hosted checkout; Layerflow does not store your full card number. We receive payment and subscription status information needed to manage workspace access, credits and billing support.

Technical data can include IP addresses, request times, browser information and error logs needed to operate and protect the service. Support correspondence contains the information you choose to send us. Abuse reports and investigations may include the reported content, relevant account or project identifiers, evidence of rights or speaker permission, and our response. We use this information to investigate misuse and protect affected people, restricting access to those who need it for that purpose.

Why we process information

We use account and project information to provide the editor, save your work, manage workspace access and perform processing you request. Where you are our customer, this processing is necessary to perform our agreement (Article 6(1)(b) GDPR). For business workspace members and support contacts, administration and responding to requests can also serve our legitimate interests (Article 6(1)(f)).

Security checks, preventing abuse, troubleshooting and protecting the service are based on our legitimate interests. Accounting and other legally required records are processed to meet legal obligations (Article 6(1)(c)). Where a feature requires consent, we request it separately; consent can be withdrawn for future processing.

For personal information in client footage, your organisation decides what to upload and why. Where we process that information on your organisation’s instructions, your organisation acts as controller and Layerflow acts as processor. Contact support to arrange the data processing terms needed for your business use before uploading client personal data.

AI processing and other recipients

When you request a feature, relevant audio, video, scripts or speaker references are sent to the provider delivering it. The categories of processing services we use include:

Hosting, object-storage and email providers process the data needed to store files, run the service and deliver essential account messages. We do not publish your private projects merely because you upload or process them. Workspace members with appropriate access can view shared projects and media.

Providers may process information outside the European Economic Area. Applicable provider agreements and lawful transfer arrangements must cover those transfers. Contact support for the current provider and contractual details before using Layerflow for footage subject to particular confidentiality, residency or regulated-data requirements. This policy does not promise that every provider processes data only within Europe or that provider-side retention ends immediately when you delete a Layerflow file.

Layerflow’s AI features analyse or transform media. We do not use them to make decisions about employment, credit or other legal eligibility.

Storage and deletion

We retain active accounts, projects and media while they are needed to provide your workspace. Moving a file to Trash is reversible and does not immediately remove it from storage. Trashed media is scheduled for permanent removal after seven days; references in projects do not prevent that removal, so those projects can lose access to the file. Deleting a project does not automatically delete shared media in the library.

Contact support to request account closure, removal of generated voice references or assistance deleting personal information. Account closure is handled through support rather than an immediate self-service account-delete button. Financial records, evidence of a trial grant and security records may need to remain for legal obligations, fraud prevention or legal claims. Storage backups and provider systems can have separate deletion schedules; contact us for the schedules applicable to your request.

Cookies and browser storage

Sign-in uses necessary cookies. When you select a website language, we save that preference in a cookie for up to one year. The editor uses browser storage and local caches for editing state, preferences and media previews. These caches are separate from the cloud library. Clearing browser storage signs you out or removes cached editing data; it does not close your account or delete server-side files. We do not require advertising cookies to use the editor.

Your rights

Depending on the applicable law, you can request access, correction, erasure, restriction or portability of your personal information, and object to processing based on legitimate interests. You may withdraw consent where processing relies on consent. Contact support@layerflow.app; we may need to verify your identity or direct a request about client footage to the organisation responsible for it.

You can complain to your local data protection authority, including the Austrian Data Protection Authority. We will communicate material changes to this policy and keep the current version available here.