سياسة الخصوصية

Introduction

Alqamar Archive (“we”, “our”) respects your privacy and is committed to protecting it. This policy explains how we handle data when you use our website (alqamararchive.com) and mobile application.

Public Content Without an Account

Reading or watching public content does not require an account or your name, email address or phone number. We nevertheless process technical data and information you choose to submit, as described below. Using the service without an account does not mean that all data is anonymous.

Data We Process

• Visitor ID and Favorites: We use a random identifier (UUID) instead of a personal account. It is stored in the website's aq_uid cookie and locally in the app. The app sends this identifier with requests to our service. Favorites are stored on our servers with the visitor identifier, content type and ID, and date added. You can remove individual favorites. This technical identifier does not contain your name, but distinguishes repeated use of the service.
• Search: Search text is sent to our service to find content and may be processed by our search provider, Meilisearch. Request results may be cached to improve speed. Storing your recent-search list on your device does not mean that searches are processed only locally.
• AI Assistant (Chatbot): When you use it, your questions and necessary conversation context are sent to our servers and AI processing providers, including OpenAI and Anthropic, to prepare a response. Questions and answers are stored with a technical session identifier to improve the service; cached copies may also be retained to speed up responses. Do not submit personal or sensitive information you do not want processed. Separate operational records measure question counts, response time, token usage and outcomes using one-way identifier hashes. These metric records contain no raw identifier, IP address or email address and are deleted after 90 days. This 90-day period applies only to chatbot operational metrics, not conversation text or other analytics data. Clearing a conversation on your device does not automatically delete server records.
• Push Notifications (App): The app uses Firebase Cloud Messaging to deliver content notifications. The service processes app-installation identifiers and a push registration token to route messages to your app installation. These are technical identifiers, not your name or phone number. You can manage notification permission in your operating system settings.
• Notification Test Phones: If you choose to set up a test phone when the feature is available, we keep a technical record with its administrator-assigned name, platform and app version, notification-permission status, and setup, activity and approval times. The push token is stored encrypted, and pairing credentials are verified using hashes. Administrators can view device status and send-attempt results. Revocation invalidates test credentials and clears the record's secrets; device metadata and attempt records may remain for audit purposes. This is an optional setup, not automatic enrollment of all users.
• Analytics and Usage Data: The website uses Umami Analytics and Vercel Analytics to understand usage and improve performance. When app analytics is enabled, Google Analytics for Firebase (Firebase Analytics) processes an app-instance ID and data such as sessions, screen and feature interactions, app and operating-system versions, and technical device information. The service may derive approximate location from an IP address; this is not precise GPS location. Details vary by app version, platform and service settings. Depending on the version, device settings and permissions, identifiers may include an Android advertising ID or an iOS identifier for vendors. Aggregated reports do not mean that the underlying technical data is completely anonymous.
• Service Configuration and Technical Data: The app uses Firebase Remote Config and app-installation services to provide feature settings and compatibility. These services may process installation IDs, app and OS versions, language, time zone, country information and technical diagnostics. Request connection information, including IP addresses, also reaches hosting and service providers when you use connected features.
• Local Storage: The app stores settings and copies of favorites and cached content on your device. Local storage does not mean that connected features send no data: the descriptions in this policy also apply to those features.

Analytics Choices

In versions supporting the “Help improve the app” option, when the service is available, you can choose whether to participate in usage analytics in app Settings. Older app versions may not have this option and may handle automatic collection differently. Update the app to see the choices available in your version. Turning participation off applies to future collection controlled by that option; it does not automatically delete previously submitted data or stop data needed for features you choose to use, such as notifications, favorites and the AI assistant.

Cookies

The website uses the aq_uid cookie to associate favorites with a visitor identifier. Administrator sign-in functions may also use session cookies. You can manage cookies in your browser; deleting them may remove access to favorites associated with your identifier. Administrator accounts are separate from public-content use and use email addresses for sign-in verification and administrative audit records.

Processing by Service Providers

We use service providers for hosting, storage, notifications, analytics, search and processing AI-assistant requests. They process data needed for their functions under the relevant service settings, terms and privacy policies. These include Google/Firebase, Vercel, Supabase, Meilisearch and the AI providers named above. When you open links or media from external services, those services' policies also apply.

Retention and Your Requests

Retention varies by data type, purpose and service-provider settings. The 90-day period above applies only to chatbot operational metric records, not to all platform data or Google Analytics. You can contact us to ask about your data or request access, correction or deletion. We may need enough information to identify the relevant records and verify your request. Do not email passwords, pairing codes or secret credentials.

Data Security

We take reasonable security measures to protect data, including encrypted connections (HTTPS), input validation, and rate limiting.

Children's Privacy

We do not ask children to provide their names or contact details to read public content. The technical-data processing described in this policy still applies to app use. Parents and guardians should help children avoid submitting personal information through conversations or contact channels, and contact us with questions or requests concerning a child's data.

Changes to This Policy

We may update this policy from time to time. The last updated date will be noted at the top of this page.

Contact Us

When you contact us, we process the contact details and message content you choose to send so we can respond. For questions about this policy: AlQamar@hhfm.me