Merchant Clock

What we keep

  • Your account. Your email address, your name if your sign-in provider shares it, and either a hashed password or the Google, Microsoft or GitHub account you sign in with. We never store a password itself.
  • Your stores. The store URLs and feed URLs you add, and the result of each scan: the score, the checks that failed and the fixes we suggested.
  • Report header. On Agency, the agency name, colour and logo you add for PDF reports.
  • Alert settings. Extra email recipients, Slack and Microsoft Teams webhook URLs, and your own webhook URL and its signing secret.
  • API keys. A hash of each key and its first characters, so you can tell keys apart.
  • Team members. The email addresses you invite and their role.
  • Billing. Your plan, subscription status, renewal date, and the card brand, last four digits and expiry date that Stripe shares with us. We never see the full card number.
  • Request logs. Our hosting provider records request logs, including IP addresses, to keep the service running and secure.

The free scan on our homepage

When you scan a store without an account, we show you the result and do not save it. Our hosting provider's request logs may still briefly record the request.

Why we use it

To scan your stores and send the alerts, digests and reports you ask for, to run your account, team and billing, to answer support email, and to keep the service secure. We do not sell your data and we do not use it for advertising.

Who helps us run Merchant Clock

  • Vercel hosts the application and keeps request logs.
  • Neon stores your account and scan data.
  • Stripe processes payments and stores your card details.
  • Resend sends alerts, digests and account email.
  • Your own integrations. Alerts you route to Slack, Microsoft Teams or your own webhook go to those services under their terms.

These providers may process data outside the UAE. Each one gets only what it needs to do its job.

Cookies

Only the cookies the service needs: a session cookie that keeps you signed in and a security cookie that protects forms. No advertising cookies.

How long we keep it

Your account, stores and scan history stay while your account is open. When you ask us to delete your account, we delete your data within 30 days, apart from billing records that tax and accounting law make us keep.

Your rights

To get a copy of your data, correct it or delete your account, email support@merchantclock.com from your account address. We reply within 30 days.

Changes

When our practices change we update this notice and the date at the top. For a significant change we email account owners first.

Contact

StyleLine FZE, Sharjah Research, Technology and Innovation Park (SRTIP) Free Zone, Sharjah, United Arab Emirates. Email support@merchantclock.com.

Merchant Clock counts marketing page visits without cookies and stores no IP addresses.

When you create a Merchant Clock account we store the first page you opened, the document referrer host (if any), and standard UTM campaign tags from that visit in a first-party cookie until you sign up. We classify that into a channel (for example Google, direct, or unknown) using the same rules as our cookieless visit counts. We do not store your IP address for this.