Privacy policy

Who we are

Comps.gg builds and runs competition websites for the businesses that operate them, and makes the Companion app so their staff can check on their site from a phone.

Comps.gg is a trading name of Louth to Mouth Ltd, registered in England and Wales, company number 14342603, registered office Excel House, Millbrook Lane, Wragby, Market Rasen, Lincolnshire, LN8 5AB.

Questions about this policy or your information: [email protected].

Who the app is for

The app is for staff of a competition site built on Comps.gg: admins and shop managers whose account has two-factor authentication turned on. It is not for the site's customers, and not for anyone under 18.

It shows you your site's sales, competitions, orders, winners and customers.

Your site's data, and who is responsible for it

The app talks to one place only: the competition site you connect it to. That site belongs to its operator, the business that runs the competitions. Comps.gg hosts and runs the site for them.

• The site's customers' details (names, email addresses, phone numbers, postal addresses, dates of birth, orders, wallet balances and the like) belong to the operator. The operator decides how they are used and is responsible for them; Comps.gg handles them only on the operator's behalf. Customers with questions about their details should contact the competition site they use.
• The app itself, and the information it keeps on your phone, are Comps.gg's responsibility, and are what the rest of this policy describes.

When you connect the app

You connect by scanning a QR code from your site's admin panel. The code is single-use and lasts five minutes. Once, when you scan it, the app sends your site:

• the code itself;
• your phone's name (the name you gave it in Android settings, or else its make and model) and that it is an Android phone;
• the app's version;
• an identifier Android gives the app on your phone (its Android ID). Android ties it to the phone, your Android user and our signing key, so apps from other developers see a different one. It stays the same if you reinstall, and changes if the phone is factory reset. The site uses it to recognise your phone if you connect it again.

Your site records the phone's name, platform, app version, when it was connected and last used, and the internet address it connected from. This is the list of Connected Devices under your account in the admin panel, where you can see which phones have access and revoke any of them.

Your site's security log also notes each pairing: the time, your account, the phone's name, platform and app version, and the internet address it came from.

What the app keeps on your phone

• Your connection: the site's name, web address and logo; your name, email address and role on the site; and the sign-in tokens that let the app ask the site for data. These are encrypted with a key that is created in your phone's Android Keystore and never leaves it.
• What your widgets and countdown show: today's revenue or new customers and order count, the counts behind "needs your attention", and the competition you pinned a countdown for. This is encrypted in the same way, so the widgets can draw while the app is closed.
• Images such as competition and prize pictures and your site's logo, cached so they load quickly.
• Your settings, such as whether the widgets hide their figures.

Everything else you look at, including customers' details, is fetched from your site when you open a screen and kept in the app's memory only while you use it. The app doesn't save it to your phone.

Some screens let you copy a detail, such as an order number or email address, or tap an email address or phone number to open your email or phone app. That only happens when you ask. What you copy sits on Android's clipboard, and what you hand to another app is then handled by that app.

Nothing is backed up to Google or copied to a new phone. A connection stays on the phone it was made on.

While you use it

• The app sends your site only what it needs to work: the pairing details above, requests for the screens you open, what you type into search, and anything you do in the app. Each request carries the app's sign-in token.
• Your site sees each request and its internet address, as it does when you use the admin panel in a browser, and logs requests for security and troubleshooting.
• The site only returns what your role may see. A shop manager sees no more in the app than in the admin panel.
• If you add a widget or pin a countdown, the app refreshes it from your site about every 15 minutes in the background.

Compy, the AI assistant (Android and iOS)

Compy uses Anthropic's Claude API. When you ask a question, the app sends it and recent chat history to your competition site's server. The server sends that text to Anthropic and may fetch site data to answer it. Those results are restricted by your role, but they are not all anonymised: depending on the question, they can include customer names, contact details, orders, spending and other permitted site records.

Device names and identifiers used for pairing are not automatically included in AI requests. The app does not send Anthropic your phone's internet address directly: the site's server makes the AI request. Anything you type into the question can still be included, so only share information you are authorised to use.

From iOS version 1.1.0, the app explains this and asks you to tap Allow AI sharing before using Compy. You can decline and keep using the rest of the app. Permission is held in memory for the app session; it is asked for again in a new session. This permission screen is not yet present in the Android version. Compy is not available in the Mac app.

The app holds the conversation in memory, not on disk. New chat, disconnecting or ending the app session clears it locally. This does not delete copies already sent to providers or included in diagnostic reports. Anthropic handles API inputs and outputs under its commercial data-retention policy and model-training policy; we do not promise zero retention.

