Privacy Policy

Policy webpage: https://mayaqar-b2245.web.app/privacy (update the website when this revision is approved)

This Policy sets out the mechanisms for collecting, using and protecting personal data through the app or website of the (MYAQAR) platform, both owned by (SULTAN FOR SOFTWARE DESIGN), in accordance with the Personal Data Privacy Protection Law in force in the State of Qatar and its related regulations and decisions.

The Customer retains exclusive ownership of all data and information they enter into the app or platform, including data relating to properties, contracts, tenants and owners. The app or website only processes that data on the Customer's behalf and in accordance with the Customer's direct instructions and directions.

MYAQAR is a mobile workspace for property owners and their authorized teams. It connects properties, units, tenants, leases, rent records, maintenance, expenses, documents and reports. This policy explains the information used by those features and the choices currently available.

1. Information used by the app

Account and profile information: your account identifier, email address, display name, sign-in credentials handled by Firebase Authentication, and optional phone number, profile photo, business name and mailing address. The app also stores portfolio size, country, language, currency, date format and app preferences.

Property and tenancy records: property addresses and details, unit information, occupancy, tenant names and contact information, lease dates, rent, deposits and notes. Tenant records can also include a national ID and emergency contact details if an authorized user enters them.

Financial records: rent due and paid, payment dates and methods, references, notes, correction history, and expenses and receipts. These are property management records. Recording a rent payment does not itself transfer money or collect a tenant’s payment card details.

Files and operational records: profile and property images, lease contracts, documents, receipts, maintenance photos and notes, task assignments, calendar events, activity records, and file metadata such as names, types and sizes.

Team and notification information: team identities, invitations, roles and workspace membership, notification preferences and history, and device push tokens used to deliver notifications.

Subscription information, when enabled: the account identifier, purchase and store transaction information, product, entitlement, plan, billing period, subscription status and expiration date. Availability depends on the app’s store and billing configuration.

Technical information: the connected service providers can process information such as IP addresses, device or app identifiers, operating system information and service request logs as part of authentication, delivery, security and service operation.

Most property and tenant information is supplied by an owner or authorized team member. Owners should enter only information they are authorized to use, explain their handling of tenant information, and take care with national IDs and uploaded documents.

2. How information is used

Information is used to authenticate accounts; synchronize workspace records; connect properties, units, tenants and leases; calculate rent balances and occupancy; record expenses; organize maintenance and calendar events; store and retrieve files; generate reports; enforce team access; and deliver notifications according to preferences. When subscriptions are enabled, purchase information is used to verify and update subscription access.

The current app does not include advertising SDKs or a dedicated marketing analytics integration. It does not request device location or access to your address book. Property addresses are entered as part of property records.

3. Access, sharing and connected services

Your workspace: property records are organized by owner workspace. Owners and invited team members can access records according to their role. Invitation access codes should be shared only with the intended recipient.

Google Firebase: the app uses Firebase Authentication for email/password, Google and Apple sign-in; Cloud Firestore for records; Cloud Storage for uploaded files; Cloud Functions for server operations; and Firebase Cloud Messaging for push notifications. Google may process data on infrastructure outside your country. See Firebase privacy and security information and Google’s Privacy Policy.

Apple and Google sign-in: choosing a provider connects authentication to that provider. Information returned to the app can include an account identifier, email address and profile information. Apple may supply a relay email address. Provider privacy policies also apply.

RevenueCat and app stores, when billing is enabled: RevenueCat uses your Firebase account identifier as the app user identifier, handles subscription purchase information and supplies entitlement status. The backend verifies the current subscriber state with RevenueCat and saves a subscription summary. Apple or Google handles the store purchase and payment details. See RevenueCat’s Privacy Policy, Apple’s Privacy Policy and Google’s Privacy Policy.

Actions you choose: calls, SMS and email actions open your device’s dialer or message composer with the tenant contact details and any prepared message. Your chosen communication provider handles the action; opening a composer does not confirm delivery. Exporting or sharing a PDF, CSV or document sends information to the location or recipient you select. Recipients and other apps handle the exported copy under their own practices.

Uploaded files use download links. Anyone to whom you forward a working download link or exported file may be able to access that copy. Check recipients before sharing tenant or financial information.

No sale of personal information: Myaqar does not sell or rent personal information to any third party. Information is shared only with the service providers described in this policy to the extent needed to operate the service, with recipients you choose, or with government or regulatory authorities where disclosure is required by law.

4. Storage and security

App records, including property, lease, tenant, rent, expense and team information, are stored in Google Cloud Firestore. Uploaded files and images are stored in Cloud Storage for Firebase. The app uses Firebase Authentication to manage sign-in, and access is governed by authentication and workspace rules. Firebase uses secure HTTPS connections for data in transit; no storage or transfer is completely risk-free.

Where information is stored: Firestore database location: [CONFIRM ACTUAL FIRESTORE REGION OR MULTI-REGION AND COUNTRY]. Cloud Storage bucket location(s): [CONFIRM ACTUAL STORAGE REGION(S) OR MULTI-REGION AND COUNTRY]. Cloud Functions location(s): [CONFIRM ACTUAL DEPLOYMENT REGION(S)]. These are project-specific Google Cloud settings, not automatically Qatar-based. MYAQAR must verify these values in its Firebase/Google Cloud project before this notice is published. Firebase Authentication processes authentication data in United States data centers.

