Privacy policy
Ahem keeps the events your apps send so you can read and search them, and keeps as little about you as it needs to run your account. We never sell data, show ads, or train AI models on what you send.
Who is responsible
Ahem (useahem.com, app.useahem.com and the Ahem apps) is operated by Bohdan Stefaniuk, a sole proprietor based in Ontario, Canada (“we”, “us”). For anything about privacy, email support@useahem.com.
The short version
- We collect what we need to run your account and deliver your events: your email, the data your apps send, and a little technical data.
- The events you send are yours. We store them to show them to you and the people you share a project with, and for nothing else.
- We never sell your data, never use it for advertising, and never use it to train machine-learning models. Treat that as permanent.
- Ahem runs on servers in Toronto, Canada.
- You can export a project at any time, delete what you sent, and ask us to delete your account.
What we collect
About you, the account holder
- Account: your email address and, if you give one or sign in with Google, GitHub or Apple, your name and that provider’s account identifier. We never see your password for those providers.
- Your workspace: projects, channels, counters, funnels, notification rules, project pictures you upload, and who you share projects with.
- Sign-in and devices: sessions (stored as a hash of the token, with a short device label taken from your browser or phone), and push tokens for the browsers and phones you turn notifications on for.
- Billing: your plan, your Stripe customer and subscription identifiers and their status. Card details go straight to Stripe; they never reach our servers.
- Messages you send us: emails and contact-form messages, so we can reply.
- Technical data: when you use Ahem, our servers see your IP address and browser details. We use the IP address to limit abuse (it is held in memory for a minute or so, not stored with your account). Error reports and server logs record what went wrong and where, not the content of your events.
What your apps send
Events: their title, body, level, type, channel, tags, links, metadata, and the person an event is about if you include one. API keys are stored only as hashes; we show a key once, when it is created.
What we don’t collect
We don’t ask for your location, contacts, photos, microphone or camera, and the phone apps contain no advertising or tracking SDKs.
Data you send about your users
Your events can contain personal data about the people who use your apps: an id, a name, an email address, details such as their plan, and whatever you put in an event. For that data, you are the controller and we are your processor: we store and show it only to deliver Ahem to you, on your instructions, and we don’t use it for anything of our own.
You are responsible for having a lawful basis to send it and for telling your users about it in your own privacy notice. Send only what you need: an internal id instead of an email works perfectly well. Don’t send sensitive data (see the acceptable use rules). You can erase a person and every event about them at any time, in the app or with the API.
If you need a data processing agreement, write to support@useahem.com.
How we use it, and why we may
| What we do | Legal basis (GDPR) |
|---|---|
| Run your account, store and show your events, send the notifications you asked for, sign you in | Performing our contract with you |
| Take payments and keep billing records | Contract; legal obligation for tax records |
| Send service emails: sign-in links and codes, receipts, important changes to Ahem or your account | Contract |
| Keep Ahem secure and working: rate limits, abuse prevention, error reports, backups | Our legitimate interest in running a reliable, safe service |
| Understand which pages and features people use, and which channels bring visitors | Our legitimate interest in improving Ahem |
| Answer your messages | Our legitimate interest in helping you; contract when it’s about your account |
| Respond to lawful requests from authorities | Legal obligation |
We send no marketing emails. We don’t make decisions about you based only on automated processing.
We do not sell your data
Your personal data and your events are not sold, rented or traded to anyone, and they are not used for advertising. We will never train machine-learning models on your events, and we will never sell them. Treat that as permanent. The only things we may share publicly are aggregate counts that identify no one, such as “Ahem stored a million events this month”.
Where your data lives, and who helps us
Your account and your events are stored in Canada. A few companies help us run Ahem; each gets only what its job needs:
| Provider | What it does |
|---|---|
| DigitalOcean | Hosts our servers, database, backups and uploaded project pictures, in Toronto, Canada. |
| Cloudflare | Delivers the website and web app, passes contact-form messages to us, and protects against attacks. It doesn’t store your events. |
| Stripe | Payments. Receives your email to create a customer record. Card details go only to Stripe. |
| Resend | Sends sign-in and service emails. |
| Better Stack | Error reports and server logs, without the content of your events. |
| Apple, Google, and browser push services | Deliver notifications to your phone or browser. A notification’s title and short text pass through them. Browser notifications are encrypted for your browser. |
| Google, GitHub, Apple | Only if you choose to sign in with them. |
| DataFast | Privacy-friendly analytics on useahem.com and the web app: pages visited, where visitors came from, and which visits led to a purchase. |
We also use Ahem itself to tell us about our own business: when someone signs up, buys or cancels, a payment fails, or a contact-form message arrives, we receive an event with the email address and account id involved. Those events are stored in Ahem like any customer’s, in Canada, and deleted with your account.
International transfers
The European Commission recognises Canada as providing an adequate level of data protection, so data stored with us in Canada needs no extra safeguards. Some providers above (Stripe, Resend, Better Stack, DataFast, Cloudflare) process data in the United States or elsewhere; where that happens, they are covered by the Standard Contractual Clauses or the EU-US Data Privacy Framework.
Cookies and analytics
We use no advertising cookies and no ad networks. There are two kinds of cookies:
- Sign-in: a cookie that keeps you signed in to the web app. Ahem can’t work without it.
- Analytics: DataFast sets two first-party cookies (
datafast_visitor_idanddatafast_session_id) to count visits and tell which marketing brought them. When you buy a plan, these ids are attached to the Stripe payment so we can see which channel led to it. They don’t follow you to other websites.
You can block or delete cookies in your browser; Ahem keeps working without the analytics ones.
How long we keep things
- Events: for as long as your plan keeps history: 7 days on Free, one year on Maker. Older events are deleted, not hidden. Moving to a plan with shorter history deletes the older events, so export first if you need them.
- Your account and workspace: while your account exists. Deleting events, people, channels or projects removes them at once.
- Sessions: a browser session ends 90 days after you last used it, a phone’s after two years. Ended sessions and used or expired sign-in links and codes (which last 15 minutes) are deleted within about a week.
- Backups: daily database backups are kept for seven days, then overwritten.
- Logs and error reports: kept for a limited time, then deleted automatically.
- Billing records: kept as long as tax law requires, even after an account is deleted.
To delete your whole account, email support@useahem.com from the address you sign in with. We delete it, with your projects and events, within 30 days, and it leaves the backups within seven days after that.
Security
Everything travels over HTTPS. API keys, session tokens and sign-in links are stored only as hashes, so even we can’t read them back. Sign-in and the API are rate-limited, and access to production is limited to the operator over a private network. No system is perfect; if we ever become aware of a breach that affects you, we’ll let you know as the law requires.
Children
Ahem is a tool for developers and isn’t meant for children. We don’t knowingly collect personal data from anyone under 13.
Your rights
Depending on where you live, you can ask to access, correct, export or delete your personal data, to object to or restrict how we use it, and to withdraw consent where we rely on it. Much of this you can do yourself: edit your details in Settings, export any project as JSON, and delete events, people, channels and projects. For anything else, emailsupport@useahem.com and we’ll respond within 30 days, or sooner if we can.
If you are one of our customers’ users and your data reached us through their app, please contact them first: they decide what is sent. We will help them answer you.
If you’re in the EEA, the UK or Switzerland, you can also complain to your local data protection authority.
California residents
The California Consumer Privacy Act gives you the right to know what personal information we collect and why, to delete it, to correct it, and not to be treated differently for using these rights. The categories we collect are in What we collect. We do not sell or share your personal information for cross-context behavioural advertising.
If Ahem changes hands
If Ahem is sold or merged, your data would move to the new owner under this policy. We’ll tell you before that happens, so you can export your data or delete your account first.
Changes to this policy
When we change this policy, we’ll update the date at the top. If changes are significant, we’ll notify you by email or in the product.
Contact
Bohdan Stefaniuk, Ontario, Canada · support@useahem.com · contact form