afterlive.About Afterlive

AFTERLIVE · LEGAL

Privacy Policy

What Afterlive collects, how clip processing works, and how you can control your information.

Last updated: September 11, 2026

1. Scope and contact

This policy covers the Afterlive website and the processing and publishing service operated under the Afterlive name ("we", "us", or "our"). It does not replace the policies of platforms you connect or visit. Contact the Afterlive operator about privacy, access, correction, deletion, or account closure using our privacy request form.

2. Information we collect

  • Account information: an account identifier and the name and email made available by your sign-in provider. With Google sign-in, this includes your Google account ID, verified email, name, and a session record. We do not receive your Google, ChatGPT, or social account password.
  • Your workspace: selected streamer handles and URLs, VOD links, clip titles and media, transcripts created during processing, caption preferences, schedules, time zone, plan, destinations, and processing or delivery results.
  • Connected account data: platform account or channel IDs, display names, authorization permissions, access and refresh tokens, token expiration, and upload references or results. YouTube supplies channel information; TikTok supplies your account identifier and display name; Meta supplies the selected Facebook Page and linked professional Instagram account information.
  • Billing information: Stripe customer and subscription identifiers, plan, and payment/subscription status. Stripe processes payment card and billing details. Afterlive does not store full payment card numbers.
  • Support and technical information: the email, topic, and message you submit through our contact form, support status, worker connection information, job errors, and security or operational logs. Hosting and connected service providers may also process network and request information, such as IP addresses, to deliver and protect their services.

3. How we use information

We use this information to sign you in, maintain your workspace, find or process the VODs you select, generate clips and captions, create titles, run your chosen schedule, upload to authorized destinations, manage subscriptions, respond to requests, and investigate failures or abuse.

Where a legal basis is required, we rely on providing the service you request, your consent for optional connections, legitimate interests in operating and securing the service, and compliance with legal obligations, as applicable. You may disconnect optional accounts and withdraw authorization through the relevant platform.

We do not sell personal information, use connected account data for advertising, or use your VODs, transcripts, clips, or Google API data to train or improve AI models.

4. Website storage and local PC processing

Account, schedule, connection, and job records are stored in the hosted service’s database. Generated clips are stored in hosted media storage. Access to clips requires your authenticated workspace or a time-limited media link used for delivery to a platform.

Clip processing runs on a Windows computer controlled by the Afterlive operator. It downloads selected VODs, transcribes audio, generates titles with local models, and renders clips. This is the business’s processing computer; it is not necessarily your own device. Source footage, transcripts, rendered clips, and processing reports may be present on that computer and accessible to the operator for service operations and support.

The current local processing workflow does not send your footage or transcripts to a hosted generative AI service. It downloads model software separately. Publishing also uses the operator’s authorized worker and the official destination APIs. The worker receives the credentials needed for an assigned upload; account connection credentials are encrypted in the hosted database.

5. When information is shared

  • Infrastructure: the hosting, database, and storage providers supporting this website, including OpenAI’s Sites service and Cloudflare, process information needed to operate it.
  • Sign-in and billing: Google or ChatGPT provides your chosen sign-in flow, and Stripe processes authorized payments and subscriptions.
  • Sources and destinations: Twitch, YouTube, or Kick receives requests for source information or footage. When you authorize delivery, the destination platform receives the clip, title, and other information necessary for that upload. Instagram may fetch a clip using a time-limited URL. Your selected platform privacy settings determine who can see published content.
  • Service operations and legal needs: authorized support may handle information needed to resolve your request, investigate security issues, protect rights, or comply with a valid legal requirement. We do not grant third parties access for their own advertising.

These providers may process information in countries other than your own. Their terms and privacy practices apply to their services. Relevant policies include Google’s Privacy Policy, TikTok’s Privacy Policy, Meta’s Privacy Policy, and Stripe’s Privacy Policy.

6. Google and YouTube API data

Afterlive uses YouTube API Services to retrieve source or channel information and upload clips you authorize. Google sign-in requests your basic profile and email. Connecting YouTube separately requests access to identify your channel and upload videos. We do not request access to your Gmail messages or Google Drive files.

Afterlive’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google API data is used for the user-facing features you request, not advertising, sale, or training general-purpose AI models. Human access is limited to the circumstances allowed by that policy, such as your specific consent for support or a necessary security or legal purpose.

You can revoke access through Google account permissions. To request deletion of stored Google or YouTube data as well, submit a deletion request. Revoking a platform grant and deleting stored service records are separate actions.

7. Retention and deletion

Workspace records and hosted clips are kept while needed for your account, processing queue, publishing history, and service support. They are not automatically erased when you disconnect a channel. Disconnecting removes the connection credentials stored by Afterlive; it does not remove past posts from the destination platform or every historical job record.

On the processing computer, the worker removes a source download after its job completes successfully. Failed source downloads, transcripts, rendered clips, publishing copies, and reports can remain until the operator removes them. There is currently no automatic expiration for those local media files. A verified deletion request includes eligible copies on the processing computer as well as hosted records.

Google sessions expire after seven days, and short-lived authorization state expires after ten minutes; expired records are cleaned up during subsequent authentication activity. Closed contact requests are eligible for removal after 90 days and are cleaned up during subsequent support activity. Open requests are kept while being handled.

Use the deletion request form to request removal of your account or particular data. The operator may need to verify your identity before acting and will respond with the scope and timing of the request. Some billing, dispute, security, or legal records may need to be retained where permitted or required. Copies already published on social platforms must also be managed through those platforms.

8. Your choices, cookies, and security

You can edit workspace preferences, turn off autopilot, disconnect channels, revoke permissions on each platform, and manage subscriptions through the billing portal. Depending on your location, you may have rights to access, correct, delete, obtain a copy of, or restrict or object to certain processing of your information, and to complain to your local privacy authority. Use our privacy request form to exercise these rights.

Afterlive uses necessary sign-in, session, and authorization-state cookies, plus interface preference storage where applicable. The application does not currently include advertising trackers or an analytics tracking SDK. The hosting layer and platforms you visit may use their own cookies under their policies.

We use measures such as HTTPS, authenticated workspace access, encrypted stored connection credentials, and limited worker authorization. No system can guarantee absolute security. Do not include passwords, API keys, payment card numbers, or unnecessary sensitive information in source content or support messages.

9. Children and changes

Afterlive account registration is intended for adults aged 18 and over. If you believe a child has provided account information, contact us so we can investigate and remove it as appropriate.

We may update this policy as the service changes. The date at the top identifies the latest version. We will provide additional notice of material changes where required. Questions can be sent through the contact form.

Afterlive
Terms of ServicePrivacy PolicyContact & support