Nothing about you, and crash reports and usage counts only if you say yes.

Last updated 12 October 2026.

This policy is written in English and translated into the other languages of this site. If a translation and the English differ, the English version applies.

Who we are

Sonopley is developed by Lumynay AB. Questions about this policy, or anything else, go to info@sonopley.com.

The controller responsible for the crash reports and usage counts described below is Lumynay AB (Sweden), reachable at info@sonopley.com.

Mail you send to info@sonopley.com is kept in our mailbox at our host, Simply.com, in Denmark, and deleted 24 months after the last message in the conversation; the host's backups of it are gone about 30 days later.

What we collect

Only two things, both from the iPhone app and each only if you agree: crash reports and anonymous usage counts, as the next two sections describe. Nothing else: no account and nothing about who you are.

Crash reports from the iPhone app

The first time you open the iPhone app, it asks whether it may send a report if it crashes. Until you say yes, it sends none.

A crash report carries only:

• What went wrong: the kind of error, its message, and where in Sonopley's own code it happened.
• Which Sonopley: the app's version and build number.
• Which iPhone: the iOS version and the model of the phone.

It never carries the names of your rooms, speakers, songs, music services or accounts, addresses on your network, or sign-in tokens — anything like that is removed on the phone before the report is sent. It carries no record of what you did before the crash, no performance measurements, no usage sessions and no identifier for you or your phone.

Reports go to Sentry, a crash-reporting service run by Functional Software, Inc., which stores them for us in its EU region in Frankfurt, Germany, wherever you are. Sentry is told not to store the IP address a report comes from, and deletes every report automatically after 90 days at most. We use the reports only to find and fix what made Sonopley crash.

Functional Software, Inc. is a US company, and its staff may reach the reports from the United States, for example to keep the service running. That is covered by the EU–U.S. Data Privacy Framework, under which Sentry is certified, and by the EU's standard contractual clauses in Sentry's data processing agreement.

If you said no, a crash is written down on your phone only and nothing is sent. The next time you open the app, it says that Sonopley closed unexpectedly and asks whether to send a report of that crash and turn crash reports on. Yes sends that one report and turns reporting on; No deletes it; Don't ask again stops the question for good.

You can change your answer at any time with the crash reports switch in the app's Settings. Turning it off stops any further reports; reports already sent stay at Sentry only until they are deleted as above.

We receive crash reports only because you agreed to send them — consent, under Article 6(1)(a) of the GDPR — and you can withdraw it at any time with the same switch.

The Windows app sends no crash reports.

Anonymous usage counts from the iPhone app

The same first-start question asks whether the app may share anonymous usage counts, so that we can see which features are used and decide what to build next. Until you say yes, nothing is counted and nothing is sent.

With your yes, the app counts on your phone how often each feature on a fixed list is used — such as starting a song, an album or a station, skipping a track, changing the volume or adding to the queue — and once a week sends a report carrying only:

• Which Sonopley: the app's version.
• Which iOS: its main version number only, such as 26.
• Which week: the year and the week number.
• The counts: how many times each feature on the list was used that week.

It never carries what you played, searched for or chose — no song, artist, album, playlist, station, room, speaker, music service or account — and no identifier for you or your phone, so nothing in a report tells us which phone it came from. Under “See what's sent” in the app's Settings you can read this week's report exactly as it would be sent.

Reports go to Sonopley's own server, which our host, Simply.com, runs for us in Denmark. A report is stored with neither the address it came from nor the time it arrived — only the week it counts — and under a random number rather than in the order reports arrived, so it cannot be matched to the host's logs, which are kept for three weeks and which we do not use to follow anyone. Each report is kept on its own for at most 30 days and then added into weekly totals for all phones together, after which it no longer exists; the totals say nothing about any one phone. We use them only to see how much each feature is used. Our host keeps backups of the server for about 30 days, so a deleted report can remain in a backup that long.