If Compy cannot answer, the server can create a diagnostic issue in our private GitHub repository containing the question, recent user questions and a limited answer. It removes recognised email addresses, phone numbers, postcodes, identifiers, monetary amounts and tables, and withholds the answer when a customer-data tool ran. These protections are not a guarantee that every personal detail is removed: for example, a name in ordinary prose may remain. These reports are available to authorised repository users for troubleshooting and are kept until removed; there is no automatic deletion period. Tool audit logs record the tool, redacted lookup arguments, row count and the operator's account ID, not the result payload.

If you tap Email me, your site sends that question and answer to the email address on your own site account through its email provider. Copy puts the answer on the device's clipboard.

Permissions

• Camera, only to scan the QR code that connects the app. The picture is read on your phone by Google's ML Kit barcode scanner and is never stored or sent anywhere. See Google's ML Kit below for what the scanner itself sends Google.
• Fingerprint, face unlock or screen lock. The app locks when you leave it and after 5 minutes without use, and asks Android to check it's you. Android does the check and only tells the app whether it passed. The app never receives your fingerprint, face or PIN.
• Notifications, only for a countdown you choose to pin. The app sends no other notifications.
• Internet, to talk to your site.

Home-screen widgets show your figures to anyone who can see your home screen. You can switch on "Hide amounts on widget" in the app's settings.

Google's ML Kit (Android)

The QR scanner is Google's ML Kit, built into the app. Google says ML Kit sends it, encrypted, for diagnostics and usage analytics: information about your phone (such as its make, model and Android version), the app's name and version, an identifier for this installation that isn't meant to identify you or the phone, and figures such as how fast the scanner ran and how it was set up. Google lists no pictures or scanned content among it, and says it doesn't share this with third parties. See Google's ML Kit data disclosure.

On iPhone

Everything above applies to the iPhone app too, except:

• When you connect, the app sends your phone's name as iOS gives it to apps (usually just "iPhone"), that it is an iPhone, the app's version, and the identifier iOS gives apps from the same developer on your phone (its identifier for vendor) in place of the Android ID. Apps from other developers see a different one. It changes if you remove every Comps.gg app from the phone, and the site then treats it as a new phone.
• Your connection is kept in the iOS Keychain, readable only by the app and its own widgets, only on this phone and only while it has a passcode. It is never included in iCloud or computer backups and never copied to a new phone.
• What your widgets and countdown show is kept in a storage area the app shares only with its own widgets. It is protected by iOS's file encryption until you first unlock the phone after it starts, so widgets can draw while it is locked, and it is never included in backups. Disconnecting deletes it.
• The countdown is a Live Activity on your lock screen and in the Dynamic Island, not a notification. iOS ends it after 8 hours, and opening the app restarts it while the competition is still in its last 48 hours. The app sends no notifications.
• Background refresh: while a widget is placed or a countdown is pinned, the app asks iOS to refresh them about every 15 minutes, and iOS decides when it actually runs. While the phone is locked the app can't read your sign-in, so widgets keep their last figures until you unlock it.
• Your settings are just "Hide amounts on widget", kept on this phone until you delete the app.
• Copying a detail puts it on the iPhone's clipboard. Customers' details are copied for this iPhone only, so iOS doesn't pass them to your other Apple devices through Universal Clipboard.
• Camera: the QR code is read on your phone by Apple's own iOS scanner. No third-party code is involved, so nothing is sent to Google or anyone else.
• Face ID, Touch ID or passcode: iOS does the check and only tells the app whether it passed. The app never receives your face, fingerprint or passcode.
• Deleting the app: iOS removes the app's files but keeps its Keychain items, encrypted and readable only by the app. If you install the app again, it deletes the old connection the first time it opens, so you have to connect again. Revoke the phone in the admin panel as well, as described under Delete your Comps.gg Companion data.

On Mac

The Mac app lives in the menu bar. It shows fewer things than the phone apps: your site's revenue and new customers, the next competition to end and your most popular one, and what needs your attention, each with a link that opens your admin panel in your browser. Everything above applies to it too, reading "Mac" for "phone", except:

