Privacy policy
Effective date: October 10, 2026. This policy covers the ScreenGecko apps for Android, iPhone and iPad, Mac and Windows, the helper console at screengecko.app/app, and this website.
The short version
- Your screen is never recorded. The picture goes directly between the two devices while a session is open, and ScreenGecko does not store it.
- Only helpers have accounts. The person being helped does not sign in.
- ScreenGecko keeps a short record of each session (when it started and ended, who ended it) for 90 days, never what was on the screen.
- We do not sell your information, show ads, or use it to train AI.
Who we are
ScreenGecko is made by G3NO SYSTEMS LLC ("we", "us"). Contact us at support@screengecko.app.
What we collect
| What | From whom | Why |
|---|---|---|
| Email address and the name you choose | Helpers | To sign you in with an emailed code and to show your name to the person you help. |
| Session details: when a session was created, joined, connected and ended, who ended it, and the kind of device (for example "Android" and the phone model) | Both sides | To run the session, show the helper their recent sessions, and investigate problems or misuse. |
| An optional label for the person you help (for example "Mom") | Helpers | For your "people I help" list. |
| Connection details exchanged to set up the video link (network addresses inside the setup messages) | Both sides | To connect the two devices. Deleted when the session ends. |
| A one-way, scrambled version of your network address | Anyone using a code or signing in | To slow down people guessing codes. Kept for up to one day. |
| A notification token for your device | Helpers who allow notifications | To tell you when someone you help asks for help again. |
| Groups you make for the people you help (for example "Clients") | Pro helpers | To sort your "people I help" list. |
| Your business name and logo (Pro branding) | Pro helpers who add them | To show them to the person you help, on the screen that asks them to share and during the session. Your logo is stored as a public picture. Whenever your business name is shown, your sign-in email address is shown under it, so the person can check who you really are. |
| Session notes and reports: your notes, the device model and system version, start and end time, which tools were used, the names of guides and files sent | Pro helpers | For your own records ("Past sessions"), a PDF on your device, or an email you choose to send. Never the screen picture, the camera picture, the contents of files or what was typed. |
The 6-digit codes and the secret keys that let a phone talk to its session are stored only in scrambled (hashed) form, so a copy of our database would not reveal them.
What we do not collect
- We do not record, store or look at the screen, the camera picture or anything typed during a session.
- The list of what is on the screen (used for "find things by name" on Android) goes only to the helper during the session and is not stored by us. Password fields are always hidden.
- Files sent during a session (a Pro feature, between a helper and an Android phone): a file goes directly from one device to the other inside the same encrypted session (through the relay only when a direct connection is not possible, still encrypted). We do not receive, store or look at it. It is saved only on the receiving device, and only after that person taps Accept.
- Talk (voice during a session, where the app offers it): the sound goes directly between the two devices inside the encrypted session, only while Talk is on. We do not record or store it.
- We do not collect contacts, photos, location or advertising IDs.
How a session works
When the person being helped agrees, their phone sends its screen directly to the helper's device, encrypted, using WebRTC. When a direct connection is not possible, the encrypted stream passes through a relay server (Cloudflare) without being stored or decrypted by us. The session ends when either person taps Stop or End, or after a time limit.
Android permissions
- Screen capture. Android asks the person every time before their screen is shared. A red bar and a notification stay visible while sharing.
- Accessibility service ("ScreenGecko remote control"). Only if the person switches it on during a session, so the helper can tap, swipe, type and find items on the screen by name. It works only while a session is open and switches itself off when the session ends. ScreenGecko does not use it to collect or store data.
- Display over other apps. Optional, so the helper's pointer and drawings show on top of other apps. It only draws; it does not read the screen.
- Camera. Only if the person chooses to show their camera instead of the screen. Nothing is recorded.
- Microphone. Only while Talk is on during a session. Nothing is recorded.
- Notifications. To show that sharing is on and to offer a Stop button.
On iPhone and iPad, Apple's screen broadcast is view-only: no one can tap or type on an iPhone or iPad through ScreenGecko. On a Mac or Windows PC being helped, the helper can use the mouse and keyboard only after the person allows it during the session, and the person can stop it at any time.
Paid plans and payments
Only helpers pay; the person being helped never pays and never sees a price. In a web browser you pay through Stripe; in the ScreenGecko Android app you pay through Google Play; in the ScreenGecko iPhone and iPad app you pay through the Apple App Store. Your card or bank details go straight to Stripe, Google or Apple: ScreenGecko never receives or stores them.
For a paid plan we store, linked to your helper account:
- Your plan (Free, Family or Pro), monthly or yearly, its status (for example active, payment overdue, canceled), when the current period ends, and whether it is set to end.
- For Stripe: the Stripe customer, subscription and price identifiers, so Stripe and ScreenGecko refer to the same subscription.
- For Google Play: the product and plan identifiers, the order identifier, whether it was a test purchase, and a one-way, scrambled (SHA-256) form of the purchase token. The token itself is not stored.
- For the App Store: the product identifier, Apple’s original and latest transaction identifiers for the subscription, its state as Apple reports it, and whether it was a test (sandbox) purchase. Your Apple Account is not shared with us; Apple tells us only that this purchase belongs to your ScreenGecko account.
- The identifiers of payment notifications we already handled, so none is applied twice.
- If you redeem a promo code or we give you a plan: the plan, when it ends, and the code in a one-way, scrambled form.
- How many minutes of help you used today, worked out from your session start and end times (Free includes 15 minutes a day).
Stripe, Google and Apple keep their own payment records under their own privacy policies. We keep billing records while your account exists and as long as the law requires afterwards. To change or cancel a plan, see Support.
Who processes data for us
- Supabase (database and sign-in), servers in the United States.
- Cloudflare (relay for video connections, when a direct connection is not possible).
- Google Firebase (hosting this website and the helper console; Firebase Cloud Messaging for Android notifications).
- Apple (Apple Push Notification service for iPhone notifications).
- An email delivery service, to send sign-in codes.
- Microsoft 365, to send a session report by email when a Pro helper asks for it (from no-reply@screengecko.app, to the addresses the helper types).
- Stripe, Google Play and the Apple App Store, to take payments for paid plans.
How long we keep it
- Session records: 90 days after the session ends, then deleted automatically.
- Video connection setup messages: deleted when the session ends.
- Scrambled network addresses used against code guessing: up to one day.
- Your account, name, "people I help" list and groups, business name and logo, and notification tokens: until you delete them or your account.
- Session notes and reports: until you delete them or your account (they stay readable if your Pro plan ends).
Your choices
- Remove someone from your "people I help" list at any time in the console. A person can also remove a saved helper from their phone.
- Delete your helper account yourself in the app (Settings, Delete account), or ask us to see, correct or delete your information, or to delete your account, by emailing support@screengecko.app from the address you sign in with. Deleting a helper account deletes its sessions, list, groups, branding (including the logo picture), reports and tokens. Deleting the account does not cancel a store subscription: cancel it where you bought it first (see Support).
- Turn off notifications in your device settings.
Security
Sessions are encrypted in transit. Codes work once and expire after 10 minutes, and repeated wrong codes are slowed down. Database access is limited by row-level security so each helper sees only their own data.
Children
Helper accounts are for adults. ScreenGecko is not directed at children under 13.
Changes
If we change this policy, we will update the date above and, for important changes, tell helpers by email or in the app.