CKB Pulse
Share
Privacy

What Pulse keeps

What Pulse shows, what it counts about visitors, what stays on your device, and how to leave.

What Pulse shows

Public activity on GitHub: the GitHub name and picture of people who did something public in a project Pulse follows, and what they did. Nothing from private repositories.

Visits

Visits are counted per day, with no cookies and no accounts. A visitor is a code made from the day's secret, the address and the browser. The secret is thrown away when the day ends, so nobody can be recognised later. Counts are kept for 90 days. Monitors, crawlers and link previews are counted apart.

What was used

Which share button was used, and which kind of card was drawn, are counted per day as plain numbers. Nothing says who pressed them.

On your device

Your browser keeps, on your device only: the language, that you saw the welcome card (the welcome page is then skipped), the look you chose, dark or light, the projects and people you follow, and your notice settings. Clear the site's data in your browser to remove them.

Notices

If you turn on notices, your browser gives the server an address to send them to. It is kept until you turn notices off, and used only to tell you about the projects you follow.

The long history

Commits per month and who made a first commit come from GitHub's public statistics, kept as counts per person and week.

Leaving

If you are in Pulse and do not want to be, write to hello@lusocryptolabs.com or open an issue with your GitHub name. It goes on a list that makes Pulse drop everything of yours when it comes in, and take it out of what is stored, the history, the lists, the cards and the feeds. It can take a few days to go live. The activity stays public on GitHub itself.

Nothing sold

Nothing is sold, there are no ads and no outside trackers. The fonts and the scripts are served by Pulse itself.

Questions

hello@lusocryptolabs.com

Write to us