Skip to main content

What should I do when I receive "4.1 Your app must comply with the following privacy-related requirements"

The most of us are developer; we are technical persons, which do their stuff better than anyone. But besides this, when we are developing a Windows Client application for Windows 8 (Metro App) we don’t need to forget about the legal stuff and similar things. We don’t like them, but we need to resolve them also.
If you have an application that use internet connection, access a backend server, share data with another 3th party like Facebook, Twitter or another system than we should have a simple privacy policy in our application.
From now one this is a MUST, even if in the past was optional. If you try to submit your application without privacy policy that you will receive a big reject with the following message:
"Your app doesn't meet requirement 4.1" (Privacy)
What I recommend, is to add a privacy policy even if you don’t thing that you store, share the user data. Why? Is safest for you and you don’t need to submit the application again if you will have this problem.
What should the privacy policy should contain? Depends, internet is full with a lot of privacy policy text. You can inspire from them, but I recommend to double check the text with someone from legal department or a lawyer.
After you have the privacy policy content, all that you have to do is to publish on your website. If your application don’t have a website, that you can create a blog and publish there the privacy policy. The good part with this is that: you can make anytime an update if the privacy policy without the need to create an update for your application.
When you create your application you will need to add a link in the setting page that will open a browser with the privacy policy. This can be done in different ways. If you have a base class for your pages, that you can override the “OnNavigateTo” method. The code should look something like this:
protected override void OnNavigatedTo(NavigationEventArgs e)
{

    SettingsPane.GetForCurrentView().CommandsRequested += (SettingsPane sender, SettingsPaneCommandsRequestedEventArgs args) =>  
      {
        IList<SettingsCommand> commands = requestEventArgs.Request.ApplicationCommands;
        if (commands.FirstOrDefault(x => x.Id.ToString().Equals("privacyPolicyCommand",StringComparison.CurrentCultureIgnoreCase)) != null)
        {
          return;
        }

        SettingsCommand privacyPref = new SettingsCommand("privacyPolicyCommand", "Privacy Policy", (uiCommand) =>
          {
            Windows.System.Launcher.LaunchUriAsync("http://mywebsite.com/privacypolicy.html");
          });
        requestEventArgs.Request.ApplicationCommands.Add(privacyPref);
      });

}
Cool, now we have in our Settings page of each page of our application a link to our privacy policy.
Next step is to add the link to our privacy policy page in the moment when we want to want to submit our applicant. There is a small input with “Privacy policy” label at the end of the page.
I hope that you will not have any kind of problems with 4.1 requirements. Good luck.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...