Privacy Policy

1. Account information

When you create an EasyLoop account we collect your email address, which is required. You may also provide a display name during sign-up, but this is optional. Your password is hashed by Supabase Auth and is never stored in plaintext by EasyLoop or accessible to EasyLoop staff.

Your account information is stored in a Supabase-managed PostgreSQL database. EasyLoop does not collect phone numbers, home addresses, date of birth, or government-issued identification.

2. Uploaded video files

Videos you upload are stored in Cloudflare R2 object storage, namespaced to your account. EasyLoop stores the original filename, the object storage path, and any title or description you provide.

Video files are not shared with other users. Files are used only to run the streams you configure. When you delete a video, the file is removed from storage and the associated record is deleted from the database. Files are not subject to an automatic time limit — they persist until you delete them or your account is removed.

3. Streaming configuration and YouTube Stream Keys

To stream to YouTube LIVE, EasyLoop stores the RTMP URL and Stream Key you provide from YouTube Studio. Your Stream Key is stored encrypted at rest in the database using AES-256-GCM encryption. The key is never returned in normal application responses — the app only indicates whether a key has been configured.

Your Stream Key is transmitted in plaintext only to the secure cloud worker that runs the stream. That transmission uses an authenticated HTTPS connection. The key is never written to logs.

Treat your YouTube Stream Key like a password. If you believe it has been exposed, rotate it in YouTube Studio and update it in EasyLoop.

EasyLoop also uses a separate Google authorization limited to the YouTube read-only scope to verify the lifecycle and ingest health of the matching live broadcast. The refresh token is encrypted at rest. This permission does not allow EasyLoop to create, edit, delete, or manage YouTube content and is separate from signing in to EasyLoop.

4. Billing and payment

Payments are processed by Stripe. EasyLoop does not receive, store, or have access to your card number, expiry date, or CVC. Payment details are entered directly on Stripe's hosted checkout page and are subject to Stripe's privacy policy.

EasyLoop stores only your Stripe customer identifier, subscription identifier, current plan, billing cycle dates, and subscription status. These identifiers are used to manage your subscription and respond to billing events from Stripe.

5. Usage records

EasyLoop records metered usage associated with your account, including streaming minutes, storage used, and data transferred. These records are used to calculate usage against your plan limits and to support billing accuracy.

6. Support tickets and diagnostics

When you submit a support ticket, the subject and message you write are stored in the database. The support system is designed to scan ticket text for common credential patterns — such as authorization tokens, API keys, and YouTube Stream Keys — and avoid storing them. However, EasyLoop does not guarantee that all sensitive content will be detected and removed in every case.

If you submit a ticket with a stream attached, EasyLoop may include technical diagnostic information about that stream alongside your ticket. The system is designed to avoid including sensitive credentials such as Stream Keys in diagnostic data, but you should avoid pasting credentials directly into support messages.

Support ticket content is visible to EasyLoop staff for the purpose of helping you.

7. Contextual help system

EasyLoop includes a contextual help feature available to authenticated users. When you use this feature, your support query may be processed by OpenRouter as part of generating a response. EasyLoop aims to limit the context submitted to what is necessary to answer your question. OpenRouter's use of data is subject to their own privacy policy.

8. Monitoring and operational logs

EasyLoop uses Better Stack for operational monitoring and log collection. Logs are used to track system health and investigate issues. Where the application is designed to redact sensitive values — such as Stream Keys and RTMP credentials — it avoids including them in log entries. EasyLoop does not intentionally include account credentials or payment information in operational logs.

9. Rate limiting and deduplication

EasyLoop uses Upstash Redis for rate limiting and alert deduplication on certain features.

10. Cookies and sessions

EasyLoop uses Supabase Auth, which uses session-related browser storage and cookies as part of authentication. EasyLoop does not set advertising cookies, tracking cookies, or analytics cookies. No third-party tracking scripts are loaded on EasyLoop pages.

11. Data deletion

You can delete individual videos from your account. Deleting a video removes the file from storage and the associated record from the database.

Account deletion procedures are being finalized. If you have a privacy-related request regarding your account data in the meantime, contact EasyLoop through the support channel available in your account.

12. Data retention

Retention periods are still being finalized and may vary by data type and by operational or legal need. Specific retention durations have not yet been published for this service. Retention rules following subscription cancellation — including rules for uploaded video files — have not yet been published.

13. Third-party services

EasyLoop uses the following third-party services to operate:

• Supabase — authentication, database, and row-level security
• Cloudflare R2 — video file storage
• Stripe — payment processing and subscription management
• OpenRouter — AI inference for the contextual help feature
• Better Stack — operational log collection and alerting
• Upstash — Redis-based rate limiting and deduplication
• Hetzner — cloud infrastructure for streaming workers

Each of these providers operates under its own privacy policy. EasyLoop does not sell data to any of these providers or to any third party.

14. Security

EasyLoop uses encryption for sensitive data at rest, authenticated connections between services, and access controls to limit which parts of the system can read sensitive credentials. Passwords are hashed by Supabase Auth and are not accessible to EasyLoop. Stream Keys are encrypted in the database. Support ticket content is scanned for secrets before storage.

No security system is infallible. If you discover a potential security issue, contact EasyLoop through the support channel in your account.

15. Changes to this policy

This policy may be updated as the service evolves. The “Last updated” date at the top of this page reflects the most recent revision. Continued use of EasyLoop after a policy update constitutes acceptance of the revised policy.

16. Contact

For privacy questions, contact EasyLoop through the support channel available in your account.