Legal

Privacy Policy

Last updated:

This policy explains what data we collect, how we use it, and your rights over it.

What we collect

  • Account data: name and email address. If you choose Google sign-in, we also receive your Google account identifier and email-verification status, and may receive your organization domain to assess email verification.
  • If you sign in with GitHub, we receive your account identifier, username, name and available email address. Repository permissions you grant to read, build and deploy projects are separate from your sign-in identity.
  • Usage, build and deploy logs needed to operate the Service and support you.
  • Billing data via an external payment processor — we do not store card numbers.

How we use it

We use data to operate the Service, provide support, bill you, improve the platform, and send notices about your service. We do not sell your data, and we do not use it for advertising.

We use Google data to create a Nashir account or link Google to an existing account after verifying ownership, to sign you in, and to verify your identity for security actions. We request only openid, email and profile; we do not request access to Gmail, Google Drive or Calendar, and we do not retain a Google refresh token for access to Google services.

Cookies

This marketing site sets no tracking cookies. The dashboard uses essential session cookies for signing in, nothing more.

Where your data is processed

Your applications and managed databases run in the region you choose — Riyadh or London today. With your own servers (BYOS), your application data stays entirely on your infrastructure. Details are in the Data Processing & Residency statement.

Your Nashir account details and linked Google sign-in identity are stored in Nashir's account-management systems. Hosting your applications on your own server does not move your Nashir account data to that server.

Your rights

You can access, correct, delete and export your data, including data received from Google. Send requests or privacy questions to [email protected]. We will act on your request in line with Saudi Arabia's Personal Data Protection Law (PDPL).

You can remove Google from Login methods in Nashir settings once another sign-in method is available, or revoke Nashir's authorization in your Google Account settings. Removing a sign-in method or revoking authorization does not delete your Nashir account or its data; request deletion using the email address above.

Retention

We keep account data, including data received from Google, for the life of the account and as required by law. You can request deletion of your account and its data at [email protected]. On account deletion, its data is removed from our managed systems within a reasonable period, except where retention is legally required.

Security

Data, including Google sign-in data, is encrypted in transit over TLS, and internal access is governed by permission controls. Google authenticates your Google identity; Nashir does not ask for or store your Google password.

Subprocessors

We use infrastructure, payment and email providers to the extent needed to run the Service, under data-protection obligations to us. Infrastructure providers may process account data received from Google to store it and operate authentication, and our email provider processes the account email address to deliver service messages. We do not sell Google data or share it for advertising.

Age of use

The Service is built for developers and teams and is not directed at anyone under 18.

Changes to this policy

We may update this policy and will notify you of material changes before they take effect.

Questions about this page: [email protected]