Privacy policy

How Shelly DevKit and this website handle your data. Your Shelly password and token never reach us, and nothing about your devices is sent to us.

Last updated October 7, 2026

Shelly DevKit is made by Sydcup OÜ, a company registered in Estonia (“Sydcup”, “we”, “us”). Sydcup is the controller responsible for the data described here. Our full company details are at the end of this policy.

This policy covers the Shelly DevKit app for iPhone and this website.

The short version

  • Your devices stay between your iPhone and Shelly Cloud. The app talks to Shelly Cloud directly. Your password, your access token, and your devices’ names, IDs, status and requests are never sent to us.
  • There’s no Shelly DevKit account. We have no server that stores anything about you.
  • Google Firebase gives us anonymous usage statistics and crash reports, keeps the app’s wording, documentation fixes and feature switches up to date, and delivers announcements if you turn them on. Usage statistics are on by default and you can switch them off at any time in Settings › Privacy. None of it includes your Shelly account, your token, or your devices’ names or IDs.
  • Purchases go through Apple. We never see your payment details.

Your Shelly account and devices

To work with your own devices, you log in with your Shelly Cloud account. You type your password only into Shelly’s own login page, shown in Apple’s secure sign-in sheet. The app never sees your password.

  • The access token that comes back is stored in the iOS Keychain on your iPhone and sent only to Shelly Cloud.
  • Device data — names, rooms, status, readings and the requests you run — travels only between your iPhone and Shelly Cloud, at your request.
  • On your iPhone the app keeps a cache of your device list, your last 50 API calls (with the token masked), the recipes you compose, and your settings.

Shelly Cloud is run by Allterco Robotics, not by us, and handles your account under Shelly’s own privacy policy. Shelly DevKit isn’t affiliated with Allterco Robotics or Shelly.

Without logging in, the app runs on a built-in demo inventory and doesn’t contact Shelly Cloud.

Services the app uses

Shelly DevKit uses a small number of outside services. Here is each one, what it receives, and what you can do about it.

Firebase Analytics (Google)

  • What is sent: which screens are opened and which features are used — for example, finishing onboarding, opening the paywall or exporting a recipe (with its number of steps) — plus basic device information: device model, iOS version, app version, country and language. Never your Shelly account, token, device names or IDs, or the requests you run.
  • Identifier: a random app-instance identifier that Firebase creates on your iPhone. No user ID and no advertising identifier.
  • Linked to you? No. It isn’t connected to your name, email address, Apple Account or Shelly account.
  • How long it’s kept: event-level data is kept for no longer than 14 months, then deleted. Reports built from it are aggregated.
  • Your choice: controlled by Share analytics in Settings › Privacy. It’s on by default. Turning it off stops collection straight away and resets the analytics identifier on your iPhone.

More: Privacy and security in Firebase and Google’s privacy policy.

Firebase Crashlytics (Google)

  • What is sent: when the app crashes, a crash report — where in the code it happened, the state of the app at that moment, device model, iOS version and app version. When a call to Shelly Cloud fails, the error code and the kind of call (for example, “set/switch”), never the request itself.
  • Identifier: a random installation identifier that Crashlytics creates on your iPhone.
  • Linked to you? No.
  • How long it’s kept: 90 days, then deleted.
  • Your choice: in this version of the app, crash reporting isn’t covered by the Share analytics switch. It contains nothing about your account or devices.

More: Privacy and security in Firebase and Google’s privacy policy.

Firebase Remote Config (Google)

  • What it’s for: updating a few things without an app update — the wording on the paywall, corrections to the API documentation, switches for features in the Build tab, and the address the app’s Help screen writes to. It never carries prices or code.
  • What is sent: a Firebase installation identifier, the app version, the iOS version, and your device’s language, region and time zone. Nothing about your Shelly account, your devices or how you use the app.
  • When: each time you open the app, it checks for new values, and downloads them at most once every 12 hours. While the app is open, it also listens for changes so they arrive without a restart.
  • Identifier: a random Firebase installation identifier created on your iPhone.
  • Linked to you? No.
  • How long it’s kept: Google keeps the installation identifier only while it’s in use, as described in Firebase’s privacy information.
  • Your choice: this isn’t covered by the Share analytics switch. If the app can’t reach Firebase — offline, for example — it uses the values built into the app.

More: Privacy and security in Firebase and Google’s privacy policy.

Firebase Cloud Messaging (Google) — announcements

  • What it’s for: occasional announcements about the app, such as news about an update or a known problem, sent as notifications.
  • When: only if you turn on Announcements in Settings › Notifications and allow notifications when iOS asks. It’s off by default.
  • What is sent: a push token for your iPhone, which Apple and Firebase use to deliver the notification, along with the app version. Your iPhone joins a single “announcements” list that every subscriber shares, so announcements are never personalised.
  • Linked to you? No.
  • How long it’s kept: while you’re subscribed. Turning Announcements off removes your iPhone from the list.
  • Your choice: turn Announcements on or off at any time in Settings › Notifications.

More: Privacy and security in Firebase and Google’s privacy policy.

