Account Terms and Privacy

Version 2026-10-10-registration-v1, dated 10 October 2026. These terms cover account creation, operation and privacy requests. They do not replace the record of your earlier private-preview consent.

Registration Scope

Registration creates an account only. It does not enable early Q4 2026 forecast entry or publicly publish your profile, display name, biography or forecasts. Round participation and profile or forecast publication require separate availability and the participation terms shown then; account creation is not consent to publish them.

An account requires an email address, display name and password. Email supports verification, sign-in and recovery; the display name identifies your account and may be a pseudonym. Your email is not public. An optional biography and public social account are not required for registration. Read the account terms and privacy notice before accepting them and submitting the signup form.

Keep your password, verification codes and follow-up codes private. Do not impersonate others, misuse the service or access their data. Email verification does not verify identity or professional qualifications. An account provides neither professional accreditation nor an investment service.

Data and Its Uses

We receive data you provide when registering, updating your account and sending requests: email, display name, optional biography and public social account, and request content. We also record session data, login attempts and security indicators such as network address and time, acceptance of a terms version and account actions, to operate and protect accounts, prevent abuse and handle your requests.

We process necessary account data to provide the service you request under the account terms, security data to protect the service, and optional data for the purposes for which you choose to provide it. You may leave optional fields blank or request their correction or removal. Without email, display name and password we cannot create an account; omitting a biography or public social account does not prevent registration.

Your password is sent to the authentication service for verification and is not included in account exports. Application sessions are managed server-side; provider authentication tokens are not delivered to application-interface JavaScript. The initiative does not request identity-document numbers, home addresses or payment details. Do not include passwords, verification codes, identity documents or sensitive data in biographies or requests.

Controller and Service Providers

The initiative's data controller is Abdullah Albudairy (عبدالله البديري), and the service operates as Arraf Management. Contact us through Profile, then Account and privacy requests, or the support page if you cannot sign in. We do not publish a personal email address or telephone number for contact.

The service uses Vercel for hosting, Supabase for its database and authentication, and Resend for verification and recovery emails. The current database, authentication and application functions are in Seoul, South Korea. Email processing is primarily in the United States; operational processing or support access may occur outside Seoul, including the United States, Singapore and the EU. Vercel delivers the service through a global network. An existing private encrypted backup is held with Google Drive; we do not promise Saudi-only storage for it. Seoul selection does not mean all processing or copies are confined there.

Service providers use data needed for authentication, hosting, email delivery, protection, operation and backup. Account data and privacy requests are not public pages; the account owner, management and providers access them according to operational need. Registration does not create a public profile or publish your email or request content.

Retention and Cleanup

Active-database cleanup is enabled, with hourly batch scheduling. An unconfirmed account becomes eligible after seven days from creation if it has never been used to sign in and has no data or dependencies blocking deletion; security records after 30 days from recording; closed ordinary support after 30 days from documented closure; and closed rights requests and minimal execution receipts after 90 days, once the request is closed, related execution is terminal and the interval has passed since the last relevant action.

Batches are bounded, so these intervals do not mean immediate deletion when the period ends. Protected records, unfinished requests or plans, and unsupported or oversized dependencies remain for review. This cleanup does not delete an active verified account, frozen forecasts or financial history. Registration audit records and security records not directly linked to a closure request may remain; the action result identifies what was removed and what remains.

These intervals apply to eligible active-database data. This workflow does not purge provider logs, backups, older Google Drive versions or exports already downloaded. Deleting an active account does not confirm destruction of every copy; external records and copies require separate follow-up by Arraf Management.

Access, Correction and Closure Requests

You may request information about your data, access, a copy, correction and destruction, and withdraw consent where it is the processing basis. Submit your request under Account and privacy requests. A reference and status are shown; administrative request closure does not prove data delivery or account deletion. Management reviews the request and explains the action result or remaining follow-up. A support message alone does not authorize account changes or release of account data.

For a copy, choose an access or copy request, then Download my account data. Fresh owner sign-in is required; you may need to sign in again after five minutes. The private download contains your registration, account and linked request data within the supported scope. It excludes passwords, session tokens, other people's data, protected financial history, support conversations not linked to verified ownership, provider logs and backups. Preparing an export does not prove that your device received it.

To close an account, choose a closure request and confirm it after fresh sign-in. Confirmation does not immediately delete the account. Management reviews and executes the plan with appropriate authorization before the short-lived confirmation expires; renewed confirmation may be needed. The automated path is for registration-only accounts: it revokes application and authentication sessions and removes covered active account data, retaining a minimal receipt without the erased content.

If immutable financial history, protected data or unsupported dependencies exist, automatic deletion does not proceed and management reviews the reason and available handling. This is a technical result, not a final determination of your rights. The receipt distinguishes active-data removal from outstanding provider-log and backup follow-up; it does not promise their complete destruction.

If you cannot sign in, the support page provides a receipt and private follow-up code for that conversation only. They neither verify account ownership nor grant access to account data. Follow-up expires 30 days after conversation creation, not after the last reply; expiry does not delete messages. Keep the receipt and code, and do not rely on the conversation alone to exercise account rights requiring owner verification. Complaints may be submitted to the competent personal-data protection authority.

Terms Updates

The required terms version is shown at registration, and your acceptance is recorded against that version. Earlier acceptances retain their original versions; private-preview consent is not automatically converted into acceptance of this version. Later participation or publication will present its relevant terms separately.