Effective date: 7 June 2026 · Last updated: 7 June 2026
This Privacy Policy describes how RM Telecom ("we", "us", or "our") collects, uses, and protects information when you use the EvidenceCam Android application and the photo verification service at evidencecam.rmtelecom.com.au (collectively, the "Service").
🔒 Your private signing key is generated entirely on your device inside the Android KeyStore and never leaves your device. We never have access to it.
📷 Photos uploaded for verification are processed in memory and are not stored on our servers. Only a SHA-256 hash of the photo and its verification result are logged.
EvidenceCam does not require you to create an account, provide a name, or supply an email address. The data we collect is the minimum necessary to operate the cryptographic verification system.
| Data | Purpose | Where stored |
|---|---|---|
| Device UUID Randomly generated on first launch |
Identifies your device for signature verification — not linked to your identity | On-device (SharedPreferences) and our server |
| RSA-2048 public key | Stored on our server so photos signed by your device can be verified | Our server (the private key stays on your device only) |
| Device make & model Android version & SDK level |
Device registration record — helps identify which device signed a photo | Our server |
| App version | Compatibility tracking during registration | Our server |
| Locale & timezone | Collected at registration; not used for profiling | Our server |
| Firebase Cloud Messaging (FCM) token | May be used to deliver device-level notifications (e.g. registration confirmation) | Our server & Google Firebase |
| GPS / location | Optionally embedded in the EXIF data of photos you capture, as evidence context. Only collected when location permission is granted and you are actively capturing a photo. We do not track your location continuously. | Inside the photo file (on-device and in photo EXIF) |
| Watermark / custom text | User-entered text displayed as a photo watermark and stored in photo EXIF | Inside the photo file (on-device) |
When you (or any third party) upload a photo to evidencecam.rmtelecom.com.au for verification:
| Data | Purpose | Retained? |
|---|---|---|
| The uploaded photo | Processed in memory to extract EXIF metadata and verify the cryptographic signature | No — discarded immediately after processing |
| SHA-256 hash of the photo | Provides a tamper-evident fingerprint logged with each verification result | Yes — in verification log |
| Device UUID (from EXIF) | Used to look up the registered public key for signature checking | Yes — in verification log |
| Filename | Logged alongside the verification result for reference | Yes — in verification log |
| GPS coordinates (from photo EXIF) | Logged with the verification result if present in the photo | Yes — in verification log |
| Photo capture timestamp (from EXIF) | Logged with the verification result | Yes — in verification log |
Verification history shown in your browser is stored in your browser's
localStorage only — it never leaves your device and is not sent to our servers.
We do not use your information for advertising, behavioural profiling, or sale to third parties.
This site uses cookies and similar browser technologies, including
localStorage, to improve functionality and remember your preferences.
| Technology | Type | Purpose | Duration |
|---|---|---|---|
CSRF token (csrftoken) |
Strictly necessary | Protects form submissions from cross-site request forgery. Required for the site to function securely. | 1 year |
Session cookie (sessionid) |
Strictly necessary | Maintains server-side session state, used for future authenticated corporate account features. | Session |
Consent preference (ec_cookie_consent) |
Functional — localStorage |
Remembers whether you accepted or rejected non-essential storage so the banner does not reappear on every visit. | Persistent until cleared |
Verification history (ec_verify_history) |
Functional — localStorage |
Stores a local list of your recent verification results for review. Never sent to our servers. Only retained if you accept cookies; cleared automatically on rejection. | Persistent until cleared or rejected |
We do not use advertising cookies, cross-site tracking, or third-party analytics scripts on this website. The only third-party service is Google Firebase, which operates within the Android app (not this website) — see Google’s Privacy Policy.
You can change your cookie preferences at any time via the Cookie Settings
link in the site footer, or clear cookies and localStorage directly through
your browser settings.
We do not sell, rent, or trade your personal information. We may share data only in these circumstances:
| Permission | Reason |
|---|---|
| Camera | Required to capture photos with the app |
| Fine Location | Optionally embeds GPS coordinates in photo EXIF as evidence context. You may deny this permission; the app will still function without GPS data. |
| Read / Write Media (Photos) | Saves captured photos to your device's gallery or a folder of your choice |
| Internet | Required to register your device with our server on first launch |
We implement technical safeguards appropriate to the sensitivity of the data, including:
No system is completely secure. We cannot guarantee absolute security, but we take reasonable steps to protect your information.
EvidenceCam is not directed at children under the age of 13 (or 16 where applicable under local law). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us and we will delete it.
Depending on your location, you may have rights regarding your personal data, including the right to access, correct, or delete it. Australian users are protected under the Privacy Act 1988 (Cth) and the Australian Privacy Principles. Users in the European Economic Area have rights under the GDPR.
To exercise any of these rights — including requesting deletion of your device registration — please contact us using the details in Section 10.
We may update this Privacy Policy from time to time. Material changes will be reflected by an updated "Last updated" date at the top of this page. We encourage you to review this page periodically. Continued use of the Service after changes are posted constitutes acceptance of the updated policy.
If you have questions or requests regarding this Privacy Policy, please contact us:
← Back to Photo Verification