RevenueCat (purchases)

  • What is sent: when the app starts, it asks RevenueCat for the current Pro plans, sending an anonymous identifier, the app version and your App Store storefront. If you subscribe or restore, RevenueCat also receives the App Store record of your purchase — which plan, when it started, when it renews or ends, and whether it’s a trial.
  • Identifier: an anonymous identifier that RevenueCat creates. We don’t give RevenueCat your name, email address, Apple Account or Shelly account.
  • Linked to you? No — only to that anonymous identifier.
  • How long it’s kept: for as long as needed to keep your purchase working and restorable, and as long as financial-record rules require.
  • Your choice: this is needed to sell and restore Shelly DevKit Pro, so it isn’t covered by the Share analytics switch.

More: RevenueCat’s privacy policy.

What the app never collects

  • your Shelly password or access token,
  • your devices’ names, IDs, rooms, status or readings, or the requests you run and their responses,
  • the email address of your Shelly account,
  • your contacts, location, photos, or anything from other apps,
  • an advertising identifier (IDFA).

Shelly DevKit doesn’t track you across apps or websites, so it never shows Apple’s “Allow tracking” prompt. There is no advertising in the app.

Turning usage data off

Open Settings › Privacy in Shelly DevKit and tap Share analytics to switch it off. It’s on by default, wherever you are, and you can switch it on or off at any time; the change takes effect straight away.

The switch covers Firebase Analytics. It doesn’t cover crash reports (Firebase Crashlytics), app settings updates (Firebase Remote Config), announcements (which have their own switch in Settings › Notifications) or purchase checks (RevenueCat).

Delete local data in Settings › Privacy wipes everything the app stores on your iPhone — the Keychain token, cached devices, request history, saved recipes and your settings. Because it resets your settings, Share analytics is back on afterwards; switch it off again if you want it off. Deleting the app removes the rest.

Purchases

Shelly DevKit Pro is sold through the App Store. Apple processes the payment, and we never see your payment details or your Apple Account. To know whether Pro is active, the app receives the purchase status from Apple and checks it with RevenueCat (see above). You can restore a purchase in Settings › Subscription › Restore purchases, or with Restore purchases on the Pro screen.

Emailing us from the app

Settings › Help has two options, Report an issue and Ask a question. Both prepare an email to contact@sydcup.com in Apple Mail, which you can read and change before you send it. If Mail isn’t set up, you can open the email in your own mail app or copy it instead. Nothing is sent to us unless you send that email. We then receive what you wrote and your email address.

  • Ask a question adds a subject line with the app version and a “Sent from Shelly DevKit” line.
  • Report an issue adds a subject line with the app version and, if Attach diagnostics is on (it is by default), a readable diagnostics block: app version and build; iOS version and iPhone model; your Shelly Cloud server and how many devices you have of each generation (or “not signed in”); whether Pro is active and on which plan; the last failed API call — its error code, method, endpoint path and time; and your language and region. The diagnostics never include your token, the email address of your Shelly account, device IDs, device names or request bodies.

Permissions

  • Notifications. Asked only when you turn on Announcements.
  • Siri and Shortcuts. Recipes you export with Pro, and the app’s built-in actions, run in Apple’s Shortcuts app and can be started with Siri. They use the same Keychain token to talk to Shelly Cloud.

The app doesn’t ask for your location, camera, microphone, contacts, photos or local network.

This website

  • Hosting. This site is hosted on Cloudflare, which processes technical data such as IP addresses to deliver it and protect it from abuse.
  • Analytics. We use Cloudflare Web Analytics, which counts page views without cookies and without tracking you across sites.
  • No forms, no cookies. The site has no sign-up or contact forms and sets no cookies. If you email us, we receive your message and email address.
  • Usage statistics (Firebase Analytics): our legitimate interest in understanding which features are used, so we can improve them. You can object at any time by switching off Share analytics.
  • Crash reports (Firebase Crashlytics): our legitimate interest in finding and fixing crashes.
  • App settings updates (Firebase Remote Config): our legitimate interest in keeping the app’s wording, documentation and features correct without an update.
  • Announcements (Firebase Cloud Messaging): your consent, given when you turn Announcements on. You can withdraw it at any time by turning them off.
  • Purchases and RevenueCat: to provide Shelly DevKit Pro under our agreement with you.
  • Website hosting and security, and replying to your emails: our legitimate interest in running the site and answering you.

Where data is processed

Sydcup is based in Estonia, in the European Union. Google (Firebase) and RevenueCat may process data in the United States and other countries. Where personal data leaves the EEA, the UK or Switzerland, these transfers rely on the European Commission’s Standard Contractual Clauses or an equivalent safeguard. Cloudflare serves this website from data centres around the world.

Children

Shelly DevKit isn’t directed at children under 13, or under the minimum age in your country, and we don’t knowingly collect data from them.

Your rights

Depending on where you live, you may have the right to access, correct, delete or export personal data about you, to object to or restrict how it’s used, and to withdraw consent. You can also complain to a data protection authority — the one where you live, or our lead authority, the Estonian Data Protection Inspectorate (aki.ee).

Most of what Shelly DevKit handles never reaches us. The usage statistics and crash reports we receive aren’t linked to you, so we usually can’t find them from your name or email — but switching off Share analytics stops usage statistics at the source. Data held by Shelly Cloud is managed in your Shelly account. For anything else, email us.

Changes

If this policy changes, we’ll update the date at the top of this page. If a change affects what the app sends, we’ll update this page before the version of the app that makes the change is released.

Contact

See also our terms of use.

Sydcup OÜ
Sepapaja tn 6, 15551 Tallinn, Harju maakond, Estonia
Registry code: 16301471 · VAT: EE102409208
Email: contact@sydcup.com