Antennapod: Privacy Policy

Created on 15 Dec 2018  路  16Comments  路  Source: AntennaPod/AntennaPod

While the app doesn't collect any data, maybe we should have a privacy policy, nonetheless, stating that we don't but with reference to external parties' policies (e.g. GitHub, Flattr, iTunes).

Are there any (F)OSS that have a similar (non-existant) data model that we could take as inspiration?

All 16 comments

Below some links to short privacy policies from open-source apps I found:

http://loophabits.org/privacy
https://k9mail.github.io/privacy-policy.html
https://termux.com/privacy-policy.html
https://github.com/jackpal/Android-Terminal-Emulator/wiki/Privacy-Policy
https://community.kde.org/KDEConnect/PrivacyPolicy

They mostly just state that they do not collect data. Some explain the used permissions. I like the paragraph about the auto backup feature in the first link. We should probably also note what information the web servers can collect when we pull the feed. Additionally, we have to mention gpodder, flattr, fyyd and iTunes.

On a related note, I've wondering how much services such as iTunes and podtrac.com can track me via the use of AntennaPod.

Does AntennaPod behave as if visiting them via browser incognito session, i.e., they can track IP address and short-lived cookies? Or does it heave more like regular browser sessions, i.e., long-lived cookies can be used to track individual usage?

We are not integrating with podtrac.
For iTunes, we are using their API. iTunes basically one sees the IP and client (AntennaPod), but we do not send any cookies or other tracking information.

While AntennaPod code base doesn't deal with podtrac, many podcasts expose their podcast files via podtrac. When AntennaPod download such media files, there might still be question on how much podtrac (or similar services) can track.

I assume AntennaPod does not send any long-lived cookies, even if they ask it with HTTP Set-Cookie, but I just want to be sure.

I wrote a first draft. What do you think about that suggestion?

All data provided to AntennaPod is only stored locally in your device. AntennaPod does not upload your data anywhere. The developers of AntennaPod do not have access to any of your data. Your data is not shared with any 3rd parties. AntennaPod does not include any advertisement libraries or any 3rd party tracking (analytics) code, such as Google Analytics.

Note: If you have activated "backup & reset" in your phone settings (Settings / Backup & Reset / Back up my data), you should be aware that Android itself will periodically save a copy of your phone's data in Google's servers. This backup contains private information, including your WiFi passwords, messages and call history. It may also include data from AntennaPod and from other apps you use. The developers of AntennaPod do not have access to this data.

The app requests the following privacy-relevant Android permissions. The permissions are only requested if you perform an action that requires them. Average app users do not need to grant permissions.

  • Read from/write to Storage (Photos/Media/Files)
    The storage area is used to open files that are not downloaded directly from within the app. It can also be used to import app settings or opml files.
  • View WiFi connections
    AntennaPod allows to restrict automatic updates to specific WiFi networks.

The web servers that provide the podcast feeds might collect additional data, such as remote IP, access time and what is being accessed. Please refer to their privacy policy for details. You can view the url by opening a podcast and pressing the info icon. AntennaPod does not allow remote servers to set cookies. The servers can detect the fact that you are using AntennaPod and which version (HTTP User-Agent is something like AntennaPod/1.7.1). If multiple podcasts are hosted on the same server, the server can find out the list of podcasts that you subscribed to and that are hosted on that server. This might happen if publishers use feedburner, podtrac or similar services to provide their feed.

When using the search feature of iTunes, fyyd or gpodder.net, those services can find out the feed which you are searching for. After subscribing, the feed is usually served from the creator's server. When synchronizing with gpodder.net, the service can use all your subscriptions and playback events according to their privacy policy.

I would add "AntennaPod is a GDPR-compliant app" or something like it.
If you don't store any data I can suppose that your app is GDPR-compliant.

I would add "AntennaPod is a GDPR-compliant app" or something like it.

To be honest, I don't see a reason why we need to explicitly state that. Every app that is distributed in Europe needs to be gdpr compliant, even without stating so. Otherwise, there might be legal consequences. Big companies use "we are gdpr compliant" to reassure users that all the things they are doing is legitimate. To me, this statement sounds like "well, we collect tons of data but don't worry - we do it lawfully".

That's all just my subjective feeling. Does the statement actually make most users feel more comfortable? To me, it feels kind of the opposite

That's all just my subjective feeling. Does the statement actually make most users feel more comfortable? To me, it feels kind of the opposite

