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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…