Legal
Qiraa Corpus Privacy Notice
Last updated: November 7, 2026
This Privacy Notice explains how Qiraa Ltd ("Qiraa", "we", "us" or "our") collects, uses, publishes, verifies, retains and otherwise processes personal information in connection with Qiraa Corpus ("Corpus").
This Notice supplements the main Qiraa Privacy Policy, which explains how your underlying Qiraa account and Qiraa's wider services are handled.
Where processing relates specifically to Corpus contributor profiles, verification, contributions, reviews, discussions, recitations, provenance or other Corpus activity, this Privacy Notice applies.
This Notice supplements the main Qiraa Privacy Policy, which explains how your underlying Qiraa account and Qiraa's wider services are handled.
Where processing relates specifically to Corpus contributor profiles, verification, contributions, reviews, discussions, recitations, provenance or other Corpus activity, this Privacy Notice applies.
1. Summary
Qiraa Corpus is a collaborative, versioned Islamic data resource. You can browse public material without a contributor account or a public profile. Browsing is not published as contributor activity; technical information needed to deliver and secure the service may still be processed.
Contributing or modifying Corpus records requires approved access and a public contributor profile for accountable attribution. Approval alone is not permission to publish your application: before publication, Qiraa must show you the actual public fields and obtain your confirmation. Work email is private by default and requires a separate optional choice to publish.
Optional sensitive profile information requires separate, freely given explicit consent. Revealing your religion is not a condition of contributing. Where required attribution itself reveals special-category information, the safeguards in section 19 apply before it can be processed or published.
Contribution records may be used for AI training under the applicable contribution terms. Personal account and profile identifiers are excluded from training by default. Identity-linked training or output features require a separate, specific opt-in that is off by default. Identifiable audio and other personal data remain subject to data-protection requirements.
Version history does not override privacy rights. Removing a public name or closing an account does not necessarily anonymise the records; information that can still be linked to you remains personal data.
Contributing or modifying Corpus records requires approved access and a public contributor profile for accountable attribution. Approval alone is not permission to publish your application: before publication, Qiraa must show you the actual public fields and obtain your confirmation. Work email is private by default and requires a separate optional choice to publish.
Optional sensitive profile information requires separate, freely given explicit consent. Revealing your religion is not a condition of contributing. Where required attribution itself reveals special-category information, the safeguards in section 19 apply before it can be processed or published.
Contribution records may be used for AI training under the applicable contribution terms. Personal account and profile identifiers are excluded from training by default. Identity-linked training or output features require a separate, specific opt-in that is off by default. Identifiable audio and other personal data remain subject to data-protection requirements.
Version history does not override privacy rights. Removing a public name or closing an account does not necessarily anonymise the records; information that can still be linked to you remains personal data.
2. Relationship with your Qiraa account
A Qiraa account is required before you can request Corpus contributor access.
Your ordinary Qiraa account is handled under the main Qiraa Privacy Policy. This includes matters such as:
The Corpus internally links your Corpus contributor record to your Qiraa account.
Your underlying Qiraa account identifier and unrelated Qiraa account information are not displayed publicly through your Corpus profile.
Closing or deleting your Qiraa account does not necessarily remove material that has already been incorporated into the historical Corpus record. See Account closure, attribution removal and anonymisation below.
Your ordinary Qiraa account is handled under the main Qiraa Privacy Policy. This includes matters such as:
- your Qiraa login credentials;
- general account information;
- authentication and security;
- ordinary Qiraa usage data;
- cookies;
- general service communications;
- payments or donations, where applicable; and
- general Qiraa account deletion.
The Corpus internally links your Corpus contributor record to your Qiraa account.
Your underlying Qiraa account identifier and unrelated Qiraa account information are not displayed publicly through your Corpus profile.
Closing or deleting your Qiraa account does not necessarily remove material that has already been incorporated into the historical Corpus record. See Account closure, attribution removal and anonymisation below.
3. Corpus access process
Browsing and applying
Public browsing does not require a public profile. To contribute or modify records, you need a Qiraa account and approved Corpus access. The application may request your name, account linkage, contact email, organisation, role, reason for applying and proposed area of work. Application information is assessed privately and is not automatically a public profile.
If you choose to submit supporting documents, such as a CV or qualification evidence, submission is optional and limited to 10 files with a combined size of 10 MB. They are used only for verification, not published as Corpus contributions. Qiraa may contact the organisations you list for references or to confirm qualifications. Sections 4, 7 and 14 explain the checks, access and deletion of this evidence.
Public profile confirmation
A public contributor profile is required before contributions or modifications are accepted. The publication process provides a preview identifying each actual public field, distinguishes required attribution from optional information, and obtains your confirmation before publishing. Work email publication and any optional sensitive fields have separate choices; they are not enabled by default or bundled into access approval.
If a required safeguard becomes unavailable or a necessary lawful basis is not in place, the affected publication must not proceed. You can continue browsing without publishing a profile. The current status of these controls is set out in section 29.
Permissions and verification
Identity and age verification through Veriff is required before contributor-platform access. A failed or inconclusive check blocks that access until your identity and eligibility as a person aged 18 or over are verified. You can request human reconsideration as described in section 20; it does not bypass those requirements. Public browsing is unaffected.
Successful verification, access approval or profile publication does not automatically grant editing, review, validation or administrative permissions. Additional qualification, role or affiliation checks may be required. Permissions depend on the relevant role, expertise, workflow and security requirements.
4. Information we collect
Applications and account linkage
Application information includes the details you submit to explain your identity, contact information, organisation, role and proposed work. Corpus connects its contributor record to your Qiraa account. Your underlying account identifier and unrelated account information are not public profile fields.
Profiles and public activity
A public profile contains the basic attribution fields identified in the publication preview, such as your contributor name and Corpus role. Organisation and other details are public only as identified in that preview and subject to the special-category safeguards. Optional additions may include a biography, photograph, qualifications, experience or areas of expertise. Verification-derived badges or tags require a separate, explicit optional publication choice after verification. Work email remains private unless separately selected for publication.
Published contributions, commits, edits, merges, reviews, decisions, disputes, corrections and public discussions may be connected to your contributor history. Optional sensitive information must not be collected or published without the separate lawful conditions described in section 19.
Verification evidence
Veriff handles identity and age verification. Identity documents, photographs or video required for that process are handled by Veriff; Qiraa does not store those original identity-verification materials. For that process, Qiraa retains only a private reference ID linked to your account. The reference is not a public profile field and remains personal data while it can be linked to you.
If you submit supporting documents to Qiraa for separate qualification, employment or affiliation checks, they may include a CV, qualification certificates or other relevant evidence. Submission is optional, with a limit of 10 files and 10 MB in total. These documents are distinct from the identity documents, photographs and videos handled by Veriff. Qiraa handles the supporting documents privately and only for verification, with access limited to authorised personnel who need them for that purpose. Qiraa may contact the organisations you list for references or qualification confirmation.
Limited records of those checks may include verified facts, the outcome, method, date, reviewer reference and necessary audit information. Verified facts may inform internal badges or tags; public display requires your separate, explicit optional choice after verification. Neither submitting evidence nor access approval publishes the documents or those badges or tags. Originals are deleted after verification is complete, subject only to the narrow exceptions and protected backup arrangements in section 14.
Read the Veriff Privacy Notice and Veriff terms alongside this Notice. The verification process explains its method, information required and relevant processing before collection. A biometric method requires its own assessment and legal conditions; ordinary profile or AI choices do not authorise it.
Drafts, messages and recordings
Drafts are private unless you publish them or submit them into a workflow clearly identified as public before submission. Qiraa may process private drafts to provide the drafting function, protect the service or recover data. Public discussion records differ from private support messages and security reports.
Audio contributions are available to authorised contributors. Their records may include the recording, passage, date, recitation type, contributor reference, review information, linguistic or tajweed annotations and technical metadata. The feature explains its purposes and permissions before recording or upload; section 13 applies to identifiable audio.
Technical information
Information needed to operate and protect Corpus may include IP addresses, authentication events, browser or device details, timestamps, session information, errors and security logs. Public browsing does not mean these necessary technical records cannot identify a visitor.
Actor IDs and acceptance evidence
Stable Actor IDs distinguish participants and connect their workflow actions. Account links and attribution records can reconnect them to individuals. Acceptance evidence may contain your account identifier, Actor ID, document version, acceptance time and relevant technical audit information.
Replacing a name with an Actor ID does not anonymise records while usable identifying links remain, including links in acceptance evidence. Public distribution of identifiable Actor IDs or attribution information is a separate disclosure, addressed in section 15.
5. Public contributor information
Public browsing does not create a public contributor profile. A profile is required to contribute or modify records so that the published work can be attributed and the review process assessed.
Before a profile goes public, you must be shown its actual public fields and asked to confirm publication. Confirmation of necessary ordinary attribution is an acknowledgement of publication, not a substitute for a lawful basis or consent to unrelated uses. Optional fields and work email publication have separate choices; sensitive information requires the explicit-consent safeguards in section 19.
Verified qualification, employment or affiliation facts may be recorded internally as badges or tags. Displaying verification-derived badges or tags publicly requires a separate, explicit optional choice after verification; approval of an application does not publish them automatically. Supporting documents remain private verification evidence and are not published with the profile. A badge describes only the check completed and does not imply religious or scholarly authority.
A public profile and its contribution history may be accessible without a Qiraa account. Published material can be indexed, cached, quoted, cited or copied by search engines, researchers, developers and others. Qiraa cannot guarantee that independent copies disappear when its own profile information changes. The duties concerning recipients and public copies in section 11 still apply.
Publication of a profile does not automatically authorise including all its fields in bulk exports, training data or identity-linked AI outputs. Each use must have the applicable purpose, lawful basis and any separate permission required by this Notice.
Before a profile goes public, you must be shown its actual public fields and asked to confirm publication. Confirmation of necessary ordinary attribution is an acknowledgement of publication, not a substitute for a lawful basis or consent to unrelated uses. Optional fields and work email publication have separate choices; sensitive information requires the explicit-consent safeguards in section 19.
Verified qualification, employment or affiliation facts may be recorded internally as badges or tags. Displaying verification-derived badges or tags publicly requires a separate, explicit optional choice after verification; approval of an application does not publish them automatically. Supporting documents remain private verification evidence and are not published with the profile. A badge describes only the check completed and does not imply religious or scholarly authority.
A public profile and its contribution history may be accessible without a Qiraa account. Published material can be indexed, cached, quoted, cited or copied by search engines, researchers, developers and others. Qiraa cannot guarantee that independent copies disappear when its own profile information changes. The duties concerning recipients and public copies in section 11 still apply.
Publication of a profile does not automatically authorise including all its fields in bulk exports, training data or identity-linked AI outputs. Each use must have the applicable purpose, lawful basis and any separate permission required by this Notice.
6. Work email addresses
A professional, institutional or other suitable contact email may be requested to assess an application, verify an affiliation or communicate about Corpus. A named email address is personal data.
Your work email is private by default. Making it public requires a separate, optional opt-in under Article 6(1)(a). Declining publication does not prevent contributions where the other access requirements are met. The publication choice must identify the address and its visibility before you agree.
You can withdraw that publication consent through any available control or by contacting support@qiraa.ai. Withdrawal applies to future publication under that consent and does not invalidate earlier lawful processing. It does not necessarily remove independent copies already obtained by others. Email needed privately for account or access administration is assessed separately under the applicable purpose and lawful basis.
Choosing public display is not permission to include the address in AI training, unrelated mailing lists or bulk releases. Those uses require their own lawful assessment and any applicable separate permission.
Your work email is private by default. Making it public requires a separate, optional opt-in under Article 6(1)(a). Declining publication does not prevent contributions where the other access requirements are met. The publication choice must identify the address and its visibility before you agree.
You can withdraw that publication consent through any available control or by contacting support@qiraa.ai. Withdrawal applies to future publication under that consent and does not invalidate earlier lawful processing. It does not necessarily remove independent copies already obtained by others. Email needed privately for account or access administration is assessed separately under the applicable purpose and lawful basis.
Choosing public display is not permission to include the address in AI training, unrelated mailing lists or bulk releases. Those uses require their own lawful assessment and any applicable separate permission.
7. Identity, qualification and role verification
Veriff carries out identity and age verification for contributor access. Qiraa keeps only a private, account-linked reference ID for that process and does not store the original identity documents, photographs or video. This does not apply to optional supporting documents you submit directly to Qiraa for separate qualification, employment or affiliation checks. Those documents are private, used only for verification by authorised personnel and deleted after verification is complete as described in section 14. Qiraa may contact the organisations you list for references or qualification confirmation.
Before collection, the verification process explains the method, information required, purposes, lawful basis and relevant retention arrangements. Read the Veriff Privacy Notice and Veriff terms alongside this Notice. Using Veriff does not transfer Qiraa's responsibility for the processing it determines or for Corpus access decisions. A method involving facial or voice recognition requires a separate assessment of biometric processing and an applicable Article 9 condition where required. Ordinary profile publication or AI-training permission does not cover that processing.
Verified facts may populate internal badges or tags. Public display requires a separate, explicit optional choice after verification and does not follow automatically from access approval. A public result must distinguish what was checked: identity, a qualification, a role or an affiliation. Verification does not establish the correctness of every contribution or amount to a religious ruling, scholarly certification or endorsement of authority. Permissions remain subject to the relevant expertise and workflow requirements.
Current-role verification needs reassessment when a role changes or its stated validity expires. A historical record of the status held at the time of a contribution must not be presented as current verification. A failed or inconclusive identity check is not, by itself, a finding that your information is false. It prevents contributor-platform access until identity and the minimum age of 18 are verified. You can contact support@qiraa.ai for human reconsideration under section 20; public browsing remains available.
Before collection, the verification process explains the method, information required, purposes, lawful basis and relevant retention arrangements. Read the Veriff Privacy Notice and Veriff terms alongside this Notice. Using Veriff does not transfer Qiraa's responsibility for the processing it determines or for Corpus access decisions. A method involving facial or voice recognition requires a separate assessment of biometric processing and an applicable Article 9 condition where required. Ordinary profile publication or AI-training permission does not cover that processing.
Verified facts may populate internal badges or tags. Public display requires a separate, explicit optional choice after verification and does not follow automatically from access approval. A public result must distinguish what was checked: identity, a qualification, a role or an affiliation. Verification does not establish the correctness of every contribution or amount to a religious ruling, scholarly certification or endorsement of authority. Permissions remain subject to the relevant expertise and workflow requirements.
Current-role verification needs reassessment when a role changes or its stated validity expires. A historical record of the status held at the time of a contribution must not be presented as current verification. A failed or inconclusive identity check is not, by itself, a finding that your information is false. It prevents contributor-platform access until identity and the minimum age of 18 are verified. You can contact support@qiraa.ai for human reconsideration under section 20; public browsing remains available.
8. How we use Corpus information
Corpus processing supports access applications, account administration, verification, appropriate permissions, contribution and review workflows, public attribution, discussions, provenance, dispute handling, service security and reliability, and applicable legal obligations or claims.
Contribution records may also support AI training, evaluation and development under the applicable contribution terms. This does not automatically make personal data in those records available for every training purpose.
Personal account and profile identifiers must be excluded from training by default. This includes account IDs, login or contact emails, profile links and identifying profile fields. Removing those fields is not proof that all remaining content is anonymous: a recording, message or other contribution may itself identify a person, and an Actor ID may remain linkable.
Before training on contribution material that remains personal data, Qiraa must identify the training purpose, its Article 6 lawful basis and any required Article 9 condition, and provide the relevant privacy information. Training on that personal data must not begin while those requirements are unresolved.
Using identifiable account or profile information in training, or deliberately linking an AI output to a contributor's identity, requires a separate, specific opt-in under Article 6(1)(a), disabled by default. The choice must explain the purpose, data, recipients and effect of withdrawal. Any special-category data additionally requires an applicable Article 9 condition; a generic AI opt-in does not cover biometric identification or every use of a person's voice.
The separate identity-linked AI opt-in is available and off by default; section 29 records the current control status. Its availability does not mean that any particular training or output processing has begun, and the purpose-specific requirements above still apply. Refusing an optional AI feature does not remove ordinary browsing or contribution access where the other eligibility requirements are met.
Contribution records may also support AI training, evaluation and development under the applicable contribution terms. This does not automatically make personal data in those records available for every training purpose.
Default training boundary
Personal account and profile identifiers must be excluded from training by default. This includes account IDs, login or contact emails, profile links and identifying profile fields. Removing those fields is not proof that all remaining content is anonymous: a recording, message or other contribution may itself identify a person, and an Actor ID may remain linkable.
Before training on contribution material that remains personal data, Qiraa must identify the training purpose, its Article 6 lawful basis and any required Article 9 condition, and provide the relevant privacy information. Training on that personal data must not begin while those requirements are unresolved.
Identity-linked features
Using identifiable account or profile information in training, or deliberately linking an AI output to a contributor's identity, requires a separate, specific opt-in under Article 6(1)(a), disabled by default. The choice must explain the purpose, data, recipients and effect of withdrawal. Any special-category data additionally requires an applicable Article 9 condition; a generic AI opt-in does not cover biometric identification or every use of a person's voice.
The separate identity-linked AI opt-in is available and off by default; section 29 records the current control status. Its availability does not mean that any particular training or output processing has begun, and the purpose-specific requirements above still apply. Refusing an optional AI feature does not remove ordinary browsing or contribution access where the other eligibility requirements are met.
9. Lawful bases
The basis depends on the specific purpose. Accepting contribution terms, confirming a profile preview and granting intellectual-property rights do not themselves establish a data-protection basis for every use.
Article 6(1)(b), contract, applies only where the processing is objectively necessary to provide the contributor functionality or perform the relevant agreement. A contractual clause alone cannot make unrelated publication or training necessary.
Qiraa's legitimate interests under Article 6(1)(f) include accountable contribution and review, preserving provenance, preventing impersonation and abuse, securing the service and resolving disputes. Required basic public attribution may rely on this basis only where it is ordinary, non-sensitive personal data and the necessity and balancing assessment supports the disclosure. You can object to processing based on legitimate interests.
The existence of an interest does not justify every field, audience or retention period. Less intrusive means and the effect on the individual must be considered. Where attribution or its context reveals special-category information, Article 6(1)(f) alone is insufficient; section 19 applies.
Optional work-email publication and specific identity-linked AI features rely on separate consent under Article 6(1)(a). Optional sensitive profile fields require freely given explicit consent under Articles 6(1)(a) and 9(2)(a) for the specified collection and publication. These choices must not be bundled with ordinary access or enabled by default.
You may withdraw consent through any available control or by contacting support@qiraa.ai. Withdrawal does not affect prior lawful processing. Future processing under that consent must stop; any request about existing data or outputs must be assessed under the applicable rights rather than treated as overridden by a contribution licence.
Article 6(1)(c) applies where a specific legal obligation requires processing; a general wish to preserve records is not such an obligation. Other processing, including identifiable audio training or biometric verification, requires its own purpose-specific assessment and any necessary additional condition before it starts. No unselected basis or special-category exception is inferred from this Notice.
Account and contributor administration
Article 6(1)(b), contract, applies only where the processing is objectively necessary to provide the contributor functionality or perform the relevant agreement. A contractual clause alone cannot make unrelated publication or training necessary.
Ordinary attribution, workflow integrity and security
Qiraa's legitimate interests under Article 6(1)(f) include accountable contribution and review, preserving provenance, preventing impersonation and abuse, securing the service and resolving disputes. Required basic public attribution may rely on this basis only where it is ordinary, non-sensitive personal data and the necessity and balancing assessment supports the disclosure. You can object to processing based on legitimate interests.
The existence of an interest does not justify every field, audience or retention period. Less intrusive means and the effect on the individual must be considered. Where attribution or its context reveals special-category information, Article 6(1)(f) alone is insufficient; section 19 applies.
Optional publication and identity-linked AI
Optional work-email publication and specific identity-linked AI features rely on separate consent under Article 6(1)(a). Optional sensitive profile fields require freely given explicit consent under Articles 6(1)(a) and 9(2)(a) for the specified collection and publication. These choices must not be bundled with ordinary access or enabled by default.
You may withdraw consent through any available control or by contacting support@qiraa.ai. Withdrawal does not affect prior lawful processing. Future processing under that consent must stop; any request about existing data or outputs must be assessed under the applicable rights rather than treated as overridden by a contribution licence.
Legal obligations and other purposes
Article 6(1)(c) applies where a specific legal obligation requires processing; a general wish to preserve records is not such an obligation. Other processing, including identifiable audio training or biometric verification, requires its own purpose-specific assessment and any necessary additional condition before it starts. No unselected basis or special-category exception is inferred from this Notice.
10. Corpus history and permanent contributions
Qiraa Corpus is designed around a versioned, append-oriented historical model.
Published contributions are therefore not treated like ordinary social-media posts or editable account content.
Once a change has been committed to the Corpus, it may form part of:
A published contribution may subsequently be:
However, the historical record showing that the earlier change existed may remain.
Preserving version history does not override an obligation to erase, correct or restrict personal data. Where a historical record contains personal data, the applicable rights must be assessed for that record as well as for the current profile.
Where personal attribution associated with a historical contribution must be removed or restricted, Qiraa may modify the attribution layer without deleting or altering the underlying non-personal Corpus contribution.
Published contributions are therefore not treated like ordinary social-media posts or editable account content.
Once a change has been committed to the Corpus, it may form part of:
- an immutable commit history;
- a published Corpus version;
- a downstream dataset;
- a research reference;
- an API response;
- a derived dataset;
- a validation history; or
- a later Corpus build.
A published contribution may subsequently be:
- amended;
- corrected;
- superseded;
- merged;
- disputed;
- reverted in a later version; or
- replaced by another contributor.
However, the historical record showing that the earlier change existed may remain.
Preserving version history does not override an obligation to erase, correct or restrict personal data. Where a historical record contains personal data, the applicable rights must be assessed for that record as well as for the current profile.
Where personal attribution associated with a historical contribution must be removed or restricted, Qiraa may modify the attribution layer without deleting or altering the underlying non-personal Corpus contribution.
11. Account closure, attribution removal and anonymisation
Account closure, removal of a public profile, erasure of personal data and anonymisation are different actions. A request is assessed against the information involved, its purpose and the applicable data-protection rights. Removing a profile does not, by itself, remove identifying information from contributions, messages, recordings, acceptance evidence or historical copies.
On account deletion, Qiraa immediately removes your live personal profile and its contact details and the ordinary link between your account and Corpus Actor ID. Qiraa requests deletion of the related Veriff-held verification records as part of that process and immediately removes its private account-linked verification reference. Provider deletion and operational backup expiry are separate processes described in section 14.
Where an identified legal obligation or an open dispute or claim requires limited information to be retained, that information is restricted to that purpose rather than kept as a live public profile or an ordinary account link. It is reviewed and deleted without undue delay when the exception ends. An existing contribution licence does not, by itself, require permanent retention of personal account links.
Removing a name or replacing it with an Actor ID can reduce public identification without making a record anonymous. Where an individual can still be identified using information reasonably available to Qiraa, the affected records remain personal data.
Pseudonymisation keeps the information needed to reconnect a record to an individual separately and protects it with appropriate safeguards. The pseudonymised record remains personal data for Qiraa where it retains that additional information. Even after the ordinary account link is removed, a restricted lawful-hold record, historical attribution, a comment, a recording or other content may still identify someone. Each remaining identifying source requires its own assessment.
Anonymisation requires that the individual is no longer identifiable by means reasonably likely to be used, taking account of the record itself and other available information. Changing an attribution label or deleting a single mapping is not sufficient where another means of identification remains. Genuinely anonymised information may no longer permit restoration of your previous attribution.
Where a lawful historical record is retained with personal attribution removed, distinct pseudonymous actor references preserve the distinction between authors, reviewers and other participants. Removing a public name must not merge different reviewers into one actor or reassign their authorship, review or approval to Qiraa.
Canonical Actor IDs remain distinct in the retained Corpus history. The record may be maintained generically by Qiraa after its personal profile association is removed, but the historical participants are not all replaced with a single Qiraa actor. Comments, audio, source material and other identifying content remain subject to redaction, restriction or erasure assessment.
Qiraa may be identified separately as the custodian maintaining a record. That label does not identify Qiraa as its original author, reviewer or approver. Pseudonymous references can preserve recorded workflow relationships; they do not, on their own, establish that the original review was independent.
Where personal attribution is removed, a historical entry is shown as Contributor identity removed, with a distinct pseudonymous reference so that different participants are not merged. This label does not mean Qiraa wrote, reviewed or approved the entry. Qiraa’s role as custodian is shown separately as Maintained by Qiraa. Identifying content within the entry requires separate assessment.
Where identifying information associated with a voice Contribution is removed, Qiraa may remove the contributor profile association and other identifying metadata while retaining the underlying recording where Qiraa has a lawful basis to do so.
A voice recording will not be represented as having been personally recited or performed by Qiraa merely because its original contributor attribution has been removed.
A release may use a separate attribution reference rather than embedding profile details in every record. Updating such a reference changes the current attribution information; it does not automatically update earlier releases, downloaded references or third-party copies, or make previously identifying data anonymous.
This Notice does not impose new contractual obligations on third parties or retroactively change a licence under which a copy was obtained. Applicable data-protection obligations remain separate from any release licence.
Where an erasure obligation applies to personal data disclosed to recipients, Qiraa must inform those recipients unless doing so is impossible or involves disproportionate effort. Where Qiraa has made the data public, it must take reasonable steps, taking account of available technology and implementation cost, to inform other controllers processing it of the request to erase links, copies or replications. Independent copies cannot be guaranteed to disappear.
The request process and response time limits are described in section 22. A release schedule does not extend a legal deadline for acting on a rights request.
A request concerning personal information does not automatically revoke intellectual-property permissions granted under the Contribution Licence. The Contributor Terms govern the contribution workflow. Those permissions do not override a requirement to erase or restrict personal data.
Account deletion and live records
On account deletion, Qiraa immediately removes your live personal profile and its contact details and the ordinary link between your account and Corpus Actor ID. Qiraa requests deletion of the related Veriff-held verification records as part of that process and immediately removes its private account-linked verification reference. Provider deletion and operational backup expiry are separate processes described in section 14.
Where an identified legal obligation or an open dispute or claim requires limited information to be retained, that information is restricted to that purpose rather than kept as a live public profile or an ordinary account link. It is reviewed and deleted without undue delay when the exception ends. An existing contribution licence does not, by itself, require permanent retention of personal account links.
Pseudonymisation and anonymisation
Removing a name or replacing it with an Actor ID can reduce public identification without making a record anonymous. Where an individual can still be identified using information reasonably available to Qiraa, the affected records remain personal data.
Pseudonymisation keeps the information needed to reconnect a record to an individual separately and protects it with appropriate safeguards. The pseudonymised record remains personal data for Qiraa where it retains that additional information. Even after the ordinary account link is removed, a restricted lawful-hold record, historical attribution, a comment, a recording or other content may still identify someone. Each remaining identifying source requires its own assessment.
Anonymisation requires that the individual is no longer identifiable by means reasonably likely to be used, taking account of the record itself and other available information. Changing an attribution label or deleting a single mapping is not sufficient where another means of identification remains. Genuinely anonymised information may no longer permit restoration of your previous attribution.
Preserving distinct contributors and reviewers
Where a lawful historical record is retained with personal attribution removed, distinct pseudonymous actor references preserve the distinction between authors, reviewers and other participants. Removing a public name must not merge different reviewers into one actor or reassign their authorship, review or approval to Qiraa.
Canonical Actor IDs remain distinct in the retained Corpus history. The record may be maintained generically by Qiraa after its personal profile association is removed, but the historical participants are not all replaced with a single Qiraa actor. Comments, audio, source material and other identifying content remain subject to redaction, restriction or erasure assessment.
Qiraa may be identified separately as the custodian maintaining a record. That label does not identify Qiraa as its original author, reviewer or approver. Pseudonymous references can preserve recorded workflow relationships; they do not, on their own, establish that the original review was independent.
Where personal attribution is removed, a historical entry is shown as Contributor identity removed, with a distinct pseudonymous reference so that different participants are not merged. This label does not mean Qiraa wrote, reviewed or approved the entry. Qiraa’s role as custodian is shown separately as Maintained by Qiraa. Identifying content within the entry requires separate assessment.
Voice Contributions
Where identifying information associated with a voice Contribution is removed, Qiraa may remove the contributor profile association and other identifying metadata while retaining the underlying recording where Qiraa has a lawful basis to do so.
A voice recording will not be represented as having been personally recited or performed by Qiraa merely because its original contributor attribution has been removed.
Attribution references and historical copies
A release may use a separate attribution reference rather than embedding profile details in every record. Updating such a reference changes the current attribution information; it does not automatically update earlier releases, downloaded references or third-party copies, or make previously identifying data anonymous.
This Notice does not impose new contractual obligations on third parties or retroactively change a licence under which a copy was obtained. Applicable data-protection obligations remain separate from any release licence.
Where an erasure obligation applies to personal data disclosed to recipients, Qiraa must inform those recipients unless doing so is impossible or involves disproportionate effort. Where Qiraa has made the data public, it must take reasonable steps, taking account of available technology and implementation cost, to inform other controllers processing it of the request to erase links, copies or replications. Independent copies cannot be guaranteed to disappear.
Requests and contribution rights
The request process and response time limits are described in section 22. A release schedule does not extend a legal deadline for acting on a rights request.
A request concerning personal information does not automatically revoke intellectual-property permissions granted under the Contribution Licence. The Contributor Terms govern the contribution workflow. Those permissions do not override a requirement to erase or restrict personal data.
12. Messages and discussions
Public Corpus discussions preserve the reasoning and review history surrounding changes. Where a tool offers author editing or deletion, the controls and any editing period actually displayed by that tool apply. This Notice does not create a universal editing window or guarantee self-service editing or deletion.
You can contact support@qiraa.ai to request a correction or exercise applicable privacy rights, whether or not an editing control is available. Qiraa may redact, restrict, correct or remove messages where necessary for legal compliance, privacy, security, safeguarding, intellectual-property concerns, confidentiality, abuse prevention or moderation.
Where personal attribution is removed, a historical entry is shown as Contributor identity removed, with a distinct pseudonymous reference so that different participants are not merged. This label does not mean Qiraa wrote, reviewed or approved the entry. Qiraa’s role as custodian is shown separately as Maintained by Qiraa.
Identifying information in the entry itself must be assessed separately; changing the displayed name alone may not meet an applicable erasure or restriction obligation.
You can contact support@qiraa.ai to request a correction or exercise applicable privacy rights, whether or not an editing control is available. Qiraa may redact, restrict, correct or remove messages where necessary for legal compliance, privacy, security, safeguarding, intellectual-property concerns, confidentiality, abuse prevention or moderation.
Where personal attribution is removed, a historical entry is shown as Contributor identity removed, with a distinct pseudonymous reference so that different participants are not merged. This label does not mean Qiraa wrote, reviewed or approved the entry. Qiraa’s role as custodian is shown separately as Maintained by Qiraa.
Identifying information in the entry itself must be assessed separately; changing the displayed name alone may not meet an applicable erasure or restriction obligation.
13. Voice recitations and AI use
A recitation can remain identifiable from the voice or its content after its name, account link and profile metadata are removed. Such a recording remains personal data. An ordinary voice recording is not automatically biometric special-category data, but particular recognition processing may involve biometrics, and the recording or its context may reveal other special-category information.
Audio contributions are available to authorised contributors. The notice shown before recording or upload distinguishes Corpus publication, annotation, research, AI training and any identity-linked output feature. It identifies the intended uses, personal data involved, recipients, retention criteria and applicable legal grounds. Intellectual-property and performer permissions are handled under the Contributor Terms and Contribution Licence; they do not replace those privacy requirements. An available recording or upload feature does not mean that every listed processing purpose is active.
Contribution records may be used for AI training, with personal account and profile identifiers excluded by default. That policy does not declare a recognisable voice anonymous or establish the lawful basis for training on identifiable audio. Such processing must not begin until the purpose-specific basis and any necessary special-category condition have been identified and communicated.
The standard grant does not authorise creating a synthetic voice, voice model or voice-generation system from a Contribution, whether or not it is linked to an identifiable contributor. Such a use requires a separate, specific opt-in that describes the use before it starts.
Synthesis and identity-linked training or output choices are disabled by default. Identity-linked features need the separate, specific opt-in described in sections 8 and 9. Ordinary non-synthesis training remains subject to the Contribution Licence and privacy requirements. Each proposed use requires its own scope, rights and privacy assessment; a generic AI choice does not authorise impersonation or establish a biometric legal condition.
If you request erasure, restriction or object to processing, Qiraa must assess the recording itself, its metadata and the particular uses. Depending on the applicable right and legal grounds, action may include deleting the audio, restricting use or access, or retaining an effectively anonymised version. Continued retention of identifiable audio requires a valid basis and, where an erasure right applies, an applicable legal exception. A perpetual licence or the value of training data is not a blanket exception.
Removing attribution must not suggest that Qiraa performed the recitation. Any limits on removing existing model data or outputs must be explained for the actual system; this Notice does not promise either universal model unlearning or an exemption from privacy rights.
Audio contributions are available to authorised contributors. The notice shown before recording or upload distinguishes Corpus publication, annotation, research, AI training and any identity-linked output feature. It identifies the intended uses, personal data involved, recipients, retention criteria and applicable legal grounds. Intellectual-property and performer permissions are handled under the Contributor Terms and Contribution Licence; they do not replace those privacy requirements. An available recording or upload feature does not mean that every listed processing purpose is active.
Contribution records may be used for AI training, with personal account and profile identifiers excluded by default. That policy does not declare a recognisable voice anonymous or establish the lawful basis for training on identifiable audio. Such processing must not begin until the purpose-specific basis and any necessary special-category condition have been identified and communicated.
The standard grant does not authorise creating a synthetic voice, voice model or voice-generation system from a Contribution, whether or not it is linked to an identifiable contributor. Such a use requires a separate, specific opt-in that describes the use before it starts.
Synthesis and identity-linked training or output choices are disabled by default. Identity-linked features need the separate, specific opt-in described in sections 8 and 9. Ordinary non-synthesis training remains subject to the Contribution Licence and privacy requirements. Each proposed use requires its own scope, rights and privacy assessment; a generic AI choice does not authorise impersonation or establish a biometric legal condition.
If you request erasure, restriction or object to processing, Qiraa must assess the recording itself, its metadata and the particular uses. Depending on the applicable right and legal grounds, action may include deleting the audio, restricting use or access, or retaining an effectively anonymised version. Continued retention of identifiable audio requires a valid basis and, where an erasure right applies, an applicable legal exception. A perpetual licence or the value of training data is not a blanket exception.
Removing attribution must not suggest that Qiraa performed the recitation. Any limits on removing existing model data or outputs must be explained for the actual system; this Notice does not promise either universal model unlearning or an exemption from privacy rights.
14. Retention
Personal data is retained only for as long as necessary for its stated purpose. The criteria below identify the events and continuing needs that determine retention; they do not make all information part of a permanent archive.
The application, profile/account and security-log deletion deadlines below apply to live operational records. Protected backup copies expire separately, within three months of each backup’s creation, as described below.
Application information is needed while the access decision remains outstanding. Unsuccessful access applications are deleted within 6 months of the decision, unless needed for an open abuse investigation, a legal obligation or a legal claim. Information retained under an exception is restricted to that purpose, reviewed when the matter ends and deleted without undue delay once the exception no longer applies. This does not authorise indefinite retention of an unsuccessful application.
On account deletion, Qiraa immediately removes the live personal profile, its contact details and the ordinary account-to-Actor-ID link. A profile-removal request, change in role or other applicable rights request also requires the affected information to be assessed. A need to preserve limited Corpus history does not justify keeping an entire profile public. Any information required for an identified legal obligation or an open dispute or claim is held separately, with access restricted to that purpose, and deleted without undue delay when that need ends.
You can contact support@qiraa.ai to request a correction or exercise your applicable rights; this does not depend on a self-service profile control being available.
Veriff holds the identity-verification materials; Qiraa does not store the original identity documents, photographs or video. Qiraa retains only the private reference ID linked to the account for that identity and age process. Under the current Veriff arrangement, verification records are retained while the account remains active.
Qiraa requests deletion of the related records held by Veriff as part of account deletion and immediately removes its account-linked reference. An identified legal obligation or an open dispute or claim may require limited information to be retained for that specific purpose. Such information is restricted, reviewed when the matter ends and deleted without undue delay when the exception no longer applies. Neither the reference nor the original identity evidence forms part of the permanent Corpus archive.
A deletion request to Veriff does not mean its records disappear immediately. Provider deletion follows the applicable arrangements and any identified lawful retention requirement. The Veriff Privacy Notice and Veriff terms describe its processing and should be read alongside this Notice; they do not remove Qiraa's responsibilities for the processing it determines. You can contact support@qiraa.ai about the handling of a verification-record request.
Optional supporting documents submitted to Qiraa, including CVs and qualification, employment or affiliation evidence, are separate from the Veriff identity process and used only for verification. Qiraa deletes the originals from live systems after verification is complete. Keeping verified facts, a limited result or internal badges or tags does not justify keeping the original documents.
Only the specific evidence necessary for an identified legal obligation or an open dispute or claim may be retained as an exception. Access and use are restricted to that matter, the need is reviewed when it ends, and the evidence is deleted without undue delay once the exception no longer applies. Protected operational backup copies expire under the separate three-month maximum below; they do not permit continued ordinary use of a deleted supporting document.
Current qualification and role records support contributor permissions while those permissions remain in use. Expiry, revocation or account deletion changes that purpose. Any remaining historical record requires a continuing need, such as explaining the status held when a recorded action occurred or resolving a specific dispute, and must not imply current verification.
A role change, verification expiry or renewal requires the accuracy and continuing need for earlier employment evidence to be reassessed. An earlier verification does not justify indefinite retention of its supporting documents.
Permanent preservation covers published Corpus releases and Corpus-only archives of content, comments, changes and history. It excludes personal profile records, contact details, ordinary account links and Veriff references. These archives are distinct from operational database backups; the existence of a database snapshot does not make its account or verification information part of a permanent Corpus archive.
Non-personal contributions and lawful version history may remain for the lifetime of the Corpus and its historical releases. Distinct canonical Actor IDs preserve the relationships between participants after their personal profile associations are removed. This does not make all history anonymous: comments, recordings, historical attribution or source content may still identify someone. Identifiable or pseudonymised material remains subject to purpose limitation, necessity, redaction and applicable rights, including in old releases.
Acceptance evidence is limited to what remains necessary to demonstrate the applicable document version and covered submission. The ordinary account-to-Actor-ID link is removed on account deletion. Any identifying acceptance detail retained after deletion requires an identified legal obligation or an open dispute or claim, is restricted to that purpose and is deleted without undue delay when the exception ends. A perpetual intellectual-property licence does not itself require permanent retention of identifying acceptance details.
Discussion records may be needed to explain a contribution or review decision. Account closure, an applicable rights request or identifying content in a message requires assessment of what can lawfully remain, what must be restricted or redacted, and whether a non-personal account of the discussion is sufficient.
Audio retention depends on the stated publication, analysis or training purpose and its legal grounds. Completion of that purpose, withdrawal of applicable consent or a rights request triggers assessment of the recording and its uses. Recognisable audio remains personal data even after attribution is removed; section 13 explains the limits on continued retention.
Routine security logs are deleted within 12 months of collection, unless tied to an identified security incident, investigation or legal claim. Logs retained under an exception are restricted to that matter and deleted without undue delay once it ends and no applicable legal obligation or claim requires them. The continuing existence of the Corpus is not a reason to retain all technical logs.
Daily and weekly operational database backups are managed through AWS RDS and retained for up to 3 months from creation. Sensitive database fields are encrypted. These backups support recovery and are separate from the permanent Corpus-only archives described above.
Information removed from live systems may remain in protected operational backups until those backups expire. It is not restored to ordinary use merely because a backup exists. If a backup is restored, applicable deletions and restrictions must be reapplied before the restored information returns to ordinary use. Any narrowly necessary preservation for an identified legal obligation or an open dispute or claim is restricted to that purpose and reviewed when the matter ends; it is not an extension of routine backup retention.
These periods are maximums, not a reason to keep information that is no longer needed. If a published deletion deadline is missed, Qiraa will record the failure internally and notify the affected person where contact details are available, explaining the remedial action and revised date. A missed internal deadline does not extend an applicable legal deadline.
The application, profile/account and security-log deletion deadlines below apply to live operational records. Protected backup copies expire separately, within three months of each backup’s creation, as described below.
Access applications
Application information is needed while the access decision remains outstanding. Unsuccessful access applications are deleted within 6 months of the decision, unless needed for an open abuse investigation, a legal obligation or a legal claim. Information retained under an exception is restricted to that purpose, reviewed when the matter ends and deleted without undue delay once the exception no longer applies. This does not authorise indefinite retention of an unsuccessful application.
Public profile information
On account deletion, Qiraa immediately removes the live personal profile, its contact details and the ordinary account-to-Actor-ID link. A profile-removal request, change in role or other applicable rights request also requires the affected information to be assessed. A need to preserve limited Corpus history does not justify keeping an entire profile public. Any information required for an identified legal obligation or an open dispute or claim is held separately, with access restricted to that purpose, and deleted without undue delay when that need ends.
You can contact support@qiraa.ai to request a correction or exercise your applicable rights; this does not depend on a self-service profile control being available.
Veriff identity records and the account reference
Veriff holds the identity-verification materials; Qiraa does not store the original identity documents, photographs or video. Qiraa retains only the private reference ID linked to the account for that identity and age process. Under the current Veriff arrangement, verification records are retained while the account remains active.
Qiraa requests deletion of the related records held by Veriff as part of account deletion and immediately removes its account-linked reference. An identified legal obligation or an open dispute or claim may require limited information to be retained for that specific purpose. Such information is restricted, reviewed when the matter ends and deleted without undue delay when the exception no longer applies. Neither the reference nor the original identity evidence forms part of the permanent Corpus archive.
A deletion request to Veriff does not mean its records disappear immediately. Provider deletion follows the applicable arrangements and any identified lawful retention requirement. The Veriff Privacy Notice and Veriff terms describe its processing and should be read alongside this Notice; they do not remove Qiraa's responsibilities for the processing it determines. You can contact support@qiraa.ai about the handling of a verification-record request.
Qualification and role verification
Optional supporting documents submitted to Qiraa, including CVs and qualification, employment or affiliation evidence, are separate from the Veriff identity process and used only for verification. Qiraa deletes the originals from live systems after verification is complete. Keeping verified facts, a limited result or internal badges or tags does not justify keeping the original documents.
Only the specific evidence necessary for an identified legal obligation or an open dispute or claim may be retained as an exception. Access and use are restricted to that matter, the need is reviewed when it ends, and the evidence is deleted without undue delay once the exception no longer applies. Protected operational backup copies expire under the separate three-month maximum below; they do not permit continued ordinary use of a deleted supporting document.
Current qualification and role records support contributor permissions while those permissions remain in use. Expiry, revocation or account deletion changes that purpose. Any remaining historical record requires a continuing need, such as explaining the status held when a recorded action occurred or resolving a specific dispute, and must not imply current verification.
Employment verification
A role change, verification expiry or renewal requires the accuracy and continuing need for earlier employment evidence to be reassessed. An earlier verification does not justify indefinite retention of its supporting documents.
Contributions and provenance
Permanent preservation covers published Corpus releases and Corpus-only archives of content, comments, changes and history. It excludes personal profile records, contact details, ordinary account links and Veriff references. These archives are distinct from operational database backups; the existence of a database snapshot does not make its account or verification information part of a permanent Corpus archive.
Non-personal contributions and lawful version history may remain for the lifetime of the Corpus and its historical releases. Distinct canonical Actor IDs preserve the relationships between participants after their personal profile associations are removed. This does not make all history anonymous: comments, recordings, historical attribution or source content may still identify someone. Identifiable or pseudonymised material remains subject to purpose limitation, necessity, redaction and applicable rights, including in old releases.
Acceptance evidence is limited to what remains necessary to demonstrate the applicable document version and covered submission. The ordinary account-to-Actor-ID link is removed on account deletion. Any identifying acceptance detail retained after deletion requires an identified legal obligation or an open dispute or claim, is restricted to that purpose and is deleted without undue delay when the exception ends. A perpetual intellectual-property licence does not itself require permanent retention of identifying acceptance details.
Messages
Discussion records may be needed to explain a contribution or review decision. Account closure, an applicable rights request or identifying content in a message requires assessment of what can lawfully remain, what must be restricted or redacted, and whether a non-personal account of the discussion is sufficient.
Audio
Audio retention depends on the stated publication, analysis or training purpose and its legal grounds. Completion of that purpose, withdrawal of applicable consent or a rights request triggers assessment of the recording and its uses. Recognisable audio remains personal data even after attribution is removed; section 13 explains the limits on continued retention.
Security information
Routine security logs are deleted within 12 months of collection, unless tied to an identified security incident, investigation or legal claim. Logs retained under an exception are restricted to that matter and deleted without undue delay once it ends and no applicable legal obligation or claim requires them. The continuing existence of the Corpus is not a reason to retain all technical logs.
Operational database backups
Daily and weekly operational database backups are managed through AWS RDS and retained for up to 3 months from creation. Sensitive database fields are encrypted. These backups support recovery and are separate from the permanent Corpus-only archives described above.
Information removed from live systems may remain in protected operational backups until those backups expire. It is not restored to ordinary use merely because a backup exists. If a backup is restored, applicable deletions and restrictions must be reapplied before the restored information returns to ordinary use. Any narrowly necessary preservation for an identified legal obligation or an open dispute or claim is restricted to that purpose and reviewed when the matter ends; it is not an extension of routine backup retention.
These periods are maximums, not a reason to keep information that is no longer needed. If a published deletion deadline is missed, Qiraa will record the failure internally and notify the affected person where contact details are available, explaining the remedial action and revised date. A missed internal deadline does not extend an applicable legal deadline.
16. International transfers
Some Qiraa service providers may process information outside the United Kingdom.
Where applicable data protection law requires additional safeguards for an international transfer, Qiraa will use an appropriate transfer mechanism and assess the protection available for the information.
The main Qiraa Privacy Policy contains additional information about Qiraa's general international data-transfer practices.
Where applicable data protection law requires additional safeguards for an international transfer, Qiraa will use an appropriate transfer mechanism and assess the protection available for the information.
The main Qiraa Privacy Policy contains additional information about Qiraa's general international data-transfer practices.
17. Security
Qiraa applies technical and organisational measures appropriate to the nature and risk of Corpus information. Sensitive database fields are encrypted. Operational databases and their daily and weekly backups use AWS RDS, with backup retention limited as described in section 14.
Corpus design should separate:
Veriff holds the original identity-verification materials; Qiraa does not store those documents, photographs or video. Access to Qiraa's private account-linked verification reference and any separately collected qualification or employment evidence is restricted to authorised personnel who require it for the relevant purpose.
Qiraa also uses security controls intended to detect unauthorised access, abuse and attempts to compromise contributor or Corpus systems.
No internet-connected system can be guaranteed to be completely secure.
Corpus design should separate:
- public contributor information;
- private account information;
- authentication information;
- verification evidence;
- internal audit information; and
- Corpus content.
Veriff holds the original identity-verification materials; Qiraa does not store those documents, photographs or video. Access to Qiraa's private account-linked verification reference and any separately collected qualification or employment evidence is restricted to authorised personnel who require it for the relevant purpose.
Qiraa also uses security controls intended to detect unauthorised access, abuse and attempts to compromise contributor or Corpus systems.
No internet-connected system can be guaranteed to be completely secure.
18. Accuracy and changing professional information
You are responsible for keeping public profile information reasonably accurate.
You should update Qiraa if:
Changing your current profile does not necessarily rewrite historical records.
For example, a historical contribution may legitimately record the organisation or role you held at the time that work was performed.
Where personal information is inaccurate for the purpose for which it is held, Qiraa may correct the attribution layer without altering the underlying historical Corpus contribution.
You should update Qiraa if:
- your work email changes;
- you leave your organisation;
- your professional role changes;
- a displayed qualification is incorrect;
- your affiliation changes; or
- other publicly displayed information becomes inaccurate.
Changing your current profile does not necessarily rewrite historical records.
For example, a historical contribution may legitimately record the organisation or role you held at the time that work was performed.
Where personal information is inaccurate for the purpose for which it is held, Qiraa may correct the attribution layer without altering the underlying historical Corpus contribution.
19. Special-category information
Browsing an Islamic corpus does not establish a person's religion. A biography, qualification, affiliation, recitation or the combination of identity and context may nevertheless reveal religious beliefs or other specially protected information. Deliberately inferring beliefs or treating people differently on that inference also requires assessment; Qiraa must not infer a legal exception merely from the Corpus's subject matter.
Collection and publication of optional sensitive profile information require separate, freely given explicit consent under Articles 6(1)(a) and 9(2)(a). Before collection, the choice must identify the information, the specified purposes and public audience, and how consent can be withdrawn. It must be off by default and separate from agreement to contributor terms. Revealing religion or completing a sensitive optional field is not a condition of contributing.
Basic attribution cannot be treated as ordinary personal data if identifying the contributor in context reveals special-category information. Where valid explicit consent cannot be freely given, the affected processing and publication must not proceed unless another valid Article 9 condition, the Article 6 basis and any required statutory safeguards have been identified and documented. This Notice does not select or assume such an alternative condition.
Qiraa cannot justify its initial publication of private sensitive information by claiming that the individual has already made it manifestly public. A preview confirmation or general access checkbox is not, by itself, explicit consent.
You can withdraw consent through any available control or by contacting support@qiraa.ai. Optional processing under that consent must stop, without penalising ordinary contribution access. The applicable rights must also be assessed for published copies and retained records; withdrawing an optional field does not automatically erase a separate lawful non-personal contribution.
Biometric verification, identifiable audio processing and other sensitive uses require their own assessment and applicable conditions. A profile-publication choice or ordinary AI-training permission does not authorise all of them. Features must not collect or publish the affected information until their required safeguards are in place.
Optional sensitive fields
Collection and publication of optional sensitive profile information require separate, freely given explicit consent under Articles 6(1)(a) and 9(2)(a). Before collection, the choice must identify the information, the specified purposes and public audience, and how consent can be withdrawn. It must be off by default and separate from agreement to contributor terms. Revealing religion or completing a sensitive optional field is not a condition of contributing.
Where required attribution itself is sensitive
Basic attribution cannot be treated as ordinary personal data if identifying the contributor in context reveals special-category information. Where valid explicit consent cannot be freely given, the affected processing and publication must not proceed unless another valid Article 9 condition, the Article 6 basis and any required statutory safeguards have been identified and documented. This Notice does not select or assume such an alternative condition.
Qiraa cannot justify its initial publication of private sensitive information by claiming that the individual has already made it manifestly public. A preview confirmation or general access checkbox is not, by itself, explicit consent.
You can withdraw consent through any available control or by contacting support@qiraa.ai. Optional processing under that consent must stop, without penalising ordinary contribution access. The applicable rights must also be assessed for published copies and retained records; withdrawing an optional field does not automatically erase a separate lawful non-personal contribution.
Biometric verification, identifiable audio processing and other sensitive uses require their own assessment and applicable conditions. A profile-publication choice or ordinary AI-training permission does not authorise all of them. Features must not collect or publish the affected information until their required safeguards are in place.
20. Automated verification and decision-making
Identity and age verification uses technology operated by Veriff and may involve automated checks. Qiraa uses the verification process to determine whether the identity and minimum-age requirements for contributor access are met.
A failed or inconclusive check prevents contributor-platform access until your identity and eligibility as a person aged 18 or over are verified. This does not prevent public browsing and is not, by itself, a finding that you supplied false information.
Human reconsideration is available. Contact support@qiraa.ai to ask for the decision to be reviewed, explain a suspected error or provide relevant additional information through the appropriate verification process. Qiraa will explain the access decision and applicable review rights. Reconsideration does not guarantee approval or permit access while identity or age remains unverified; any new verification evidence must be handled through the appropriate process rather than published on your profile.
Where automated processing materially affects your access, Qiraa provides appropriate information about that processing and the rights that apply. Using a provider does not remove Qiraa's responsibility for its access decision. The reconsideration route does not limit your rights to challenge processing or contact a regulator.
Qualification verification is ordinarily carried out manually. Identity and age checks do not establish scholarly competence, validate a contribution or grant review permission. Scholarly contribution and review decisions remain subject to the separate expertise and workflow requirements.
A failed or inconclusive check prevents contributor-platform access until your identity and eligibility as a person aged 18 or over are verified. This does not prevent public browsing and is not, by itself, a finding that you supplied false information.
Human reconsideration is available. Contact support@qiraa.ai to ask for the decision to be reviewed, explain a suspected error or provide relevant additional information through the appropriate verification process. Qiraa will explain the access decision and applicable review rights. Reconsideration does not guarantee approval or permit access while identity or age remains unverified; any new verification evidence must be handled through the appropriate process rather than published on your profile.
Where automated processing materially affects your access, Qiraa provides appropriate information about that processing and the rights that apply. Using a provider does not remove Qiraa's responsibility for its access decision. The reconsideration route does not limit your rights to challenge processing or contact a regulator.
Qualification verification is ordinarily carried out manually. Identity and age checks do not establish scholarly competence, validate a contribution or grant review permission. Scholarly contribution and review decisions remain subject to the separate expertise and workflow requirements.
21. Your rights
Depending on applicable law, your location and the lawful basis used for a particular processing activity, you may have rights including the right to:
The right that applies and its scope depend on the processing and the relevant law. A contribution's presence in version history, or an intellectual-property licence allowing its use, is not by itself a reason to refuse a data-protection request.
Non-personal or effectively anonymised contributions may remain after personal data is removed. Where identifiable or pseudonymised information remains, its continued processing still needs an applicable lawful basis and must respect any relevant erasure, restriction or objection rights.
If Qiraa refuses all or part of a request, the response must explain the reasons and your options to complain to the ICO or seek a judicial remedy. A generic reference to permanent Corpus history is not a sufficient explanation of a legal exception.
- be informed about how your information is used;
- access personal information held about you;
- correct inaccurate or incomplete information;
- request deletion of information in applicable circumstances;
- request restriction of processing;
- object to certain processing;
- receive certain information in a portable format;
- withdraw consent where processing relies on consent; and
- complain to a relevant supervisory authority.
The right that applies and its scope depend on the processing and the relevant law. A contribution's presence in version history, or an intellectual-property licence allowing its use, is not by itself a reason to refuse a data-protection request.
Non-personal or effectively anonymised contributions may remain after personal data is removed. Where identifiable or pseudonymised information remains, its continued processing still needs an applicable lawful basis and must respect any relevant erasure, restriction or objection rights.
If Qiraa refuses all or part of a request, the response must explain the reasons and your options to complain to the ICO or seek a judicial remedy. A generic reference to permanent Corpus history is not a sufficient explanation of a legal exception.
22. How to make a privacy request
You may contact Qiraa to request:
For Corpus-related requests, contact support@qiraa.ai and say that your request concerns Corpus. Describe the information or activity involved so it can be located. You do not need to use legal terminology or an unavailable account control to exercise a right.
Where Qiraa has reasonable doubts about your identity, it may ask for the additional information necessary to confirm it. The information requested must be proportionate; identity documents are not automatically required for every request.
For requests under the UK GDPR, Qiraa must respond without undue delay and ordinarily within one calendar month of receipt. Applicable rules govern when the period starts if information reasonably needed to confirm your identity is outstanding. If further information is needed, Qiraa must explain what is needed and why.
Where necessary because of the complexity or number of requests, the response period may be extended by up to two further months. Qiraa must notify you of an extension and its reasons within the initial one-month period.
The response must explain the action taken, any information lawfully retained and the reason for retaining it, or the reasons for refusing all or part of the request. It must also explain your right to complain to the ICO and seek a judicial remedy where a request is refused. Required erasure is carried out without undue delay; a publication or attribution-update schedule does not replace that obligation.
- access;
- correction;
- deletion;
- de-identification;
- restriction;
- objection; or
- another applicable data-protection right.
For Corpus-related requests, contact support@qiraa.ai and say that your request concerns Corpus. Describe the information or activity involved so it can be located. You do not need to use legal terminology or an unavailable account control to exercise a right.
Where Qiraa has reasonable doubts about your identity, it may ask for the additional information necessary to confirm it. The information requested must be proportionate; identity documents are not automatically required for every request.
For requests under the UK GDPR, Qiraa must respond without undue delay and ordinarily within one calendar month of receipt. Applicable rules govern when the period starts if information reasonably needed to confirm your identity is outstanding. If further information is needed, Qiraa must explain what is needed and why.
Where necessary because of the complexity or number of requests, the response period may be extended by up to two further months. Qiraa must notify you of an extension and its reasons within the initial one-month period.
The response must explain the action taken, any information lawfully retained and the reason for retaining it, or the reasons for refusing all or part of the request. It must also explain your right to complain to the ICO and seek a judicial remedy where a request is refused. Required erasure is carried out without undue delay; a publication or attribution-update schedule does not replace that obligation.
23. Children and contributor eligibility
Public Corpus browsing is separate from contributor access and remains subject to Qiraa's general terms.
Current Corpus contributor, editing and reviewer access requires verified identity and eligibility as a person aged 18 or over. If the identity or age check fails or is inconclusive, contributor-platform access remains blocked until those requirements are verified. Human reconsideration under section 20 does not bypass the minimum age or the need to verify it.
Any future process for younger contributors would need separately announced eligibility rules, safeguards, privacy information and approval requirements. This Notice does not offer an exception to the current access requirements.
Current Corpus contributor, editing and reviewer access requires verified identity and eligibility as a person aged 18 or over. If the identity or age check fails or is inconclusive, contributor-platform access remains blocked until those requirements are verified. Human reconsideration under section 20 does not bypass the minimum age or the need to verify it.
Any future process for younger contributors would need separately announced eligibility rules, safeguards, privacy information and approval requirements. This Notice does not offer an exception to the current access requirements.
24. Changes to this Notice
Qiraa may update this Privacy Notice as the Corpus, applicable law, verification methods or processing activities change.
The latest version will display an updated effective date.
Where a change materially affects how contributor personal information is used, we will notify affected contributors before it applies to them.
Historical versions of this Notice may be retained for accountability.
The latest version will display an updated effective date.
Where a change materially affects how contributor personal information is used, we will notify affected contributors before it applies to them.
Historical versions of this Notice may be retained for accountability.
25. Language versions
Qiraa may make this Privacy Notice available in multiple languages.
Translations are provided to improve accessibility and understanding.
If there is an inconsistency between translated versions, the English version will be treated as the reference version to the extent permitted by applicable law.
Translations are provided to improve accessibility and understanding.
If there is an inconsistency between translated versions, the English version will be treated as the reference version to the extent permitted by applicable law.
26. Complaints
If you have a concern about Corpus personal information, you can contact support@qiraa.ai so Qiraa can investigate it.
You have the right to complain to the Information Commissioner's Office (ICO) about processing covered by UK data-protection law, and may have rights to complain to another competent authority. This Notice does not require you to complete an internal appeal before exercising an applicable legal remedy.
Exercising a data-protection right will not affect your right to raise a complaint.
You have the right to complain to the Information Commissioner's Office (ICO) about processing covered by UK data-protection law, and may have rights to complain to another competent authority. This Notice does not require you to complete an internal appeal before exercising an applicable legal remedy.
Exercising a data-protection right will not affect your right to raise a complaint.
27. Contact
Qiraa Ltd
Registered in England & Wales (Company No. 16939592)
ICO registration number: ZC223490.
For Corpus privacy requests and enquiries: support@qiraa.ai.
Postal contact: Qiraa, 61 Bridge Street, Kington, HR5 3DJ, United Kingdom.
The same support address can receive general Corpus enquiries. Underlying Qiraa account processing is also described in the main Qiraa Privacy Policy.
Registered in England & Wales (Company No. 16939592)
ICO registration number: ZC223490.
For Corpus privacy requests and enquiries: support@qiraa.ai.
Postal contact: Qiraa, 61 Bridge Street, Kington, HR5 3DJ, United Kingdom.
The same support address can receive general Corpus enquiries. Underlying Qiraa account processing is also described in the main Qiraa Privacy Policy.
29. Status of controls
As of 7 November 2026, the following controls and features are operational:
If a required control becomes unavailable, the feature or processing that depends on it must remain off until the control and any necessary safeguards are restored. Public browsing does not require a public contributor profile. The availability of these controls does not remove the separate duties, rights or restrictions described elsewhere in this Notice.
- Public-profile preview and confirmation: contributors see the actual public fields and confirm them before publication. Access approval alone does not publish an application or profile.
- Public work-email opt-in: publishing a work email is a separate optional choice, off by default. Declining it does not prevent otherwise eligible contributions.
- Identity-linked AI opt-in: the separate, specific choice is available and off by default. Its availability does not mean that a particular training pipeline or identity-linked output is running; each use still needs the purposes, permissions and legal grounds described in this Notice.
- Audio contributions: authorised contributors can submit audio through the contribution workflow, subject to the notices, rights and privacy requirements in section 13. This does not by itself activate AI training or voice synthesis.
- Human reconsideration of failed verification: a person can request review through support@qiraa.ai. Contributor-platform access remains blocked until identity and eligibility as a person aged 18 or over are verified; review does not bypass those requirements.
If a required control becomes unavailable, the feature or processing that depends on it must remain off until the control and any necessary safeguards are restored. Public browsing does not require a public contributor profile. The availability of these controls does not remove the separate duties, rights or restrictions described elsewhere in this Notice.
