Platform Protection

Security Practices & Architecture

Platform:Share360 | Operator:HiqMobi | Standards: Modern Transport Encryption & Token Authentication

1. Security Architecture Overview

At HiqMobi, safeguarding user data, financial details, and transaction integrity is fundamental to platform operations. We build defensive measures across client applications, API layers, databases, and third-party payment integration gateways.

2. Technical Safeguards

End-to-End Transport Encryption: All communications between the mobile application, web client, and API servers are encrypted using modern Transport Layer Security (TLS 1.3 / HTTPS). Plaintext HTTP traffic is rejected.
OAuth 2.0 & Token Authentication: We do not store plaintext passwords for creators. User authentication is managed via Google OAuth Identity Tokens and signed JWT sessions with strict expiration timelines.
Financial Information Hygiene: Payout identifiers (such as UPI IDs and bank IFSC details) are stored with parameterized database access patterns to prevent SQL injection and unauthorized tampering.
Operational Audit & Access Controls: All critical platform operations are protected by multi-layered, role-based authorization controls with comprehensive audit logging tracking all campaign verifications and payout disbursements.
Anti-Tampering Controls: The mobile app incorporates runtime package signature verification to detect unauthorized APK modifications and malicious app clones.

3. User Security Recommendations

Users are encouraged to maintain active security hygiene:

Always download Share360 exclusively from the official Google Play Store. Never install APK files from unknown websites or modified third-party stores.
Protect your Google account using 2-Factor Authentication (2FA).
Do not share your referral code or device access credentials with unknown third parties claiming to offer automated earning bots.

4. Reporting Security Concerns

If you suspect a vulnerability, unauthorized access, or suspicious platform activity, please refer to our Responsible Disclosure program or report directly to our security lead at Legal@hiq.mobi.

2. Technical Safeguards

End-to-End Transport Encryption: All communications between the mobile application, web client, and API servers are encrypted using modern Transport Layer Security (TLS 1.3 / HTTPS). Plaintext HTTP traffic is rejected.

OAuth 2.0 & Token Authentication: We do not store plaintext passwords for creators. User authentication is managed via Google OAuth Identity Tokens and signed JWT sessions with strict expiration timelines.

Financial Information Hygiene: Payout identifiers (such as UPI IDs and bank IFSC details) are stored with parameterized database access patterns to prevent SQL injection and unauthorized tampering.

Operational Audit & Access Controls: All critical platform operations are protected by multi-layered, role-based authorization controls with comprehensive audit logging tracking all campaign verifications and payout disbursements.

Anti-Tampering Controls: The mobile app incorporates runtime package signature verification to detect unauthorized APK modifications and malicious app clones.

3. User Security Recommendations

Users are encouraged to maintain active security hygiene:

Always download Share360 exclusively from the official Google Play Store. Never install APK files from unknown websites or modified third-party stores.

Protect your Google account using 2-Factor Authentication (2FA).

Do not share your referral code or device access credentials with unknown third parties claiming to offer automated earning bots.