Privacy Policy

1. Who is responsible

Eyes Software - FZCO is the controller for account, billing and website data. For content a customer produces — the people, voices and messages in their shows, and the questions and chat on their watch page — the customer decides what to collect and we process it on their behalf.

2. What we collect

• Account data: name, email, password (stored hashed) or Google sign-in, workspace name, members and roles.
• Studio data: scenes, graphics and files you upload, stream destinations (stream keys are encrypted), recordings, watch-page settings.
• Live media: camera, microphone and screen streams of people in a studio. They pass through our media servers to build the program and are only stored when the producer records the show.
• Guest details: the name, title and company a guest types before joining (shown on their name tag).
• Viewer interaction, only if the producer turns it on: the display name and messages in watch-page chat, and the fields of the Q&A form (for example name, email, company and the question).
• Usage and billing: streaming minutes, viewer minutes (counted with a random per-browser id), storage, credit purchases. Card details are handled by our payment provider; we never see full card numbers.
• Technical data: IP address, browser and device type, logs and error reports, used for security, abuse prevention and fixing problems.

3. Why we use it

• To provide Reji: run studios, stream to your destinations, host watch pages, store recordings (contract).
• To bill usage and keep accounting records (contract and legal obligation).
• To keep Reji secure, prevent abuse and fix errors (legitimate interest).
• To send service emails such as receipts, security notices and important changes (contract). We do not send marketing without your consent.
• To measure our ads on rejee.live with Meta: with your consent where the law asks for it first, and otherwise until you opt out (consent or legitimate interest, depending on where you are).
• To see how the public pages of rejee.live are used and where visitors get stuck, with Microsoft Clarity (recordings of visits and heatmaps): with your consent where the law asks for it first, and otherwise until you opt out. What you type into forms is not recorded. Separately we count, without cookies and without anything that identifies you, how many visits reach each step of signing up.

4. Who we share it with

We do not sell personal data. We use carefully chosen providers who process data for us under contract:

• Hetzner Online (Germany/Finland) — servers, databases and media servers.
• Cloudflare — content delivery, security and file storage (R2).
• Stripe — card payments.
• Sentry — error reports (only technical data; browser reports only with your consent).
• Google — only if you choose to sign in with Google.
• The streaming platforms you choose (YouTube, Twitch, Facebook, LinkedIn and others) receive the stream you send them.
• Meta Platforms Ireland — ad measurement on rejee.live (Meta Pixel and Conversions API), with your consent or until you opt out, depending on where you are.
• Microsoft (Clarity) — recordings of visits and heatmaps on rejee.live's marketing, sign-up and top-up pages, with your consent or until you opt out, depending on where you are.

5. Ad measurement (Meta Pixel and Conversions API)

On rejee.live we tell Meta Platforms Ireland Ltd. when someone views a page, creates an account, starts the free trial or buys credit, so we can measure and improve our ads. Your browser sends these events through the Meta Pixel, and our server sends the same events through Meta's Conversions API so they are counted once and not lost to ad blockers.

What we send: the event, the page address, your IP address and browser, Meta's cookie ids (_fbp, _fbc) and, for sign-ups and purchases, your email address and account id as irreversible SHA-256 hashes (never in plain text), plus the purchase amount and currency. Meta may combine this with data it has about you under its own privacy policy and may transfer it outside the EU. Where you are decides how this starts. In the EU and EEA, the United Kingdom, Switzerland, Brazil and Türkiye (and whenever we cannot tell your country) nothing is sent until you accept marketing cookies in the cookie notice (legal basis: your consent). Elsewhere it is on by default (legal basis: our legitimate interest in measuring our ads) and you can turn it off at any time with "Cookie settings / Do not sell or share my personal information" in the footer; a browser that sends the Global Privacy Control signal is treated as having turned it off. Either way, once it is off we stop sending events, in the browser and from our servers, and your choice is remembered.

6. International transfers

We are based in the United Arab Emirates and our servers are in the European Union. When data moves between countries we rely on appropriate safeguards, such as the European Commission's standard contractual clauses, and on providers that offer equivalent protection.

7. How long we keep it

• Account and studio data: while your account is open; deleted within 30 days after you close it, except billing records.
• Recordings: until you delete them.
• Uploaded files nobody uses: deleted after 30 days.
• Live stream segments for the watch page and replays: deleted 30 days after the stream.
• Watch-page chat: the last 200 messages, deleted after 2 days.
• Q&A questions: until the producer deletes them or the workspace is closed.
• Database backups: kept for 14 days.
• Billing and payment records: as long as tax and accounting laws require (usually up to 10 years).

8. Your rights

Depending on where you live (for example under the GDPR, the UK GDPR, the UAE Personal Data Protection Law or Türkiye's KVKK) you can ask to access, correct, delete or export your data, object to or restrict some processing, and withdraw consent at any time. Write to [email protected]; we answer within 30 days. If your data is in a customer's show, chat or Q&A, we will forward your request to that customer. You can also complain to your data protection authority.

9. Security

We use encryption in transit (HTTPS, encrypted WebRTC), encrypt stream keys at rest, limit access to production systems and keep backups. No system is perfectly secure; if a breach affects you, we will tell you and the authorities as the law requires.

10. Children

Reji is not meant for children under 16 and we do not knowingly collect their data. If you think a child has given us data, contact us and we will delete it.

11. Changes

We will post changes on this page and tell account holders about material changes before they apply.