Session replay technology gives developers valuable insight into drop-offs, errors and more activity in the app. However, many apps have not revealed that this information is being collected and for what purpose. As a result, apps over the store were given a sudden 24 hour notice to remove session replication SDK, receive explicit permission from the user to allow recording or be removed from the store.
A ] Techcrunch
report showed that popular apps used increased replay technology to record
user screens while the apps were being used, without first getting permission.
The session replay SDK came from third party customer experience analytics firms,
and mainly records or screenshots the app it is open to send back to
There are two problems with this: first the data was not
Always properly masked, potentially revealing sensitive user information.
Second, users were not informed that they were being registered ̵
No permission notice and very few privacy rules themselves
mentioned screen recording. Those who did included what the policy still had
to update to get explicit user permission or to be removed.
Shortly after this information came out, Apple celebrated
store to find out which apps used increased replay technology. Someone like that
The discovery was notified that they had 24 hours to tell the users they were
registered or remove SDK. Those who failed to do so within the time frame
would be removed from the store.
Apple's alert told developers:
"Your app uses analytics software to collect and send user or device data to a third party without the user's consent. Apps must request explicit user's consent and provide a clear visual indication when registering, logging or otherwise register user activity. "
The intention of increased replay technology is to see how
Users interact with an app, especially to identify errors or other errors.
This can quickly become risky if the apps require users to type sensitive
information, such as credit card number or password information. If the app
Really masking the data, the risk is minimized, but it's not always that
In one case, the Air Canada app failed to mask
information right. This can cause the data to become vulnerable to being caught
and stolen, especially in the wake of a recent air
Canada data breach . This damages important user data, for example
credit card number or passport information.
Some of the apps returned the data to third-party servers,
while others sent them back to their own data servers. Either way, no
guarantees that the data is properly protected or hidden.
available and contains information about data sharing, such as analytics tools.
Specifically, in the section
In addition, there are additional user policies
Permissions that an app needs to collect data:
"Apps that collect user or user data must secure the user's consent to the collection. Paid functionality must not depend on or require a user to access this data. Apps must also provide Customer Easily Accessible and Understandable Way to Consent. Make sure your target strings clearly and completely describe the use of your data. "
Apple released a statement that said:
" Protecting users' privacy is critical to Apple's ecosystem Our App Store Review Guidelines require apps to explicitly require the user's consent and provide a clear visual indication when registering, logging, or otherwise registering user activity We have notified developers who violate these strict privacy policies and policies and take immediate action if is necessary. "
In cases where apps are targeted for removal, not many
There is a clear breach of the App Store policy and a reason for removal.
or facial removal, since users did not give them access.
ASO & What
Developers can do
It should without saying that it is removed from the App
The store is disastrous for an apps optimization. Not only prevents the removal of one
The app from being found or downloaded at all remains the effect even after it is
If an app is removed, it loses all keyword indexing
and rankings. Putting it back on the store later will require re-indexing for
targeted keywords – the app must begin the process of building its ranking up
Everything again, which takes time. The setback would be huge.
Apps that were in danger of removal have already been informed
and should have updated now. If they don't, they will have been
The best way to avoid
removal for a similar situation must take place at the users. If you
will use the session replay SDKs to record their usage, make it clear
is just to help solve any issues that may arise and improve the user
Experience, users still have the right to know if their behavior is
This is more than just a matter of following guidelines –
It is about openness, security and trust in the user. Users lose
believe in an app when they learn that it has been collecting information about
those without permission – this is reflected in the uninstallations and negatives
rankings / ratings, which can both adversely affect the app's rankings
If your app used an SDK again, you should have received
A notice with 24-hour notice Friday night and updated accordingly
now. It's important to monitor Apple's messages in case there are other drastic ones
change like this; anyone who decided to wait until after the weekend
will have got their app taken down then. If your app doesn't use an increased replay
SDK, this serves as an important lesson to follow the guidelines carefully and
Ensure user privacy.
Want more information on optimizing the App Store?
Contact Gummicube and
We help you get your strategy started.