Skip to content
Open
Show file tree
Hide file tree
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
Binary file added Evidence/FirebaseConsole.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
38 changes: 38 additions & 0 deletions Evidence/README.MD
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
Datavenorg Developer Transparency & Policy Compliance

This repository serves as the official developer domain for PrecisionTracker and CallManager. It hosts required legal documentation and technical verification files for the Google AdMob and Play Store ecosystems.

🛡️ Ad Operations & Security
To ensure the highest level of traffic quality and inventory security, the following standards are implemented:

Authorized Sellers Only: We have implemented the app-ads.txt standard to prevent unauthorized inventory spoofing and ensure ad requests only originate from verified sources.

Test Environment Integrity: All development builds are strictly configured to use Google Test Ad IDs. Physical test devices are hard-coded within the AdMob console to prevent unintentional "Invalid Activity" during debugging.

Data Sovereignty: Our applications prioritize local-first data architecture. All sensitive user data is stored locally on the owner's device to ensure absolute privacy and data sovereignty.

📊 Technical Evidence (Audit: May 2026)
In response to recent automated traffic flags, we have compiled the following transparent data points to assist in manual account reviews:

1. User Volume Verification
Source: Google Play Console

Current Status: Stable organic audience of 16–24 active users.

Insight: High-volume ad requests are inconsistent with our verified small-scale user base, indicating external bot interference or "click-injection" targeting our Ad Unit IDs from outside the app.

2. Analytics Discrepancy
Source: Firebase Analytics (Linked to AdMob)

Finding: Internal logs show zero ad_impression or ad_click events during the flagged period. This confirms that the activity detected by AdMob servers did not execute within the application code itself.

3. Debugging Logs
Source: Android System Logs (logcat)

Finding: Detailed logs (see Running_test_log2.txt in this repo) document a high-intensity debugging session on May 11, 2026. Rapid process cycles and background BackupAgent activity during testing explain the unintentional request spikes from authorized developer environments.

Developer Contact: datavenorg@gmail.com

Privacy Policy: [https://jmarindi.github.io/precision-tracker-privacy/]

Privacy Policy: [https://jmarindi.github.io/CallManagerPrivacy/ ]
2,654 changes: 2,654 additions & 0 deletions Evidence/Running_test_log2.txt

Large diffs are not rendered by default.

Binary file added Evidence/SentinelAlert.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added Evidence/precissionTracker.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading