Skip to content

Describe a presenter in one sentence and watch them deliver your script. See how it works

1. What we collect

Only what the service needs to work. There is no advertising network here and no third-party tracking pixel.

  • Your email address and name, so the account exists and we can reach you about it.
  • A one-way hash of your password. We never store the password itself and cannot read it.
  • The scripts you write, the images you upload, and the videos you generate.
  • Your credit balance and a ledger of every reservation, settlement, refund and purchase.
  • A session cookie that keeps you signed in. It is strictly necessary, and there is nothing else to consent to.

2. What we do not collect

We never see or store your card number. Card details go directly to Stripe, our payment processor, and we only receive the result of the payment and a customer reference.

We do not build advertising profiles, we do not sell personal data, and we do not share your scripts or videos with anyone except the rendering provider that produces them.

3. Who processes your data

Three processors are involved in delivering the service, and each sees only the part it needs.

  • A third-party avatar rendering provider receives the script, the voice selection and the presenter image in order to produce the video. It does not receive your email address or your payment details.
  • Stripe processes payments and holds the billing details attached to your customer record.
  • Our hosting and storage platform runs the application and holds the database and the finished video files.

4. Where your videos are stored

Finished videos and generated presenter images are copied from the rendering provider into our own storage, which is served over a content delivery network. This is what stops your library breaking when the provider expires its own links.

A file served that way is reachable by anyone who has its exact address, though the addresses are not listed or guessable in practice. Treat a rendered video as shareable rather than secret, and do not put information into a script that would harm you if the video were seen.

5. How long we keep things

Renders and their files stay until you delete them from your library, which removes the stored file as well as the record. Billing ledger entries are kept for as long as tax and accounting rules require, because they are financial records.

If you close your account, we delete your renders and personal details and retain only what the law requires us to keep.

6. Your rights

You can ask for a copy of your data, ask us to correct it, or ask us to delete it. Where the GDPR or a comparable law applies to you, those rights apply in full, including the right to complain to your local data protection authority.

Write to support@sayline.ai from the address on your account and we will respond within thirty days.

7. Cookies

One cookie, for your sign-in session. It is required for the service to function, it is not used for advertising or cross-site tracking, and it is removed when you sign out.

Visitor statistics for the public pages are collected in an aggregate, cookieless form that does not identify you.

8. Security and breaches

Passwords are hashed, sessions are held in cookies that JavaScript cannot read, and all traffic is encrypted in transit. Database queries are parameterised, so a script you type cannot reach the database as an instruction.

No system is perfect. If a breach ever affects your personal data, we will tell affected account holders and the relevant authority without undue delay.

9. Changes to this policy

If we change what we collect or who processes it, we will update the date at the top of this page and email account holders when the change is material.

Questions about this page

Write to support@sayline.ai and a person will answer. Include the email address on your account so we can find it.

Made with Modulify