KHATTAH Privacy Policy

1 Who is responsible

The responsible operator is [FULL LEGAL NAME AND BUSINESS ADDRESS]. Privacy officer or responsible contact: [NAME OR ROLE], [PRIVACY EMAIL], [POSTAL ADDRESS]. Effective date: [INSERT AFTER APPROVAL].

This draft starts from an Alberta private sector context. Alberta PIPA and, where applicable, federal PIPEDA or other local privacy laws may govern particular activities. The applicable laws must be confirmed after operating locations and data flows are known.

2 Information we handle

Account information includes your name, registered email, Member ID, password hash, verification and account status, preferences, and any phone or profile details you provide. Participation records include requester and owner IDs, Package ID, link letter, request and payment confirmation times, link status, contribution amount and currency, reward status and associated transaction references.

We may also handle support correspondence, messages you ask us to send, consent records and security records such as access events, IP addresses, timestamps and administrative actions. The operator must confirm which device or browser details, analytics and other logs are actually collected [VERIFY BEFORE PUBLICATION].

Payment providers may process payment and payout details under their own notices. KHATTAH should retain only the information reasonably required for confirmation, reconciliation and support. Do not send full card numbers, security codes or banking passwords through support or invitation emails. Exact provider fields must be documented before live payments [PAYMENT PROVIDERS TO BE CONFIRMED].

3 Why information is used

We use necessary account information to register and authenticate you, communicate about the service and provide account settings. Participation information connects a request to its intended inviter, package and A–E link, checks payment, avoids duplicate credit, records objectives and administers lawful rewards, refunds and disputes.

Security and support records help investigate misuse, control administrator access, resolve complaints and meet applicable legal duties. We must identify any additional purpose before using information for it. Optional marketing, analytics or unrelated purposes must have an appropriate legal basis and a separate choice when required.

4 What other members can see

Request Invitation is available to all members who complete registration, including unpaid members. It displays available yellow links and completed green links. For these links, registered members can see owner Member IDs, Package IDs, A–E letters and availability or paid status. Even without a name, an ID and a paid status can reveal information about a person’s participation.

Each owner’s Activity page displays only their own completed green links, including the paying member’s ID and payment confirmation time. These details are not intended to appear in another owner’s Activity. Authorized administrators may access records needed for their assigned role.

Your email address, password hash, full payment details and private support messages are not intended for the shared invitation listing. The operator must verify that templates, APIs and exports respect these visibility boundaries. Visibility of an invitation is not permission for members to copy, scrape or republish personal information.

5 Emails cookies and choices

When you request an invitation, we use your registered email to send the requested link and its package and membership identifiers. Account security, payment and support communications are sent as needed for the relevant service. Marketing messages must be distinguished from those functions and use the consent and unsubscribe arrangements required by applicable anti spam law.

KHATTAH uses its signed session cookie for sign-in, form protection and session preferences. The khattah_cookie_choice cookie remembers a choice for 180 days. The optional khattah_language cookie is set for 180 days only when allowed and is removed when declined. Cookie Settings allows changes at any time. These controls add no advertising or analytics cookies. Third party resources and providers still require review before launch.

You can ask to change optional preferences or withdraw consent where applicable. We will explain if withdrawing a necessary permission prevents a service you request. Withdrawal does not automatically remove records that must lawfully be retained.

6 Service providers and transfers

We disclose information to providers only as reasonably needed for services such as hosting, email delivery, payment processing and support, under suitable arrangements. Provider names, purposes and processing countries are [HOSTING PROVIDER AND COUNTRIES], [EMAIL PROVIDER AND COUNTRIES], [PAYMENT PROVIDERS AND COUNTRIES] and [OTHER PROVIDERS]. These entries must be completed.

Information processed outside your jurisdiction may be subject to access under another country’s laws. We must provide the notices and contact information required for those transfers. We may also disclose information where lawfully required, to address substantiated fraud or security matters, or with your authorization. Any business transfer must preserve applicable privacy obligations and appropriate notice.

Selling member information or using it for unrelated advertising is not part of this proposed policy. The operator must confirm that commitment and check all vendor arrangements before publication.

7 Security and administrator access

Passwords are stored as hashes rather than displayed as readable passwords. Appropriate safeguards must cover access permissions, authentication, session handling, secure transmission, backups and administrator audit records. Only authorized staff should access information for an identified purpose.

Administrator View as member access must be limited, logged and read only. It must not expose passwords or allow payment or account changes. Local testing shortcuts must not carry into a live system. No online service can promise absolute security; safeguards must be reviewed and maintained.

If an incident involves personal information, we will assess it, take reasonable containment steps and make any notifications required by applicable law. This draft does not replace the operator’s incident response procedure.

8 Retention access correction and complaints

Keep information only for the purposes and period reasonably necessary, taking applicable laws and disputes into account. Before publication, adopt an actual schedule for account records, payment and reward records, security logs, support messages, consent evidence and backup expiry [RETENTION PERIODS REQUIRED]. Do not describe all transaction history as permanently retained personal information.

You may ask the privacy contact about your information, request access or correction, and raise a complaint. Depending on applicable law and circumstances, you may also request deletion, account closure or withdrawal of consent. These requests are subject to lawful exceptions; we must explain any refusal or retention need. We may ask for proportionate proof of identity through a secure method.

We will respond within the time required by applicable law and explain any permitted extension or applicable fee before proceeding. You may complain to the Office of the Information and Privacy Commissioner of Alberta or the Office of the Privacy Commissioner of Canada where their jurisdiction applies.

9 Children changes and publication checks

The proposed service is for adults aged 18 or older. If we learn that a person under the approved age has supplied information, we will assess account access and handle the information under applicable law. The operator must confirm eligibility and implement the corresponding registration controls.

Material privacy changes will be communicated with an updated date and any notice or fresh consent required by law. Before publishing this policy, confirm the operator, actual fields and cookies, member visibility, providers and countries, retention periods, privacy contact and rights process. A policy must describe the real service rather than substitute for missing controls.

Reviewer references Alberta privacy law overview https://oipc.ab.ca/overview-privacy-laws/ and federal consent and retention guidance https://www.priv.gc.ca/en/privacy-topics/privacy-laws-in-canada/the-personal-information-protection-and-electronic-documents-act-pipeda/p_principle/