Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand description of why we may not have found any tracking #17

Merged
merged 1 commit into from
Dec 6, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/i18n/en.json
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@
"heading": "Analysis of “{{appName}}” found nothing",
"explanation": "The analysis of the app has finished. We did <strong>not</strong> detect any tracking data transmissions without consent.",
"what-heading": "What does that mean?",
"what-explanation": "<p>This could mean that the app genuinely doesn’t perform any tracking. However, it is also possible that we missed something.</p><p>Mind you, our analysis process doesn’t enter anything into the apps or accept any prompts. If tracking companies are only contacted after certain inputs, we are unable to detect that.</p><p>On top of that, we have made the decision to rather miss something than produce false positives, which is why we are only detecting tracking endpoints that we have researched and classified as such. This means that we <em>will</em> miss some tracking data transmissions but it enables us to say for sure that tracking actually occurred if we do detect something, which is important for the complaints.</p>"
"what-explanation": "<p>This could mean that the app genuinely doesn’t perform any tracking. However, it is also possible that we missed something.</p><p>Mind you, our analysis process doesn’t enter anything into the apps or accept any prompts. If tracking companies are only contacted after certain inputs, we are unable to detect that.</p><p>It could also be because the app detected our analysis environment and refused to run in it. This is especially common for banking apps for example.</p><p>On top of that, we have made the decision to rather miss something than produce false positives, which is why we are only detecting tracking endpoints that we have researched and classified as such. This means that we <em>will</em> miss some tracking data transmissions but it enables us to say for sure that tracking actually occurred if we do detect something, which is important for the complaints.</p>"
},
"proceeding-landing-awaitingControllerNotice": {
"heading": "Analysis of “{{appName}}” detected tracking",
Expand Down