Home › Blog › Mobile apps

Mobile App Compliance: Québec Checklist for 2027

By2Friends · · 8 min read

Mobile App Compliance: Québec Checklist for 2027

Before your next iOS or Android update, check age ratings, location data, Law 25 and French content so your Québec app stays publishable in 2027.

Before your next iOS or Android update, check four points: age ratings in App Store Connect, data declared in Google Play, Law 25 and French. Mobile app compliance is not only a legal file anymore. It is also a release-management issue.

If your app supports clients, field teams, members, tenants, patients, students or shoppers in Québec, a blocked update can quickly become a business problem. The good news: most issues can be found in one short audit before your next release.

Mobile app compliance: what changed for 2027

Two platform changes make this a good time to review your app.

Apple announced in November 2026 that App Store Connect now includes new age-rating content descriptors starting November 16, 2026. When completing the age-rating questionnaire, developers must declare whether an app includes shared real-world location with another person or group, or dating and relationship features. Apple says these declarations are required when submitting an update or changing the age-rating questionnaire, and all apps must complete them by January 12, 2027. Source: Apple Developer, November 2026

Google Play is also tightening app declarations. In its October 29, 2026 policy announcement, Google said developers have at least 30 days to comply with listed policy changes, and that starting in November 2026 they must declare trader status in Play Console under new Console requirements. The same update also introduced future declaration requirements for permissions such as local network access for apps targeting Android 17 or higher. Source: Google Play Console Help, October 2026

For location, Google Play is more specific. Its foreground location guidance says all apps requesting precise location with ACCESS_FINE_LOCATION must complete a Play Console declaration to show why precise location is needed and why the location button or coarse location is not enough. Google says the declaration is available in November 2026 and compliance is mandatory for apps in scope on January 27, 2027. Source: Google Play Console Help, November 2026

For a Québec business, this means the app stores are asking the same question your clients and regulators ask: do you collect only what is necessary, and can you explain it clearly?

Check 1: age rating, location and dating features

Start with the features that can change an app store review.

Make a simple inventory:

Do not answer from memory. Ask the product owner, developer and support person to walk through the app together. Store questionnaires often fail because the answer is technically true for one screen that nobody remembered.

For Apple, the key is to update App Store Connect declarations before January 12, 2027 if your app is affected. For Android, the key is to know whether location is approximate, precise, continuous, background, or only used once. If precise location is not essential, reducing it can simplify the Google Play declaration and improve user trust.

A practical rule: if the feature works with a postal code, city, store selection, QR code, appointment address or one-time location button, do not ask for always-on precise GPS by habit.

Check 2: Google Play Data safety must match the real app

Google’s Data safety section is not a marketing text. Google says all developers with an app published on Google Play must complete the Data safety form, including apps in closed, open or production testing tracks. It also says developers are responsible for complete and accurate declarations, and must consider third-party code such as SDKs and libraries. Source: Google Play Console Help, Data safety

This is where many business apps drift over time. A mobile app may begin as a simple client portal, then add analytics, push notifications, crash reporting, payment, chat, AI search, maps or a CRM integration. Each addition can change what data is collected or shared.

Before the next release, compare three things:

  1. Permissions in the code: camera, contacts, location, microphone, files, photos, Bluetooth, notifications.
  2. SDKs and services: analytics, ads, payment, chat, maps, authentication, AI tools, support widgets, crash logs.
  3. Declarations and policies: Google Data safety, App Store privacy details, privacy policy, onboarding notices and consent screens.

If one column changed and the others did not, you have a compliance gap.

For example, a delivery app might use location only while the driver is active. A client portal might collect uploaded invoices. A fitness or health app might collect sensitive personal information. An AI assistant might transmit support questions to a third-party model provider. Each case needs a clear data map.

Check 3: Law 25 still applies inside the app

This section is general information, not legal advice. For legal interpretation, speak with a qualified lawyer or privacy professional.

Québec’s Commission d’accès à l’information explains that publishing a privacy policy is mandatory when a business collects personal information using technology. It gives websites and mobile applications as examples, and says people must have access to the policy when personal information is collected through a site or mobile app. Source: Commission d’accès à l’information du Québec

The CAI also says a privacy policy should explain what information is collected, the purposes, third parties that may receive it, protective measures, cookies if used, rights and remedies, and policy changes. It must be written in clear and simple terms. Source: Commission d’accès à l’information du Québec

For mobile apps, translate that into product work:

The CAI also says technologies that identify, locate or profile a person must not have those functions activated by default; the person must be able to activate them voluntarily. For an app, that affects onboarding, location tracking, personalization, recommendations and AI-assisted scoring.

Check 4: French is part of the user experience

In Québec, French is not an afterthought to add after the build.

The OQLF says every business active in Québec must be able to offer service in French, whether to consumers or to other businesses. It also says service in French should be available through all communication channels used by the business, in comparable conditions to other languages. Source: OQLF, language of service

For a mobile app, that means you should review the whole user journey:

The OQLF also states that customers of businesses active in Québec have the right to be served and informed in French before, during and after a transaction. Source: OQLF, commerce and business language

This is more than translation. A proper French version avoids mixed button labels, untranslated error states, English-only support macros and store screenshots that promise a French app while the logged-in experience is mostly English.

A 10-day pre-release plan

You do not need a three-month committee to reduce risk. You need a structured pass before the next app update.

Day 1: feature inventory
List every sensitive feature: location, account, payment, documents, chat, AI, camera, contacts, health, children, user-generated content and notifications.

Day 2: store declaration review
Open App Store Connect and Play Console. Export or screenshot the current declarations. Mark every answer that depends on old assumptions.

Day 3: permission and SDK review
Ask the developer for the current mobile permissions and third-party SDK list. Include analytics, crash reporting, authentication, payments, maps and AI.

Day 4: privacy policy gap review
Compare the data map with the privacy policy. If the app changed but the policy did not, update the policy before release.

Day 5: consent and defaults
Check whether location, profiling, marketing, personalization or AI features are opt-in where required. Remove unnecessary default activation.

Day 6: French QA
Test the app in French from install to support request. Capture every English-only screen, email, notification and error.

Day 7: edge cases
Test with a new user, returning user, admin, employee, client, cancelled account and user with denied permissions.

Day 8: support readiness
Prepare simple answers for users who ask why the app needs location, what data is collected, how to delete an account and who to contact.

Day 9: release notes and evidence
Document what changed. Keep screenshots, declarations and policy versions. This helps if an app review question arrives.

Day 10: submit with someone on call
Do not submit on Friday afternoon if the app is business-critical. Submit when the product owner and developer can answer review questions quickly.

Build and update your app with By2Friends

By2Friends builds mobile apps, client portals, AI features and business tools for Québec companies that need things to work in the real world: privacy, French, store review, integrations and support included.

If your next iOS or Android release touches location, accounts, payments, AI, documents or customer service, we can help audit the app, clean up the user experience and prepare the release. Start here: mobile app development for Québec businesses.

Cover photo: cottonbro studio / Pexels

#mobile app compliance #app store #google play #law 25 #french language #quebec

Keep reading