Back to Weaze

Privacy policy

Last updated 26 October 2026

The Weaze team operates weaze.app. This policy explains how we handle information for accounts and product previews on the Weaze website and mobile app.

Information we handle

  • Account information: your name, email address, email verification status, and account creation and update dates.
  • Google sign-in information, if you choose it: your Google account identifier, name, email address, verification status, and profile picture URL if Google provides one. We also store authentication tokens associated with the connection.
  • Apple sign-in information, when available and chosen: your Apple account identifier, email address (including a private relay address if you choose one), verification status, and name if Apple provides it. Provider credentials stay on our server.
  • Sign-in and security information: session identifiers, necessary cookies, IP address, browser user agent, sign-in timestamps, and records used to limit abusive requests.
  • Location information: address searches, selected places, and coordinates you deliberately pinpoint on a map. Device location in the browser or mobile app is requested only if you choose “Use my location” and grant permission. The mobile app uses a one-time foreground position to help place your pin; it does not track your location in the background.
  • Support messages: the information you choose to send when you contact the Weaze team.

How we use it

We use account and sign-in information to create and manage your account, verify your identity, keep you signed in, send verification codes, prevent abuse, and respond to support requests.

We use Google account information only for sign-in, account management, security, and account support. We do not sell it, use it for advertising, or use it to train AI models. We request only basic identity, email, and profile access, without access to your Gmail messages, Google Drive files, contacts, or calendar.

Services that process information

Cloudflare hosts the website, its assets, and our account service. Account and session records are stored in Cloudflare D1. Cloudflare also processes verification email delivery, website requests, security information, and performance analytics for us.

Cloudflare operates a global network. The production account database is currently located in Europe, and our service providers may process information outside Nigeria.

When you choose Google sign-in, Google processes the authentication request and provides the identity information described above. Google is an identity provider for Weaze; it is not used to access your other Google content.

Google Maps processes address searches, selected places, and coordinates you explicitly choose or share from your browser or mobile device to provide address suggestions, identify a selected pin’s nearby address, and display maps. These requests pass through Cloudflare where applicable. Map loading sends requests to Google from your browser or the native Maps SDK in the mobile app. We do not store searches or coordinates in your account or delivery records.

If you use Apple sign-in when enabled, Apple processes that authentication request and may provide a private relay email address rather than your usual address.

The Weaze team uses this information to operate the website and mobile app, protect accounts, and handle support and privacy requests.

Cookies and account security

Necessary session cookies keep you signed in. Logging out ends your current session. You can also remove cookies through your browser settings, which may sign you out.

The mobile app stores its session token and basic account details in iOS Keychain or Android secure storage so it can restore your account. Native sessions last up to seven days unless renewed or revoked. Social sign-in returns only a short-lived, single-use exchange code to the app; your session token is not placed in the redirect URL.

Sign-in codes are stored as hashes, and our application does not log the plain verification code. Google access and refresh tokens are encrypted before storage. We use secure connections and restricted account endpoints to protect sign-in information.

Website analytics and previews

We use Cloudflare Web Analytics to understand page visits and loading performance. These analytics are separate from your Weaze account and are not used to identify you for advertising.

Delivery demos run in your browser. Their form choices and simulated progress are held in page memory and reset when you refresh. They do not create real delivery bookings or take payments. Mobile delivery plans and selected pins are also held only in app memory. When you confirm a pin, we may look up its nearby address without changing the exact point you selected. Your shared website and mobile account is stored separately from these previews.

Retention and your requests

We retain your account information until you request its deletion. Expired sessions, verification codes, and old rate-limit records are cleaned up periodically.

To request access to, correction of, or deletion of your account information, contact saeed@onsell.ai. We may need to verify that the request is from the account holder before making changes.

You can also remove the Weaze connection from your Google Account settings. Removing that connection does not by itself delete your Weaze account; contact us if you want the account deleted.

Questions and updates

For privacy questions, contact the Weaze team at saeed@onsell.ai. We will update this page when the website’s data practices change and show the updated date above.