• When you connect, you don't scan a code: you paste the pairing link or a screenshot of the QR code, drop a screenshot onto the app, or click the pairing link in your browser. The app shows the site and its address, and sends nothing until you click Connect. It then sends the code, your Mac's name as macOS gives it to apps (the name in System Settings › General › About), that it is a Mac, the app's version, and your Mac's hardware identifier in place of the Android ID. The hardware identifier is the same for every app on the Mac and doesn't change if you reinstall the app, so your site recognises the Mac if you connect it again. If the app can't read it, it makes a random one and keeps it in its settings.
• Reading a screenshot of the QR code happens on your Mac, with Apple's own Vision framework. The image isn't stored or sent anywhere. The app reads the clipboard only when you click Paste, and has no access to the camera.
• Your connection (the site's name and web address; your name, email address and role on the site; and the sign-in tokens) is kept in the macOS Keychain, readable only by the app, only on this Mac and only while it is unlocked. It is never synced through iCloud Keychain.
• The app runs in Apple's App Sandbox, so its own files are in a folder only it can read, and it can't see your other files apart from a screenshot you drop onto it.
• Nothing else is saved. Your site's figures and its icon are held in the app's memory while it runs. No images are cached, and the app never receives customers' details: for those, it opens your admin panel.
• Your settings are what the menu bar shows, the period the figures cover, whether amounts are hidden, and your admin panel's address if you set one.
• While it runs, the app asks your site for its figures about every 45 seconds and for what needs your attention every minute, and fetches your site's icon after connecting. It stops while your Mac is asleep. There are no widgets, countdowns or background refresh, and it sends no notifications.
• No app lock and no permissions. The figure in the menu bar is the point of the app, so your Mac's own login protects it. "Hide amounts" blanks every amount, for screen sharing.
• Launch at login is off until you turn it on in the app's Settings. macOS lists it under Login Items, where you can turn it off too.
• Updates come from the Mac App Store under Apple's terms. The app itself talks only to your site, and fetches your site's icon from the address your site gives for it, which may be on another server your site uses, such as one that hosts its images.
• Deleting the app: disconnect first (the gear menu, then Disconnect this Mac), so your site removes the Mac and the app deletes your connection. Moving the app to the Bin leaves its settings folder and Keychain item behind, readable only by the app. Revoke the Mac in the admin panel as well, as described under Delete your Comps.gg Companion data.

What the app doesn't do

• No adverts, and no advertising identifier.
• No analytics or tracking tools of our own. The data sent to your site, Anthropic and GitHub when using Compy, and Google by the Android QR scanner, are described above.
• We don't sell your information or share it for advertising.
• No location, contacts, photos or files.

How long it's kept

• On your phone, your connection and what the widgets and countdown show stay until you disconnect, your site ends the connection, or you uninstall the app. Your settings and cached images stay until you uninstall the app or clear its storage in Android settings.
• Your site ends the connection when you revoke the phone, and also if your password is changed or reset, you sign out everywhere, or your account is locked or archived. The app then can't fetch anything more (in rare cases it can for up to 15 minutes), and deletes your connection and widget data the next time it tries.
• Your site keeps the phone's device record until the phone is disconnected or revoked.
• Pairing codes are deleted within an hour of expiring.
• Your site's server logs, which include each request's internet address, are deleted after 30 days.
• Security log entries about pairing and revoking are kept permanently, as the site's record of who had access. The internet address and browser details in them are cleared after 180 days.
• Compy provider data and diagnostic reports follow the handling described under Compy; clearing the local chat does not delete those copies.
• What ML Kit sends Google is kept by Google under its own policy.

Delete your Comps.gg Companion data

You can delete what Comps.gg Companion holds about you at any time, in any of these ways:

• In the app: open Settings (the cog on the dashboard) and tap Disconnect (on a Mac: the gear menu, then Disconnect this Mac). The app deletes your connection, sign-in tokens and widget and countdown data from your phone, and tells your site to remove the phone. If the phone is offline, the phone's copy is still deleted; then revoke it in the admin panel as below.
• In your site's admin panel, signed in to the account you connected the phone with: open Companion App at the foot of the sidebar (or Settings › App › Companion App), find the phone under Connected Devices and click Revoke. The phone loses access straight away (in rare cases within 15 minutes) and deletes its connection and widget data the next time the app tries to use it.
• Uninstalling the app deletes everything on the phone, including your settings and cached images. It doesn't tell your site, so revoke the phone in the admin panel as well.
• By email: write to [email protected] from the email address on your site account, saying which site and which phone. We'll remove the phone and confirm within a month.

What is deleted: your connection, sign-in tokens and widget and countdown data on your phone (and, if you uninstall, your settings and cached images too), and the phone's device record on your site with its sign-in sessions. The pairing code you scanned is deleted within an hour of expiring, whatever you do.

What is kept, and for how long:

• Security log entries recording that the phone was paired and removed (the time, your account, the phone's name, platform and app version) are kept permanently in your site's security record, so its operator can always check who had access. The internet address and browser details in them are cleared after 180 days.
• Server logs of the app's requests are deleted after 30 days.
• What ML Kit sent Google is kept by Google under its own policy; we can't delete it.
• Your account on the competition site isn't affected. It belongs to the site's operator: ask them if you want it closed.

Your rights

Under UK data protection law you can ask for a copy of the information held about you, and ask for it to be corrected or deleted. You can also object to how it is used, or ask for that to be limited. Email [email protected] and we will reply within a month. If your request is about a competition site's customer records, we will pass it to that site's operator, who is responsible for them.

If you're unhappy with how we handle your information, you can complain to the Information Commissioner's Office at ico.org.uk. We'd like the chance to put it right first.

Changes to this policy

If the app starts handling information differently, we will update this page and the date at the top before the new version is released.