Last updated October 26, 2026
About this policy
This policy describes the data handling implemented in the ServiceTool Atlas website. Hosting and email services also process information when you visit the site or contact us. Their account-level logging, analytics, and retention settings are not established by the website source code.
Information you provide voluntarily
You can email [email protected] about software recommendations, factual corrections, editorial feedback, business inquiries, or privacy questions. Correspondence can include your email address, name, message, and any attachments or other information you choose to provide. We use that information to review and respond to the matter you raise. Email delivery also involves your email provider and our receiving email service. Please do not send passwords, payment details, customer records, or other sensitive information.
The website has no account registration or contact form. Its interactive forms are the browser-based software finder and reader-vote confirmation described below.
Software finder
The software finder asks about your industry, team size, current software, budget, and operational priority. Its recommendation rules run in your browser. The website code does not transmit these answers to a server, put them in the page URL, or save them in cookies or browser storage. The page provides a “Start again” control to clear your answers.
Hosting and technical logs
Delivering and securing a website involves processing technical request information, which can include an IP address, requested URL, browser information, and request time. The repository contains an Astro static build and Cloudflare Pages-compatible headers and a voting function. These files do not establish which hosting services are active or which technical logs are retained.
Cloudflare dashboard settings for request logging, security features, and log or backup retention have not been verified in this repository review. We therefore cannot confirm those live settings or retention periods from the code. See Cloudflare’s privacy policy for information about its processing.
Cookies, analytics, and embedded content
Cloudflare Web Analytics has been configured for servicetoolatlas.com. Configuration alone does not confirm that its measurement script is installed or that analytics data is being collected. No Web Analytics beacon is included in the website repository reviewed for this policy; Cloudflare can also inject that script through hosting or proxy settings outside the repository. Live script installation and data collection have not been verified in this review.
Cloudflare describes Web Analytics as privacy-conscious, cookieless measurement of website usage and performance, such as page views and page-load timing. Its beacon does not use cookies or browser storage to measure visitors, and Cloudflare states that it does not track individual users across its customers’ websites. If the beacon runs, it sends measurement data to Cloudflare for processing and reporting. This analytics behavior is separate from our functional voting cookie and hosting security services. Read Cloudflare’s beacon documentation and data collection explanation.
The website source contains no advertising pixels, embedded videos, third-party font services, or browser local-storage or session-storage use. Fonts use your device’s available fonts, and site assets are served with the website. Hosting security cookies and other settings outside the repository have not been verified.
Reader thumbs-up voting
The comparison page requests voting availability and totals from /api/votes/. Whether voting is available depends on the running service configuration; the source code alone does not confirm that public voting is active. If the service is unavailable, the page disables voting and does not display totals.
When an available voting service accepts a save or removal, it sets the functional cookie atlas_reader_vote, containing a random browser identifier, with a maximum age of 180 days. Its lifetime is renewed on an accepted save or removal. The cookie is restricted to the voting API path, marked HttpOnly and SameSite=Strict, and marked Secure on HTTPS. It helps retrieve your selections, limit repeat voting, and let you undo a vote.
The voting database stores a keyed hash of the browser identifier, the software and category selected, and a timestamp. Rate-limit records contain the hashed identifier, a time bucket, and an attempt count. The application does not write names, email addresses, or IP addresses into these database records. Hosting and anti-bot services can process technical information separately. The experience checkbox is a self-confirmation, not verification of a customer account.
Only aggregate vote counts are displayed publicly. Your browser receives its own selections so it can show and remove them. You can remove a selection using its selected thumbs-up button while the identifying cookie remains available. Deleting the cookie does not itself delete database records and can prevent the site from recognizing your earlier selections.
The public-mode code loads Cloudflare Turnstile when you open a voting confirmation. The browser contacts Cloudflare for the anti-bot check, and the voting server sends the resulting token to Cloudflare for verification. Cloudflare processes information for this check under its privacy policy. The local development voting service uses a separate SQLite database and does not load Turnstile; local counts are labeled as preview data.
Affiliate links and external websites
No affiliate links or affiliate tracking scripts are published in the current website code. Vendor and research links take you to external websites, which handle information under their own privacy policies. Following a link makes a request to that destination; the site’s configured referrer policy sends only the referring origin for cross-origin HTTPS requests. See our affiliate disclosure for the current commercial-link status.
Data retention and security
The voting code deletes vote records whose saved timestamp is more than 180 days old during subsequent API requests. Saving a vote again updates that timestamp. Rate-limit records more than five minute buckets old are also deleted during subsequent requests. Cleanup depends on requests reaching the service; these rules do not establish deletion timing for backups or exported aggregate counts.
No fixed retention schedule for email correspondence, hosting logs, or provider backups is established in the repository, and we do not promise one here. The voting implementation uses hashed identifiers, same-origin write checks, rate limits, and public-mode bot verification. The hosting headers restrict framing and browser access to the camera, microphone, and location. These controls do not guarantee that storage or transmission is risk-free.
Privacy inquiries
For questions about this policy or information you have shared with us, email [email protected]. Describe the relevant interaction without including sensitive information. Voting records are linked to a browser identifier rather than an email address, so an email address alone does not identify a vote record.
Policy updates
We update this page to reflect changes to the website’s data handling and confirmed service settings. The date above identifies the most recent policy update.