Privacy Policy

1. Information handled by the current Service

The current Service does not include user accounts, a member database, or a feature that stores user-created reveal content on a proprietary RevealNum server. Titles, values, units, themes and animation settings entered in Quick Number Reveal, scene content created in Result Reveal, names, scores and ranking settings used in Ranking Reveal, and participant names or draw settings used in Draw are handled in the browser to provide those features.

Table data pasted into Ranking Reveal and CSV / TSV files selected by the user are read in the browser for parsing, column mapping and ranking generation. The current implementation does not upload those file contents to a proprietary RevealNum backend for processing. Winner selection in Draw also runs in the browser, and draw history is kept only in page memory while the page remains open.

To keep edits during the same browser session, the Service may store Quick Number Reveal, Result Reveal, Ranking Reveal and Draw draft settings in sessionStorage. When a user explicitly chooses Japanese or English, that functional preference is stored in localStorage (revealnum.locale) so the root page can remember the language choice. The current implementation does not synchronize these browser-stored draft values to a proprietary RevealNum backend.

2. Technical data processed for hosting

The Service is designed to be delivered through infrastructure providers such as Cloudflare. To deliver pages, maintain security, prevent abuse, and investigate failures, hosting providers may process technical request information such as IP addresses, user agents, request times, and request metadata under their own policies.

3. Contact information

If you send us an email, we may process your email address, name or display name, subject, message, and any other information you voluntarily include so that we can reply and resolve the request.

Contact records may be retained for as long as reasonably necessary for support, rights protection, abuse handling, and legally required records, then deleted using reasonable methods when they are no longer needed.

4. Cookies, analytics, and advertising

When enabled in production, the Service uses Cloudflare Web Analytics to understand aggregate page views, visit patterns, and performance metrics such as Core Web Vitals. According to Cloudflare, Web Analytics does not use cookies or localStorage to collect usage metrics and is not intended to track individual users across customer properties.

The Service includes a provider-neutral product-event layer for actions such as theme selection, animation selection, reveal start and completion, fullscreen use, and language switching. Reveal values, titles, subtitles, prefixes or suffixes, contact-message text, and other free-form user input are deliberately excluded from analytics event payloads. Cloudflare Web Analytics does not currently accept custom events, so these product events are not sent to Cloudflare.

Google Analytics (GA4) is not used. If Google AdSense is explicitly enabled in production, ads are limited to designated slots on ordinary content and tool pages. The Service does not place its own ad slots inside the reveal overlay or on Privacy, Terms, or Contact pages.

When Google AdSense is enabled, third-party vendors, including Google, may serve advertisements. These vendors may use cookies to serve ads based on a user's prior visits to the Service or other websites. Google's use of advertising cookies enables Google and its partners to serve ads based on visits to the Service and/or other websites. As a result of ad serving, third parties may also place or read cookies in a user's browser or use web beacons, IP addresses, or other identifiers to collect information.

Users may opt out of personalized advertising through Google My Ad Center (https://myadcenter.google.com/). Users may also visit https://www.aboutads.info/ to opt out of some third-party vendors' use of cookies for personalized advertising where that option is available.

When AdSense is enabled, the project is designed to use Google's certified Privacy & messaging CMP for consent or opt-out choices where regional rules require them, including the applicable EEA, UK, and Switzerland flows. The site does not create a separate custom CMP database that duplicates the user's consent record.

5. Service providers and disclosure

Except where required by law, we do not operate the Service for the purpose of selling personal information we hold to independent third parties without consent. Providers needed for hosting, email, and other service functions may process information to the extent required to perform those functions.

6. International processing

Because internet infrastructure is distributed, hosting, email, or other providers may process information outside the country where a user lives. Where required, we will review safeguards applicable to those transfers.

7. Privacy requests

Where applicable law gives you rights to access, correct, delete, or otherwise request action concerning information we hold about you, you may contact us through the Contact page. We may need to verify your identity before fulfilling certain requests.

8. Children’s privacy

The Service is a general-purpose result presentation, ranking, and draw tool and is not designed to actively collect personal information from children. If future features require age-specific consent or protections, we will implement the additional measures required for those features.

9. Changes to this policy

We may update this policy when features, advertising, analytics, laws, or operating practices change. If a change is material, we will provide a reasonably prominent notice through the Service.