SESSION Pilates
Session Pilates · Build 1.47.0
Static checks identify review items, not a guarantee of safety.
Overview
1 finding categories to review
SESSION Pilates (com.marianatek.sessionpilates) scored grade A, 99 out of 100, in a static scan of version 1.47.0 on 2026-10-03. It has no high or critical findings, and 1 lower-severity finding category across 2 occurrences. 1 tracking SDK is present in the package, which describes what ships, not what runs or what it sends. This is static analysis of a single build: it does not observe the app running and does not establish that any data is exposed.
Start with these findings
lowData Safety label omits Calendar2 occurrences
Interpretation & review guidance
The app's Google Play Data Safety label omits a data category it can actually access — a permission it requests, or an advertising/device identifier it references. Under-declaring collection is a Play policy issue and a COPPA/privacy concern. This is a static signal: a requested permission is capability, not proof of collection — confirm against runtime behavior.
How often Data Safety labels disagree with the package →
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Build & components
1 components recorded. Certificate parsing does not validate APK signature integrity.
Inspect build evidence →Findings
1 categories · 2 occurrences. Severity totals describe categories. Expand a finding for interpretation and review guidance.
lowData Safety label omits Calendar2 occurrences
Interpretation & review guidance
The app's Google Play Data Safety label omits a data category it can actually access — a permission it requests, or an advertising/device identifier it references. Under-declaring collection is a Play policy issue and a COPPA/privacy concern. This is a static signal: a requested permission is capability, not proof of collection — confirm against runtime behavior.
How often Data Safety labels disagree with the package →
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
data-safety:Calendar- Recorded match
Pattern recorded; identifying value redacted.
2 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
No categories match these filters. Clear the search or choose all severities.
Privacy signals
Capabilities and bundled software do not prove that data was collected or transmitted.
Precise location Approx. location Storage
Requested permission inventory (15)
Data collection & flow (privacy signal, not part of the grade)
- Persistent-identifier APIs referenced in code (Android ID, Device ID / IMEI) with 1 analytics/ad SDK(s) present — the mechanism used for cross-app profiling.
- Calendar, Photos & files data requested with third-party analytics/ad SDKs present.
This maps what the app can access (permissions it requests, identifier APIs its code references) to the third parties bundled in it. It reflects capability and SDK presence — not proof that a specific value was transmitted.
Data Safety: declared vs observed (Play label vs our analysis)
We compare the developer's Google Play Data Safety declaration with what the binary can actually do (permissions it requests, identifier APIs and third-party SDKs it ships). A mismatch is a capability signal to confirm — a requested permission is not proof of collection.
Trackers & SDKs (1 detected · privacy signal, not part of the grade)
Build & components
Scanned build 1.47.0. Store metadata may describe a newer release.
16d97ab7eb569bac2f71beb536d258cfad94b0343ac3606eece7a17a7db6f193Signing certificate (who signed this build — factual, not part of the grade)
be:a8:48:5a:a2:ef:a7:15:fb:e9:ad:de:3b:1c:3e:d6:6a:a5:7e:23:25:72:11:06:d7:7e:77:98:2e:59:c7:26The certificate fingerprint identifies the parsed signing certificate. Knowing this public fingerprint does not establish ownership or validate the APK signature.
Component inventory
1 components. Advisory matching covers a curated set; no match is not proof that a component is vulnerability-free.
| Component | Version | Advisory matches |
|---|---|---|
com.squareup.okhttp3:okhttp | 4.12.0 | None recorded |
About this app · store information
About this app
SESSION is a 50-minute full mind and body experience.
Screenshots
Scan history
Each row is an observed scan. Gaps between scans do not establish how long a finding existed.
| Scanned (UTC) | Build | Score | Grade |
|---|---|---|---|
| 2026-10-03 20:53 UTC | 1.47.0 | 99 | A |
Export & share
Exports describe the recorded assessment. Signed evidence proves origin and integrity, not completeness or safety.
Coverage & gap matrix · Verify signed evidence
Embed the latest grade
Embed this grade
The badge reads the latest recorded grade each time it is loaded, and links back to the full report so a reader can see the build it covers and what the scan could not see.
Grades can move when a new version is scanned or when a detector is corrected. If you would rather publish a grade that cannot change under you, link a signed Proof Capsule instead.
API users can request authenticated, scan-specific exports at /v1/scans/040cf395-ecd0-4ac7-aa69-f4e9a14f39c2/findings.sarif (also coverage.json and proof.json).
Request a correction or removal · How to interpret a scan · Browse apps