Privacy policy

Fawaid Archive is a source-retrieval archive operated by the Fawaid Archive project. It makes stored, timestamped transcripts of public recordings searchable. The service does not generate religious answers, fatwas, or summaries. Clearly marked English translations may be machine-generated.

We process publicly available YouTube channel and video metadata, audio or declared captions, timed transcript text, source status, and provenance records so visitors can find and verify passages.

• Audio may be sent to OpenAI for automated speech recognition when usable captions are unavailable.
• Stored transcript passages may be sent to OpenAI to create numerical search embeddings.
• A visitor’s search text may be sent to OpenAI to create a search embedding when semantic or hybrid retrieval is used. Exact-mode searches do not need that embedding.
• Search text is used for retrieval; it is not used by Fawaid Archive to compose a religious response.

Public searching and transcript reading do not require an account. If you sign in with Google, we store the identity fields Google supplies (such as name, email, profile image, and provider account identifier), authentication tokens needed for the connection, an essential session token, your role, and preferred language.

• Collections, saved transcript moments, bookmarks, and notes you create.
• Correction reports you submit, including the cited text, explanation, and account email used for follow-up.
• Editorial actions and audit records if the account is assigned an editor or administrator role.

Rights requests can be submitted without an account. We store the requester’s name, email, stated authority, reason, evidence links, target source or video, handling status, and resolution so the request can be investigated and documented.

We use essential authentication and security cookies only. We do not sell personal data and do not use advertising cookies. Security and application logs may contain an IP address, request path, timestamp, and technical diagnostics.

• Google and YouTube provide sign-in, public source metadata, and privacy-enhanced embedded playback.
• OpenAI provides speech recognition and search embeddings.
• Infrastructure processors may include Hetzner, Cloudflare, Backblaze B2, Resend, and uptime-monitoring services for hosting, delivery, backups, transactional email, and availability checks.

Account data remains until you delete the account or ask us to act. Expired sessions and short-lived operational records are removed through maintenance. Routine application logs are intended to be retained for no more than 30 days and encrypted operational backups for no more than 30 days, except when a longer period is required to investigate abuse, protect the service, or meet a legal obligation.

Deleting a regular account removes its Google connection, authentication tokens, sessions, collections, saved moments, and bookmarks. Correction reports are retained as an anonymous editorial record. Rights requests and append-only publication or moderation records may be retained to protect source integrity, establish what action was taken, and meet legal obligations.

You can download an account-data copy or permanently delete a regular account from the Account page. Editors and administrators must first transfer their responsibilities and be returned to a regular-user role. You may also contact us to request access, correction, deletion, restriction, or to object where applicable in your jurisdiction.

• You may use the public archive without signing in.
• You may revoke Fawaid Archive in your Google account; revocation stops future Google access but does not by itself delete data already stored here.
• For a rights request that cannot be completed in the account interface, email us from the relevant address.

We use access controls, encrypted transport, constrained service credentials, and backups, but no internet service can promise absolute security. The service is not directed to children under 13 and we do not knowingly request their personal data. We may revise this policy as the service changes; the effective date above identifies the current version.