Privacy Policy

Cloud Hosting and Database Infrastructure

The application, its API and its primary database are hosted with a cloud infrastructure provider in the US East (Virginia, USA) region, on SOC 2 Type II / ISO 27001 certified infrastructure with point-in-time recovery backups.

Data involved: all application data — engagements, documents, fatwas, user accounts and encrypted OAuth tokens — together with IP addresses and standard HTTP request metadata. Data is encrypted at rest, and sensitive fields are additionally encrypted at the application layer using AES-256-GCM. Transfers to the United States are made under the UK International Data Transfer Addendum (IDTA) and Standard Contractual Clauses.

AI-Assisted Document Processing

Some features generate Shariah advisory suggestions or analyse uploaded documents using a large language model. This processing is performed by a third-party AI provider under enterprise API terms on a paid tier.

Data involved: advisory titles and descriptions, relevant knowledge-base context, and the content of documents submitted for analysis.

• The platform is model-agnostic by design. The architecture supports alternative providers, including customer-specified or self-hosted models, where a client's requirements call for it.
• Customer content submitted for analysis is not used to train or improve the provider's models.
• FiqhEngine does not train machine-learning models on customer content, and never uses one customer's content for the benefit of another.
• Content may be transiently cached by the provider for a short period to support processing, and is not retained beyond that.
• The current provider is named in the sub-processor register provided to customers on request.

Transactional Email Delivery

Account, security, and workflow notification emails are delivered on our behalf by a transactional email provider under a Data Processing Addendum.

Data involved: recipient email address, sender name, message subject and body, and basic delivery metadata. Where a customer provides their own mail server, transactional emails may instead be routed through that customer-configured SMTP service.

Calendar and Contact Integrations (Optional, User-Connected)

FiqhEngine offers optional calendar integrations with Google Calendar and Microsoft Outlook. These integrations are off by default; you enable them per user account from the Calendar widget by clicking "Connect Google" or "Connect Microsoft" and granting consent on the respective provider's OAuth screen.

• Google Calendar API (scope calendar.events) — read your upcoming events to render the in-app schedule view, and write engagement and task due dates as all-day calendar events so deadlines surface in your existing workflow.
• Google People API (scope contacts.readonly) — autocomplete attendee email addresses when you schedule a meeting from within FiqhEngine. Contacts are fetched on demand and not copied to FiqhEngine's database.
• Google OpenID (scope userinfo.email) — display the connected Google account address in the calendar widget so you can see which account is connected.
• Microsoft Graph API (scopes Calendars.ReadWrite, Contacts.Read, offline_access, openid, profile, email) — equivalent functionality against Microsoft 365 / Outlook calendars and contacts.

What we store. Only the OAuth access and refresh tokens (encrypted at rest with AES-256-GCM), the connected account's email address, and a per-event identifier so we can later update or remove events we previously created on your behalf. Event bodies, attendee lists, and contact lists are fetched on demand and not persisted.

Disconnect at any time. Use the Calendar widget's Settings → Disconnect option to revoke FiqhEngine's access and delete the stored tokens immediately. You may also revoke the grant directly with the provider at myaccount.google.com/permissions or account.microsoft.com/privacy/app-access.

Google API Limited Use compliance. FiqhEngine's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, we (a) only use Google user data to provide and improve the calendar and contact features described above; (b) do not transfer Google user data to third parties except as necessary to provide those features, comply with applicable law, or as part of a merger, acquisition, or sale of assets with your prior notice; (c) do not use Google user data for serving advertisements; (d) do not allow humans to read Google user data unless we have your explicit affirmative consent, it is necessary for security purposes (such as investigating abuse), to comply with applicable law, or for internal operations where the data has been aggregated and anonymised; and (e) do not use Google user data to develop, improve, or train generalised or non-personalised AI or machine-learning models.

Meeting and Conferencing Integrations (Optional)

Where your organisation enables meeting scheduling, join links are minted through the conferencing provider configured for your deployment. Data involved: meeting subject, start time, duration, and organiser or host identity. Recording behaviour defers entirely to your own conferencing account configuration.

Team Messaging Integrations (Optional)

Where your organisation connects a team messaging workspace, we deliver workflow notifications into it. Data involved: notification content and the destination channel and workspace identifiers you configure. The integration is off unless you enable it.

Electronic Signature Services (Optional)

Where e-signature is enabled, documents are sent for signature through an electronic signature provider, which returns the executed document and its audit trail. Data involved: the document to be signed, signer name and email address, and signature and audit metadata. If e-signature is not configured, the platform falls back to manual signed-PDF upload and no signature provider is used.

Error Monitoring and Diagnostics

We use an error monitoring service to capture unhandled exceptions in the server and in the browser, so faults are detected and fixed. Data involved: exception messages, stack traces and request context such as the URL and HTTP method. Personally identifying data is not intentionally transmitted: event data is scrubbed before sending, user identity is removed, and request and performance tracing is disabled.

Website Analytics (Marketing Site Only, Consent-Gated)

Aggregate visitor analytics run on our public marketing website only, and load solely after you grant Analytics-cookie consent. They are not used inside the authenticated application. Data involved: pseudonymous usage events and device or browser metadata, with IP anonymisation enabled. No application database content is sent. See the Cookie Policy above for the named provider and cookie detail.

Source Code Hosting and Development Tooling

Our source code repository and continuous integration pipeline are hosted with a code hosting provider. Data involved: source code and commit history. No customer data, production secrets, or personal data is stored in the repository.

What We DON'T Use

• ❌ Advertising networks or data brokers
• ❌ Social media tracking pixels
• ❌ Profiling or automated decision-making services

International Data Transfers

Some services are located in the USA. We protect your data through:

• Standard Contractual Clauses (SCCs) approved by EU Commission and the UK International Data Transfer Addendum (IDTA)
• Encryption in transit (TLS 1.2 minimum, TLS 1.3 supported) and at rest (AES-256-GCM)
• Access controls and authentication
• Regular security audits