אבטחה
כך אנחנו מגינים על התמונות שלך, על הלקוחות שלך ועל העסק שלך.
מסמך זה זמין באנגלית. הנוסח האנגלי הוא הנוסח המחייב.
Infrastructure
The website is served by Vercel's globally distributed edge network, with automatic DDoS mitigation and TLS 1.3 encryption in transit. Cloudflare serves the public thumbnail domain (media.zawiya.studio) and runs the bot check on our sign-in, registration and gallery security forms. All data at rest is encrypted using AES-256. Apart from our own image-analysis server in the EU (Finland), we do not run our own servers — our database is managed PostgreSQL on Supabase and your photos are stored on Cloudflare R2, both SOC 2 Type II certified providers.
Photo storage
Your photos are stored on Cloudflare R2. Full-resolution originals are access-controlled: every view and download is brokered by our server, which checks the requester's session or gallery access, enforces the gallery's download-quality limits, and issues short-lived links. Lower-resolution thumbnails and previews are served from a CDN for speed and may be reachable by their URL while a gallery is live. Right-click saving of originals is disabled at the application layer for galleries where the photographer has enabled protection.
Access control
Gallery access is controlled at three levels:
- Public — anyone with the link can view (no account required).
- Password-protected — clients must enter a photographer-set password. Passwords are hashed with bcrypt before storage; we never store them in plaintext.
- Private — only the photographer can view; share via a signed direct link.
Download tokens are single-use, short-lived, and scoped to a specific image and quality level. They cannot be reused or shared to bypass access restrictions.
Authentication
Photographer accounts authenticate via Supabase Auth, which provides email/password login with email verification, secure session management using HTTP-only cookies, and automatic token rotation. We enforce a minimum password strength of 8 characters including at least one uppercase letter and one number.
All admin actions require a separate privilege check server-side regardless of the session cookie. Client-side role checks are purely cosmetic.
Billing & activation
Subscription plans are paid through an Israeli payment provider, on its own secure payment page, which opens on the provider's website. Zawiya has no card form of its own: we never receive, store or transmit card numbers or bank details, so there is no card data on our platform to steal. When you choose a plan, we record only a payment request — the plan, the billing period, the amount, a payment reference and the date. The payment provider sends us nothing automatically; our team activates the plan after confirming the payment in the provider's records. Gallery upgrades and featured listings are arranged directly with our team over WhatsApp or email.
Rate limiting & abuse prevention
All public gallery routes apply per-IP rate limiting for password attempts, download requests, and API calls. Repeated failed password attempts trigger a temporary lockout. Download traffic is throttled per session to prevent bulk scraping. Sign-in, sign-up, password reset, event registration and the gallery security check ask for Cloudflare's bot check (Turnstile) before they go through.
Data privacy
We collect only what is necessary to operate the platform. Client IP addresses are stored as one-way SHA-256 hashes — the original IP is never retained. The optimized previews and the watermarked or resized downloads we generate are re-encoded and carry no embedded camera metadata. Original-quality downloads, by design, deliver the photographer's untouched master file — including its original EXIF, which may contain GPS coordinates or device details — so the recipient gets an unaltered original. We do not sell, rent, or share your data or your clients' data with third parties. See our Privacy Policy for full details.
Vulnerability disclosure
If you discover a security vulnerability in Zawiya, please report it responsibly by emailing info@zawiya.studio. We aim to acknowledge all reports within 48 hours and to release a fix within 14 days for critical issues. Please do not publicly disclose the vulnerability until we have had a chance to address it.
Contact
For security concerns or questions, contact us at info@zawiya.studio.