Privacy policy
Last updated 8 November 2026
We collect the account, site and billing data listed below to run the product. FireCert Clock is run by StyleLine FZE, a company registered in the Sharjah Research, Technology and Innovation Park (SRTIP) Free Zone, Sharjah, United Arab Emirates ("we", "us"). We also explain why we use it, who helps us, and the choices you have. Questions go to support@firecertclock.com.
What we collect
- Account details. Your email address and a hashed password. The password itself is never stored. If you sign in with Google, Microsoft or GitHub, we keep the address and provider id those services share with us.
- Sites and assets. Building names and addresses, asset types, locations, interval presets, last service dates and next due dates.
- Visit files. Service reports and inspection certificates you upload, plus extracted text we keep so we can show the file against that visit and attach it to a site PDF.
- Client contacts. Names and email addresses you add on a site so they can receive reminder emails.
- Technician details. Names, emails and calendar feed tokens used for iCal subscriptions.
- Alert destinations. Slack, Microsoft Teams and generic webhook URLs, and a webhook signing secret, if you add them.
- API keys. A hash of each key and its first characters so you can tell keys apart. We cannot show a key again after it is created.
- Team members and invites. 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 or store the full card number.
- Technical logs. Our hosting provider records request logs, including IP addresses, to keep the product running and secure.
AI date reading
On Starter and above, documents you upload for auto-fill are processed by third-party AI service providers acting as subprocessors, only to extract information for your account, including a suggested service date and next due date. You confirm those dates before they become the live record. The providers receive the document text for that request only. We ask that they not use the text to train their models. If the key is missing or the model fails, we still store the upload and you enter the dates by hand.
The free tools
Public lookup and generator pages do not store the buildings or units you type in. They return a result and keep nothing in your account. Hosting logs may still briefly record the request, as with any web page.
Why we use it
- To calculate due dates, send the reminders you set up, attach certificates to reports, and keep a visit history.
- To run your account, team and billing.
- To send service emails: reminders, client contact reminders you asked for, password resets, payment problems and, if you opt in, a monthly summary.
- To keep the product secure.
We do not sell this data and we do not use it to advertise.
Who helps us run FireCert Clock
- Vercel hosts the application and keeps request logs.
- Neon hosts application data.
- Stripe processes payments and stores your card details.
- Resend delivers our emails.
- Third-party AI service providers act as subprocessors. They process documents you upload for auto-fill, only to extract information for your account, when AI date reading is on and a key is configured.
- Your own integrations. Reminders you route to Slack, Microsoft Teams or your own webhook are sent to those services under their terms.
These providers may process data outside the UAE. We share only what each one needs to do its job.
Cookies
The only cookies we set are the ones the product needs: a session cookie that keeps you signed in, and a security cookie that protects forms against cross-site request forgery. No analytics or advertising cookies.
How long we keep data
- Account data, sites, assets, visits, uploaded files and settings are kept while your account is open.
- Deleting a site removes its assets, visits and uploaded files. Removing a key, invite or technician deletes it.
- Sessions expire after 14 days. Password reset links expire after use or after a short time.
- When you ask us to delete your account, we delete your account data within 30 days. We keep billing records that tax and accounting law require us to keep.
- Hosting logs are kept for the period set by our hosting provider.
Client contacts
If you receive reminder emails because a contractor or building manager added your address, you can ask them to remove it, or email support@firecertclock.com from that address and we will take it off the site.
Your choices and rights
You can view and change most of your data in the app, export assets as CSV on Business, and remove sites, files, keys and integrations at any time. To get a copy of your data, correct it, or delete your account, email support@firecertclock.com from your account address. We reply within 30 days.
Security
All traffic uses HTTPS. Passwords and API keys are stored as hashes. Fetches of user-supplied URLs refuse private and internal network addresses. No system is perfectly secure, so if you find a problem, please tell us at support@firecertclock.com.
Children
FireCert Clock is a business product and is not meant for anyone under 18. We do not knowingly collect data from children.
Changes
We update this policy when our practices change and change the date at the top. If a change is significant, we will email account owners before it takes effect.
Contact
StyleLine FZE, Sharjah Research, Technology and Innovation Park (SRTIP) Free Zone, Sharjah, United Arab Emirates. Email support@firecertclock.com.
FireCert Clock counts marketing page visits without cookies and stores no IP addresses.
When you create a FireCert 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.