SECURITY
How we protect your information.
Updated 10 October 2026
We use access controls and limited-lived sessions to protect information. Here is what that means for you.
Account and request access
Connections use HTTPS. Passwords are salted and hashed, rather than stored as readable text. Verification, password-reset, invitation and request-access links expire and work once. Login and email-request limits help reduce repeated guessing and unwanted messages.
Owner access is restricted to the designated verified owner. Support-request access is tied to a verified email link and a private session.
Private by permission
Server checks restrict brand records and collaboration messages/files to authorized accounts. Published brand and offer images may be viewable through their links; a private collaboration attachment has separate access checks. Do not place confidential information in material intended for publication.
The owner can manage accounts, offers, creator reviews and requests. Management decisions are recorded. This is access-controlled storage, not end-to-end encrypted messaging.
Files and services
Uploads are limited by file type and size. These checks do not amount to a guarantee that every file is safe, and automated malware scanning is not currently connected. Account information is stored in the hosted database; uploaded files use separate object storage. Service credentials are kept outside the public website code.
Our current stage
Haggles is available as a public website beta in Lebanon. We have tested key permissions and failure cases, but do not claim independent security certification or that a service can be risk-free. Hosting backup and recovery specifications are still awaiting confirmation from our hosting provider.
Help keep your account safe
Use a unique password for your email account and enable its multi-factor protection. Never share sign-in links, passwords or verification codes. Open links only when you requested them.
Report concerns through Contact & requests or care@collabhunts.com. Describe the affected feature without sending sensitive records belonging to others.