Privacy policy

Last updated 7 October 2026.

OurPulse lets a person (the owner) ask a group of people (the respondents) a few questions, and shows the answers as a whole. This page says what the service stores, why, for how long, who else touches it, and how to ask about it. It is written to match what the software actually does.

Who is responsible

OurPulse at ourpulse.click is run by Niki Dimitrov, a private individual in Bulgaria. For anything on this page, write to [email protected].

For the questions an owner asks and the answers they collect, the owner decides what is asked and who gets the links; OurPulse processes that data on the owner's behalf. For owner accounts and the running of the service, OurPulse is the controller.

Owners

To create pulses you sign in with Google. OurPulse stores:

• Your Google account identifier and email address, to recognise you on the next sign-in and to show which account you are using. Nothing else from your Google account; the sign-in asks only for openid and email.
• The pulses you create (title, questions, open and close times, settings), their answers, any report you push, webhook URLs you register, and API keys you create. Keys are stored as a hash; the key itself is shown once.
• A log of what you did in the app: that you signed in, created a pulse, asked for a draft, opened results, pushed a report or made an API key, with the time and whether it came from the browser, the API or the command line. It has no page views, no IP address and nothing about respondents. It is used only to see whether OurPulse is being used and how. When you delete your account the entries lose their link to you and only the counts remain.
• When you use the "Describe it, get a draft" card, the text you typed or dictated, your time zone and local time are sent to the AI model (see Who else processes data) and are not stored by OurPulse. Speech is recognised by your browser or device; no audio reaches OurPulse.

Respondents

You do not need an account to answer. What is stored depends on how the owner set up the pulse.

Pulses open to anyone with the link

• No sign-in. A cookie set for that one pulse marks your browser as having answered, so the same browser cannot answer twice. It holds a random value, not your identity.
• Your answers are stored with a two-word pseudonym chosen at random, or with whatever name you typed over it. If you type your real name, it is stored with your answers and shown to the owner.
• OurPulse cannot otherwise tell who answered. The owner sees the pseudonym or typed name, the answers and the time.

Pulses that require Google sign-in

• You sign in with Google so that each person can answer once. OurPulse keeps a one-way token derived from the pulse and your Google account; it blocks a second answer and cannot be reversed into your account, and it is never stored together with your answers.
• Your answers are stored without your name, unless the owner made the pulse named. The owner is told whether a pulse is named when they create it, and the answer form says so.
• If you also own pulses, the same session cookie is used.

Free-text answers

Whatever you type into a text question is stored as is. If you write something that identifies you or another person, it is kept with the answers and shown to the owner and to anyone the owner shares the results or report link with.

Cookies

Cookie	Who	Purpose	Lifetime
Session	Owners, and respondents on sign-in pulses	Keeps you signed in.	30 days
Sign-in state	Anyone signing in	Protects the Google sign-in round-trip.	10 minutes
One per pulse	Respondents on open pulses	Blocks a second answer from the same browser.	1 year

Every cookie is needed for the service to work; none is used for analytics, advertising or tracking across sites, and no third-party cookies are set. That is why there is no cookie banner.

Your browser's local storage keeps small preferences such as the speech language you picked. It never leaves your browser.

What OurPulse does not do

• No advertising, no tracking pixels, no fingerprinting. The app pages (pulses, results, your account) load no analytics script; usage is counted from the log above and the answers themselves, inside the database. The public landing site (this page, the home page and the terms) loads Cloudflare Web Analytics, a cookieless page-view counter that keeps no IP address and does not follow you across sites.
• No selling or sharing of data with anyone for their own purposes.
• No profiling or automated decisions about you.
• Your IP address is not stored in the database. Cloudflare keeps short-lived request logs for operating and securing the service; see below.

Who else processes data

OurPulse runs on services provided by other companies. Each acts on OurPulse's instructions and sees only what is needed for its part.

Provider	What for	What it sees
Cloudflare, Inc.	Runs the application and the database; counts page views on the landing site; routes mail to [email protected].	Everything stored above, plus request logs (IP address, URL, time) kept briefly for security and debugging, and aggregate page-view counts for the landing site. The database lives in Cloudflare's network, which has data centres inside and outside the European Union.
Google LLC	Sign-in with Google.	That you signed in to OurPulse, under Google's own privacy policy. Nothing else on the pages loads from Google; the fonts are served from ourpulse.click.
OpenRouter, Inc. and the model provider it routes to	Turning an owner's description into a draft pulse.	The owner's description text, time zone and local time, for the duration of the request. OurPulse asks OpenRouter not to use it for training; the model provider's own terms apply.
GitHub, Inc.	Serves this website (the pages at ourpulse.click other than the app itself).	Request logs, under GitHub's privacy statement.

Some of these companies are outside the European Economic Area. Transfers rely on the EU–US Data Privacy Framework where the company is certified, and otherwise on the European Commission's standard contractual clauses in the providers' terms.

How long data is kept

• A pulse and all its answers are kept until the owner deletes the pulse. Owners can also reset a pulse, which deletes every answer and keeps the questions.
• An owner account, with every pulse, answer, report, webhook and API key under it, is deleted when the owner presses Delete my account. There is no automatic expiry of closed pulses.
• Sign-in requests from the command-line login expire after 10 minutes and are removed.
• Database backups are kept by Cloudflare for up to 30 days.

Your rights

Under the GDPR you can ask to see the data held about you, to have it corrected or deleted, to restrict or object to its processing, and to receive it in a portable form. You can also complain to a supervisory authority; in Bulgaria that is the Commission for Personal Data Protection (cpdp.bg).

If you are an owner

• You can export each pulse as CSV, delete a pulse, reset its answers, and revoke API keys from your account pages.
• To delete your account and everything under it, open Account from the menu in the top right and press Delete my account. It takes effect at once.

If you are a respondent

Because of how answers are stored, OurPulse usually cannot find yours:

• On an open pulse, your answer carries only a pseudonym, unless you typed your name.
• On a Google sign-in pulse, the one-way token cannot be turned back into your account, so OurPulse cannot tell which answer is yours, unless the pulse is named.

The practical route is to ask the owner who sent you the link; they can remove a single response from their results page, by name on a named or open pulse, or by the time you answered on an anonymous one. If you do not know who the owner is, or they do not answer, write to [email protected] with the pulse link and we will contact the owner or remove what can be identified.

Security

All traffic is over HTTPS. API keys are stored hashed. Pushed reports are served from a page that cannot run scripts or load outside resources. The one-way token for sign-in pulses is written in the same database transaction as the answer and is never joined to it.

Children

OurPulse is not aimed at children under 16. If you believe a child's data ended up in a pulse, write to the address above.

Changes

When this page changes, the date at the top changes and the previous version stays in the site's history on GitHub. A change that matters to owners is announced on their account page.

Home Terms of service [email protected]