Privacy policy

Operator: SciPocket · Updated: October 15, 2026

Analytics

The site uses Google Analytics (GA4) to understand usage and improve the site. Only if you allow analytics do we load Google’s measurement code and use cookies to measure page views, visitors, traffic sources, devices, and counts of searches, calculations, and grid operations. Measurement information is sent to Google.

Search terms and report contents are not sent as analytics measurement fields. For sync pair detail URLs, measurement keeps only the pair identifier. Advertising-personalization data collection is not enabled for analytics.

You can use the site without allowing analytics. Your choice is stored in your browser for 180 days and can be changed using “Analytics settings” in the footer. Withdrawing permission stops subsequent measurement. Changing this setting does not delete information already sent to Google.

How Google uses information from sites and apps · Google Privacy Policy

Cookie-free page and app-operation counts

To improve the site, we count requests for article and app pages, and search, calculation, and grid operations, by day in Japan Standard Time. Japanese and English counterparts are combined in these totals, with a breakdown by page language. This is separate from Google Analytics and runs regardless of your analytics choice. The stored totals contain only the date, public page path or predefined operation type, page language (Japanese or English), and count. We do not use counting cookies or store IP addresses, cookies, visitor identifiers, URL queries, referrers, or individual browsing histories in these totals.

We check the User-Agent and browser request-destination headers as requests arrive to exclude identifiable automated access and prefetches, but do not store these headers in the totals. Page counts include reloads and are an approximate request count, not a count of visitors or people who read an entire article. For app-operation counts, the browser sends only the operation type and page language to the server without attaching cookies. Search terms, teams, grids, and calculation settings are not sent for this count. Totals are stored on the server for the operator to review.

Bug and missing-data reports

The report category, sync pair, message, and submission time are stored on the server and used for corrections and handling inquiries. If email notifications are configured, this information is sent to the operator’s email address and processed by the email service used. A browser-identifying cookie is used to display only reports submitted from that browser. A value derived from the IP address is used to prevent excessive submissions.

Please do not include personal information such as your name or email address in reports. Cookies used to identify your reports are separate from analytics consent.

Saving sync grid builds

Saved sync grid names, sync pair identifiers, move levels, and selected tile numbers are stored in your browser’s localStorage. Saving a build does not send it to the server. Clearing the site’s browser data also deletes these saved builds.

Language preference and temporary transfer

Your display-language preference is stored in your browser’s localStorage. When switching languages, settings and results may be temporarily stored in the same tab’s sessionStorage. A transfer can be used once and is valid for five minutes. Language switching does not save your builds on the server.

Saving your team-builder roster

Excluded pair identifiers, individual move levels, and the default move level are stored in your browser’s localStorage. Your entire roster is not sent to the server. Clearing the site’s browser data deletes these settings.

Sharing damage teams by URL

When you select “Share this team”, the three selected pairs, grids, calculation settings, and results are saved on the server to create a short sharing URL. Anyone with the link can view them. Your full roster is not shared. A value derived from the IP address is used to prevent excessive submissions.

If a short URL cannot be created, the site creates a direct link containing the team data instead.

Advertising

Google AdSense code is installed on this site. Displaying ads requires Google’s review and approval.

Third-party providers, including Google, may use cookies to serve ads based on previous visits to this and other sites. Google advertising cookies allow Google and its partners to show ads based on your interests. Loading advertising code sends information such as your IP address and browser information to Google and other providers, and cookies may be used even if no ad is displayed.

You can disable personalized ads through Google ad settings. You can also disable third-party cookie-based personalized advertising through advertising choices page as well. You can manage or delete cookies through your browser settings. Permission for analytics does not constitute consent to advertising.

Google advertising technologies and policies · How Google uses data

If an advertising consent message appears, you can make your choices in that message. When European consent management is available, you can change your choices using “Advertising privacy settings” in the footer. Advertising choices and this site’s analytics choice are managed separately.

External images

Trainer images in search results are loaded from an external site, pokemon.brybry.ch. Loading these images sends connection information, including your IP address and browser information, to the image provider. We do not send search terms or report contents to that provider.

External fonts

The site uses Google Fonts. Fetching fonts sends connection information, including your IP address and browser information, to Google. This request is separate from GA4 analytics.

External links

After you follow an external link, the destination site’s privacy policy applies.

Contact

For questions about this policy, please use the form described on the About & contact page. We update this policy as needed.