Yes, you may be right and a privacy-oriented user will read all the privacy policy knowing that it must be GDPR-Compliant in Europe. But IMHO the 90% of normal users doesn't even fully know what the GDPR states. If you start the Privacy Policy with "AntennaPod doesn't collect any of your data" this would probably be the only sentence a normal user will read before clicking "Accept" (if you are going to show the Privacy Policy at the first start of the app). :-)
Anyway, I agree with you that my suggestion may be unnecessary, but I don't think it is "dangerous"

I wrote an updated draft. I added a notice about the GDPR and I restructured the text a bit. I am happy to hear your suggestions (including grammar and spelling mistakes).


Which kind of data do we process?

All data provided to AntennaPod is only stored locally in your device. AntennaPod does not upload your data anywhere. The developers of AntennaPod do not have access to any of your data. Your data is not shared with any 3rd parties. AntennaPod does not include any advertisement libraries or any 3rd party tracking (analytics) code, such as Google Analytics. AntennaPod is therefore fully compliant with the GDPR.

When synchronizing with gpodder.net, the service can use all your subscriptions and playback events. They handle your data according to their Privacy Policy. Synchronization is disabled by default.

Permissions

The app requests the following privacy-relevant Android permissions:

  • Read from/write to Storage (Photos/Media/Files)
    The storage permission is used to open files that are not downloaded directly from within the app. It can also be used to import app settings or opml files. The permission is only requested if you perform an action that requires reading from storage.
  • View WiFi connections
    AntennaPod allows to restrict automatic updates to specific WiFi networks.

Side channels

If you have activated "backup & reset" in your phone settings (Settings -> Backup & Reset -> Back up my data), you should be aware that Android itself will periodically save a copy of your phone's data in Google's servers. This backup contains private information, including your WiFi passwords, messages and call history. It may also include data from AntennaPod and from other apps you use. The developers of AntennaPod do not have access to this data.

The web servers that provide the podcast feeds might collect additional data, such as remote IP, access time and what is being accessed. This includes the fact which episodes you are downloading or streaming. Please refer to their privacy policy for details. You can view the url of a podcast by opening the podcast and pressing the info icon. AntennaPod does not allow remote servers to set cookies. The servers can detect the fact that you are using AntennaPod and which version of AntennaPod you are using (HTTP User-Agent). If multiple podcasts are hosted on the same server, the server can detect the list of podcasts that you subscribed to and that are hosted on that server. This might happen if publishers use feedburner, podtrac or similar services to distribute their feeds.

When using the search feature of iTunes, fyyd or gpodder.net, those services can store your query. After subscribing, the feed is usually served from the creator's server.

@ByteHamster I'm not the right person to correct someone else English. I can only suggest to check :)

1) I find more readable the bullet lists, so I would prefer to read the first part as a list:
e.g.

All data provided to AntennaPod:
- are only stored locally in your device 
- are not upload anywhere
- the developers of AntennaPod do not have access to them
- are not shared with any 3rd parties 
- are not used for any advertisement or 3rd party tracking (analytics) code, such as Google Analytics.

AntennaPod is therefore fully compliant with the GDPR.

When synchronizing with gpodder.net, the service can use all your subscriptions and playback events. They handle your data according to their Privacy Policy. Synchronization is disabled by default.

2) "Data" is singular or plural? e.g. "All data provided to AntennaPod is only stored" or "All data provided to AntennaPod are only stored"? It seems an open questions. IMHO the plural form is more readable but maybe only because in my mother tongue it's used as plural.

3) "AntennaPod allows to restrict automatic updates TO specific WiFi networks." or "AntennaPod allows to restrict automatic updates ON specific WiFi networks."?

These are only suggestions/questions. I think the new Privacy Policy is good and complete also as you have published it.

Addition:

The developers may update this policy in the future. It is advisable to check the policy periodically for any changes. Changes to this Privacy Policy are effective when they are made on this document.

If you have questions, open an an issue on GitHub.

Last Updated: This Privacy Policy was last updated on xx-xx-xxxx.

"Data" is singular or plural?

Let's just replace with information instead. Google also mostly uses information in its policy.

Many thanks! Reviewing it now.

Actually, two things:

  • Should we add a comment on Google Play (refer to Google's privacy policy, and tell what developers can see in the Play console)?
  • I guess a link should be added in Google Play? F-droid doesn't seem to have a structured field.

Should we add a comment on Google Play (refer to Google's privacy policy, and tell what developers can see in the Play console)?

I think we should rather keep the policy shorter to not frighten users. The developer statistics should be in the privacy policy of Google Play.

I guess a link should be added in Google Play? F-droid doesn't seem to have a structured field.

I added it to the Play Store. Might take a few hours to be updated.

Was this page helpful?
0 / 5 - 0 ratings