Privacy
This page tells you what AwesomeRepos records when you use the site. It describes what the code does today. When the code changes what it records, this page changes in the same update. Last change: 1 November 2026.
What AwesomeRepos does not record
- AwesomeRepos sets no cookie for a Visitor. A Visitor is a person who is not signed in. The site sets a cookie only when you sign in. See Accounts.
- For a Visitor, the database keeps no IP address and no user agent. The user agent is the name and version of your browser.
- The pages load no script, font, or image from a different site. All files come from awesomerepos.com.
- AwesomeRepos sends none of its records to a different company. Cloudflare carries each request between your browser and our server. As for each website, Cloudflare and the proxies in front of our server can see your IP address.
- To stop abuse, the server counts requests in its memory for a short time. The sign-in limits use the IP address. The server does not write these counts to the database, and a restart deletes them.
Page views
When a page opens, a small script on the page sends one message to our server. The server keeps:
- the path of the page, without the part after “?”
- the name of the site that sent you to the page, if it is a different site
- the value of
utm_sourceorrefin the address, if there is one - the time
- if you are a Visitor, a Member, or an Operator
- the value of the return marker (see below)
- a daily code
The server calculates the daily code from three items: a random value for the day, your IP address, and your user agent. It keeps only the code, not the three items. Each UTC day gets a new random value. After the day ends, the server deletes the random value of that day. Thus, nobody can connect your visits on two different days. Also, nobody can calculate the code again from an IP address. When you are signed in, the code comes from the random value and your account ID.
Why: to count the people and the pages each day, and to find which pages help people. The server does not record page views from a browser that says it is a bot or a crawler.
The return marker
Your browser keeps one value in its local storage. The name of the value isawesomerepos:last-visit-week. The value is the date of the Monday of the UTC week of your last visit, for example 2026-10-26. It is not a cookie, and it does not identify you. Your browser does not send it with each request.
On your first page view in a week, the script compares the value with the current week. Then it sends “new” or “returning” with that page view, and it writes the current week. On other page views it sends nothing about the marker.
Why: the number of people who come back each week is the main measure of AwesomeRepos.
To remove the return marker:
- Open the settings of your browser and delete the site data for awesomerepos.com. This also deletes your theme choice.
- Or use a private window. The browser deletes the marker when you close the window.
If you remove the marker, your next visit counts as “new”. If your browser blocks local storage, the script sends no marker.
Other data in your browser
awesomerepos-themein local storage keeps your choice of the light or the dark theme. It stays in your browser.- Session storage keeps, for a short time, the text that you type in a search field while the next page opens, and one note for Saved Views. The browser deletes session storage when you close the tab.
Events
The server records these events, with the page, the time, and the daily code:
- a click on a link to github.com, with the GitHub path of the link
- a new Bookmark or a new Saved View
- a new account
Why: to know which parts of the site people use.
Errors
When a page or the server has an error, AwesomeRepos keeps the path of the page, the error message, the location of the error in the code, and the time. In the browser, the script ignores errors from the scripts of other sites, and it sends at most 5 errors for each page. Errors do not have a daily code.
Why: to find and repair problems.
Feedback
When you send “Report a problem” or the feedback form, AwesomeRepos keeps your message, the page, the time, and if you are a Visitor, a Member, or an Operator. For “Report a problem”, it also keeps the repository. When you are signed in, it also keeps your account ID. Do not write personal data in the message.
Why: to read each message and act on it.
Accounts
When you make an account, AwesomeRepos keeps:
- your name and your email address
- a hash of your password, not the password
- the type of account (Member or Operator) and the time that you made it
- your Bookmarks and your Saved Views
- each UTC day on which you opened a page while you were signed in
When you sign in, the site sets a session cookie. The cookie keeps you signed in. The database keeps a record of the session, with the IP address and the user agent of the browser that signed in. A session ends when you sign out, or about 7 days after you last use the site. When you sign out, the server deletes the session record. AwesomeRepos does not yet delete old session records on a schedule.
Why: to keep you signed in, to keep your Bookmarks and Saved Views on each device, and to count the Members who come back.
There is no button to delete an account yet. To ask for deletion, use thefeedback form and write the email address of the account.
Search data from Google
When Google Search Console is connected, AwesomeRepos imports totals from it each day: the search words, the pages, the clicks, and the number of times a page showed in the results. These totals contain no data about one person.
How long AwesomeRepos keeps the data
- Page views, events, and the days of signed-in Members: 400 days.
- Errors: 90 days.
- The random value for the daily code: 1 day. The server deletes it after the UTC day ends.
- Totals, feedback, and search data from Google: no time limit. Totals are counts for each day or week, page, site, and event. They contain no daily code.
- Accounts, Bookmarks, and Saved Views: until the account is deleted.
- The return marker and your theme choice: in your browser, until you delete them.
Questions
To ask a question about this page or about your data, use thefeedback form. We read each message.