Your register is your business.
Who operates this service
Aidan Maguire · Founder & CEO
Aidan Maguire trading as CertKeep (sole trader) 48 Rossmore Drive, Belfast, BT7 3LA, United Kingdom
What is stored
Certkeep stores the person names, team names, course details, dates and references you enter, along with record identifiers, update times and the identifier of the account that owns them. We also record the terms version, account identifier and time of your explicit acceptance to keep a record of the service agreement. We receive your account identifier and email through ChatGPT sign-in. If you use paid billing, we store a Stripe customer identifier. Payment card details are handled by Stripe and are not stored in the register. Stripe’s billing portal lets you update billing name, email, address and phone details. It currently also offers shipping and tax-ID fields; CertKeep does not need these for the training register, and you should leave them blank unless genuinely required for your billing circumstances. Those optional billing fields are not copied into CertKeep’s database.
How it is used
Records are used to show your register, calculate expiry statuses and produce exports. Your account identifier separates your records from other accounts. Email may be supplied to Stripe to create your billing account. This version does not send marketing or renewal emails and uses optional, consent-based daily page counts without visitor identifiers. It does not use advertising trackers. Counts are not unique visitor numbers and may include repeat visits.
Service providers and access
Hosting and authentication are provided through Sites and ChatGPT; structured application data is stored using Cloudflare D1. Stripe handles payments when enabled. Authorised service operators and infrastructure providers may access data to run, maintain or troubleshoot the service. The operator must confirm applicable processing arrangements and retention policies before commercial launch.
Control over your data
You can export all your records as CSV, edit them or delete individual records. Cancelling a subscription does not delete records. They remain available in your account unless you delete them. Contact the operator for account-level deletion and billing-record queries. Infrastructure backups or provider billing records may remain subject to their retention arrangements.
Cookies and analytics choices
Sign-in uses essential cookies. A local preference remembers your analytics choice. Optional counts store only a date, approved page path and total, retained for up to 90 days with cleanup on the next counted visit. No IP address, user agent or referring URL is stored in these counts. Hosting providers may retain separate operational logs. Do Not Track and Global Privacy Control disable these optional counts. Use Cookie preferences at the bottom of any page to change your choice.
Billing events
To prevent duplicate checkout requests, we retain one checkout-attempt entry per account: the chosen price, random request key, creation time and temporary processing lock. We retain Stripe event identifiers, event types and receipt times for up to 30 days, with cleanup when the next event arrives. We do not store webhook payloads or card data.
Use only necessary information
You may use initials or an internal staff identifier instead of a full name. Team and reference fields are optional. Do not enter medical information, identity documents, passwords or other sensitive details. Store a certificate reference rather than the certificate document. Use the service only for records you are authorised to manage.