Zaynat

Zaynat legal drafts — operator review pack

Published for reading as a draft; not effective commercial terms. Incomplete details and proposed policies remain subject to completion and approval.

Prepared 9 September 2026. These are original working drafts for review, not a legal opinion or a certification that the business is licensed/compliant. A UAE-qualified lawyer should review the operator identity, permitted licence activities, applicable data regime, Arabic version and final commercial provisions before commercial launch. No public website terms or acceptance flows were replaced by this drafting task.

Documents

  1. CUSTOMER-TERMS.md — Luca Kozak/customer platform relationship, independent Partners, bookings and direct payments.
  2. PARTNER-TERMS.md — Luca Kozak/Partner SaaS agreement, approval and publication, subscription rules and a draft processing schedule.
  3. PRIVACY-NOTICE.md — current demo data behaviour, planned production distinctions and privacy information to complete.
  4. LEGAL-NOTICE.md — operator identity, contacts, disclosures and third-party attribution.

Facts provided

Luca Kozak is the proposed contracting operator, with a UAE freelancer licence registered in Abu Dhabi. Customers pay Partners directly. The supplied email is luca@zaynap.app; confirmation was requested because the product domain is zaynat.app. Issuing authority, licence number, full registered address and final effective date remain missing. Do not invent a company name, licence authority, VAT status or licence scope.

Proposed business rules — approval needed before use

  • Default customer cancellation/rescheduling: free at least 24 hours before a confirmed appointment, unless a different lawful policy was clearly disclosed and accepted before booking.
  • Pending requests: withdrawal without a cancellation charge.
  • No default no-show penalty: a Partner must disclose and obtain agreement to any lawful charge in advance.
  • Partner-cancelled service: refund the unprovided service if the customer declines an alternative; initiate an established refund within 14 days or sooner if law requires.
  • Subscription cancellation: stop renewal before its date; access runs through the paid period. No ordinary convenience refund of a started billing period, with explicit mandatory-rights, billing-error and material-failure exceptions.
  • Free no-card trials do not silently create paid commitments.
  • Keep accepted founding-Partner price protection. Annual discounts and Premium pricing are governed by the accepted order; the unresolved Premium annual-price discussion is not decided in these documents.
  • No booking commission under the offered subscription plans. Optional paid services require separate agreement.
  • Premium tools do not imply unlimited bespoke development; additional work requires a scope.
  • Proposed 30-day post-termination export-request window; implement before promising it.
  • Proposed B2B liability cap tied to 12 months' fees, with listed exceptions. This is a negotiated risk allocation requiring legal review, not a UAE statutory rule or customer-liability cap.
  • UAE law and competent Abu Dhabi courts, subject to mandatory jurisdiction and rights.

Publication dependencies

Complete licence identity and contact fields, confirm the freelancer licence authorises the actual activities, select effective dates, and obtain the operator's approval of the proposed rules. Finalise payment/subscription renewal mechanics and tax disclosure; these are not implemented by writing terms.

Prepare the legally required Arabic customer information and contract text with qualified review. Do not treat English-only drafts as a complete UAE launch package.

Define actual production data flows: Supabase project region, hosting, subprocessors, messaging and billing providers, transfer arrangements, retention/deletion schedule and incident contacts. Complete the Partner processing annex and security measures. Decide and implement any required analytics/third-party consent mechanism. Booking consent and callback requests are not general promotional consent; validate UAE promotional-data and calling requirements before marketing.

Update registration and booking UI to link the correct version, prominently show Partner identity, total price and cancellation terms, capture affirmative acceptance where needed, and retain evidence of the version accepted. Privacy acknowledgement is not interchangeable with optional marketing consent. Preserve prior versions; do not generate a changing "last updated" date on every render.

Replace the existing placeholder legal page only after the specific publication version is ready. Keep the current prototype notice accurate: local accounts, inboxes and analytics are not a production security boundary. Ensure account deletion explains its actual scope across bookings, enquiry records, analytics and Partner copies.

Official sources checked

These sources informed the review points; the specific commercial periods and liability allocation above are drafting proposals, not statements of statutory requirements.

Abu Dhabi registration alone does not establish whether a specific free-zone/data-protection regime applies or establish the licence's permitted activities. Review against the actual issuing authority and licence. The applicable law and publication requirements should be rechecked when the production launch date and business details are final.