A report that cannot be sent — when the phone is offline, say — waits on the phone and goes with the next one, up to twelve weeks' worth.

You can change your answer at any time with the usage counts switch in the app's Settings. Turning it off stops the counting at once and deletes the counts and unsent reports on your phone. Reports already sent carry nothing that ties them to you, so we cannot pick out yours; within 30 days each is added into the totals and deleted, as above.

We receive usage counts only because you agreed to share them — consent, under Article 6(1)(a) of the GDPR — and you can withdraw it at any time with the same switch.

The Windows app counts nothing and sends no usage counts.

What the apps send, and to whom

The apps talk only to these, and only to do what you asked:

• Your Sonos speakers, on your home network, to find and control them.
• Sonos, to read the details of the music services your speakers offer.
• The music services you pin, only while you browse or search one, to list and find music and show its pictures. Each request carries a random identifier made for this install, and signing in to a service is done with that service, which receives the sign-in you give it.
• Image servers named by your speakers' listings, for cover art. They receive only the address of the picture.
• SoundCloud (soundcloud.com), only for the cover art of a SoundCloud song your speaker cannot show itself. It receives only that song's number.
• Sentry, from the iPhone app: only the crash reports you agreed to send, as described above.
• Sonopley's own server, from the iPhone app: only the weekly usage counts you agreed to share, as described above.

Music plays from your speakers, through the accounts your Sonos household already has. Sonopley never sees a payment detail or a Sonos password.

Nothing else leaves your phone or computer.

What the apps keep, and where

Apart from the crash reports and usage counts you agree to send, everything stays on your own phone or computer, or in your own iCloud where said below, and is copied to no other server — ours or anyone else's:

• Sign-ins to music services, in Windows Credential Locker on Windows and in the Keychain on iPhone.
• Your speakers' addresses, your settings, moments, cue points and Sonopley favourites, in the app's own files on the device.
• A history of what you start playing — what, when and in which rooms, and where you last left off — in the app's own files on the device and, on an iPhone with iCloud on, in your own iCloud, so a new or reinstalled iPhone finds it; for a page of your listening the app does not show yet. Nothing in it is ever sent to us. Removing the app removes the device's copy; the iCloud copy is deleted in the iPhone's Settings, under your iCloud storage.
• A run log of when the app started and how it stopped, with the error if it crashed, for the app's own diagnostics.
• A crash not yet sent, on iPhone while crash reports are off, until you answer the question at the next start.
• This week's usage counts and any report not yet sent, on iPhone while usage counts are on.
• Your answers to the crash report and usage count questions, on the phone and, with iCloud on, in your own iCloud, so a new iPhone does not ask again. They are never sent to us.
• The random identifier sent to music services, made once for this install. It identifies nothing else about you or your device.

This website

These are plain pages: no cookies, no analytics, and nothing loaded from anyone else — even the fonts are our own copies. The one script is on the front page at sonopley.com, which reads the languages your browser prefers to open the site in yours; it stores nothing and sends nothing.

The server our host runs keeps standard access and error logs: the address a request came from, the time, the page asked for, the page that linked to it and the browser or app that asked. They are kept for three weeks and are not backed up, and we do not use them to follow anyone.

A community, and anything else online

A Sonopley community is planned. Before it opens, this page will have a section of its own saying what it collects and why, and joining it will be your choice.

The same goes for anything else Sonopley might one day offer online: it will be something you choose to turn on, described here before it ships.

Your rights

You can ask us to show, correct or delete what we hold about you by writing to info@sonopley.com. Apart from crash reports and usage counts we hold nothing, and because neither carries a name, account or device identifier, we usually cannot tell which is yours — for a crash report, tell us roughly when the crash happened and we will do what we can.

You also have the right to complain to the data protection authority where you live.

About Sonos

Sonopley is not endorsed by or associated with Sonos, Inc. Sonos is a trademark of Sonos, Inc.