International processing: Firebase Cloud Messaging, hosting and other Google services may use global infrastructure. Apple, Google and RevenueCat process authentication or subscription information under their respective privacy notices and infrastructure arrangements. Therefore customer data may be stored, transferred to or accessed from countries outside Qatar, including the United States. MYAQAR will use the safeguards required by applicable law and can provide the confirmed primary application-storage regions on request at info@myaqar.com.

The mobile app and its service SDKs may keep local sessions, preferences and cached records on your device. Reports or files you export or download can also remain on the device or with the recipient. Protect your device, account credentials and invitation codes.

5. Retention and archived records

Retention of live workspace data: Account information, workspace settings, property and tenant records, leases, financial records, uploaded files and team memberships are retained while the owner’s workspace remains active and the information is needed to provide the service. Archived properties or tenants remain stored while the workspace is active; archiving is not deletion. Following a verified workspace-closure or account-deletion request, eligible live workspace records and uploaded files will be erased within 30 calendar days after verification, unless retention is legally required or the records belong to another workspace owner.

Other retention periods: MYAQAR-controlled notification and activity histories are retained for up to 12 months from creation; MYAQAR-controlled security and technical logs for up to 90 days; and support correspondence, account-verification records and deletion-request confirmations for up to 24 months after the case is closed. Data is then deleted or anonymized unless a legal obligation, dispute or security investigation justifies a longer period.

Subscriptions and statutory records: MYAQAR may retain the minimum invoices, payment references, subscription transactions and tax/accounting records necessary to comply with applicable Qatar requirements for up to 10 years after the relevant financial year (or longer where a specific legal hold applies). This exception does not automatically cover customers’ entire property, tenant or lease databases. Apple, Google, RevenueCat and other service providers may retain information they control under their own retention rules.

Deletion timetable: MYAQAR will respond to a received personal-data deletion request within 30 calendar days. Once the requester’s identity and authority have been verified, eligible live account and workspace data will be deleted within 30 calendar days. Data held in backups, snapshots or provider soft-deletion/recovery copies may remain for up to 90 additional days after deletion from live systems, subject to technical constraints and legally required preservation. MYAQAR must configure and test its deletion and backup-retention processes to meet these commitments before publishing this revision.

Limits of deletion: Removing a team member’s account does not erase property records belonging to the workspace owner. Previously exported, downloaded or forwarded files cannot be withdrawn from recipients’ devices or services. Signing out, uninstalling MYAQAR or cancelling a subscription does not itself delete cloud data. Subscription cancellation must be completed separately with Apple or Google.

6. Your choices and requests

Review and edit account and property information using the app’s available screens, subject to your workspace permissions.

Manage notification preferences in the app and push permissions in your device settings.

Select the files you choose to upload through the system file picker. Calls and messages require an action by you.

Use the report export options for PDF and CSV copies of supported financial reports. These exports are not a complete copy of all account data.

Cancel or manage subscriptions through the Apple App Store or Google Play account used to make the purchase; the Terms of Use explains the steps and refund process for each store. Subscription cancellation and account/data deletion are separate actions.

Depending on the law that applies to you, you may have rights to access, correct, delete or obtain a copy of personal information, restrict or object to processing, withdraw consent where processing relies on it, or complain to a data protection authority.

Request account or workspace deletion through More or My Account in the app, through the public account-deletion request page, or by emailing info@myaqar.com from the registered account email. MYAQAR may verify the requester’s identity and authority. We respond within 30 calendar days after receiving the request; after verification, eligible live data is erased within 30 calendar days, with remaining backup/recovery copies handled as set out in Section 5. If an exemption applies or additional time is necessary, support will explain the reason. Opening the request page does not by itself delete data.

If you are a tenant whose information was entered by a landlord or property manager, contact that person or organization about the tenancy records they manage. Their own obligations and privacy notice apply to their collection and use of your information.

7. This landing website

This website is hosted on Firebase Hosting. Loading its pages sends normal web requests, including your IP address and browser request information, to the hosting service. All images and fonts used on these pages are hosted with the website.

This website has no account registration, contact form, advertising pixels or analytics scripts. Its page code does not set cookies or use browser local storage. Your language choice is stored in the page URL so it can follow links within this website. Contact links open your email app; any email you send is handled by your email provider and Myaqar’s support mailbox. Clicking an external privacy or store link takes you to a service with its own privacy practices. The app screenshots use sample data and do not show actual customer records.

8. Changes to this policy

This page will be updated when the app’s features, providers or confirmed operational practices change. The date at the top identifies the most recent update. Store availability and billing activation may vary by release.

9. Operator and privacy contact

Operator: Myaqar. For support, questions about this policy, or requests about your personal information, contact info@myaqar.com. Please describe your request and provide the account email needed to identify the relevant records. Avoid sending passwords, payment card details or unnecessary tenant documents. If your question concerns records managed by a landlord or property manager, contact that person or organization as well. Visit Contact Us.

SULTAN FOR SOFTWARE DESIGN (One-Person Limited Liability Company)

Commercial Registration No.: 248696

Tax Identification Number (TIN): 5009039017