Developer Verification

  Can you clarify the "new" in "Starting in February 2024, new developers who want to have their apps visible in the European Economic Union"? Does it mean that developers who already have an account don't need to do it?

What does it mean if someone who is supposed to fill that form doesn't fill it? Will he notice it when he uploads new apps? Also when he uploads new versions of existing apps? I mean will it be visible in the developer dashboard that the 20 some countries in Europe are not available? Or the only think we'll see is a slow-down in the downloads?

Also this form is one of the worst forms I've ever seen! www.garmin.com/.../

The whole sentence makes little to no sense. For example:

"This won’t affect the features and services you can access in Connect IQ Developer Registration Form or your eligibility for Connect IQ Developer Registration Form developer programs."

OK, so what does it affect?

Or: "I certify to only offer products or services that comply with the applicable rules of Union law." Union law? Is this some copy&pasted form from the time of the American Civil War??? Or you mean the European Union Law?

Look, I know that people usually don't read the legal stuff, but this form is the total opposite of it. This tells us nothing what it is for, just a few examples it is not for...

  • I'd also like to know what email address will be displayed; will you be showing my Connect IQ login email address or the email address that I use on the app upload details (labelled as "The email address will be displayed publicly as a contact for your app."). I don't want my login email exposed and if an email address needs to be displayed then I want it to either be the app contact email or another email I specify.

    Further to the privacy of a developer, will you be exposing the postal code? Because while 64106 might be generic enough in that it covers all of Kansas City, my postal code identifies my location down to a single side of a street block. For example, "T2P 1C9" tells me that you live on the south side of 8th Ave SW between 2nd and 3rd Street in downtown Calgary, Alberta (Canada). There might be 12 houses in a city block which means you basically know where I live.

    Finally, can you please post a link to the law(s) that we are to be complying with? Is this related to Apple's fight with the EU?

  • "New" developers will be any developer that has submitted their first app (either public or beta) after February 17, 2024. Existing developers will be grandfathered and will not need to complete the registration process immediately (but will need to at some point in the future).

    When a new developer submits their first app after the 17th, everything will work essentially as it always has, except region limits will be set on the app to exclude the EEA. This is visible in the submission form. Once a new developer completes registration, they will be able to add the EAA region countries to the region limits in their app listing if they choose.

    The email submitted in the form will not be shared externally, and neither will your Connect account email address—the contact information displayed on the app listing is the support email for the app (the "Contact Developer" email), which is set per-app by you.

    Postal code is not exposed in the contact info. We're currently only displaying City, State/Province, and Country (or similar) to logged in users.

    This is all in place for compliance with the EU Digital Services Act: https://commission.europa.eu/strategy-and-policy/priorities-2019-2024/europe-fit-digital-age/digital-services-act_en.

  • Postal code is not exposed in the contact info. We're currently only displaying City, State/Province, and Country (or similar) to logged in users.

    Is the screenshot in the official announcement not an accurate example of what will be shown? This is a genuine question, not a “gotcha” attempt.

    In some cases, a postal code could correspond to a single large apartment building.

    https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/developer-verification-begins-in-february

  • That screen cap is inaccurate. I think it was from an early design when we were still trying to determine what developer information we were required to display. I've updated the blog post to be more specific.

  • 7 hours ago you wrote: "Postal code is not exposed in the contact info", but in the announcement you updated 30 minutes ago: "City/State/Zip"

  • I wonder who'll read or even click that link to the law.

    Am I guessing this right: Garmin doesn't really care, as long as nobody contacts Garmin that some app has some issues with GDPR. When some legal entity from the EU will contact Garmin then this new form will enable Garmin a. not to take responsibility (won't pay a fine) b. pass responsibility to the developer, c. quickly remove the app from the store.

    And the more interesting and important question that Garmin legal will need to give us their opinion on: when my Datafield or app records a fit file via CIQ apis and it is synced to the Garmin servers at the end of the activity, then what's the legal status? I mean who's the controller of the collected data? The app developer or Garmin?

    Or let's ask a broader question: if I only use the apis in the SDK (Properties, Storage, Fit contribution, Complications, System.println, etc) and don't use the internet (make no web requests from my code) then am I OK? Or are there still things to consider?

  • Just a guess, but one thing here that was in the original blog post was that a developer could be requested for something like a scan of their DL to verify they are a real person and not just a random, made up email address, so if someone contacts Garmin, Garmin has a real person to attach the app to incase there is an issue in the EU.  Garmin will have more info about the dev that's not shown to the public.

  • Regarding use of phone number should we expect to be contacted on it? Or is that more for providing options in the event something happens? Like will the EEA be ringing me up or?

  • Exactly! It would be great if the form we fill in would include information about how that data will be used. (Not intended as a pun. but as this whole thing was triggered by privacy laws in the EU it would be great if Garmin would provide us this information, exactly as it is required by the law and as now Garmin expects us to abide that same law)

    Which piece of information will be public to the world

    Which will only be used by Garmin

    Which will be used by Garmin and shared by 3rd parties on demand (i.e in the event some 3rd party contacted Garmin about our app)

  • The blog post about this was updated to show what's exposed and now says:

    For individual developers:

    • Support Email Address
    • City/State/Country