DENCHU COLLECTION · PRIVACY POLICY
Privacy Policy
English translation for convenience. If it differs from the Japanese original at denchu-collection.com/privacy, the Japanese version applies.
Optional LINE Login and Progress Saving
If you choose “Continue with LINE”, your LINE identifier, display name and profile image are handled through Supabase authentication dedicated to Denchu Collection. We do not obtain your email address, friends list or chats, and we do not send notifications. No login is needed for free play. This is a separate system from the ChatGPT login used for purchase rights, and it does not share accounts or data with the tennis service.
Only when you yourself tap “Save” do we save the following to the dedicated Supabase storage: your team, training, items, battle progress, prefectures visited, number of summons, pole numbers and meetings, and reunion reward records. Saving is not automatic. We keep the current save and, for recovery from mistaken operations, the one immediately before it. We do not send your exact location, photos, per-shot location matching values, photo matching values, movement routes, conversation choices or your device's sound settings. Purchase rights for the paid pass, pass-exclusive training and data for pass-exclusive challenges in progress are not included in this backup.
Access is restricted so that saves can be read and written only through your own login. Authentication information is also kept in the browser. The link between the progress on your device and your LINE identifier is stored on the device, to stop operations that would mix in progress from a different account. Logging out does not erase the progress on your device or your cloud save. Restoring replaces your current team and items, but the claim history on your device remains. This does not completely prevent on-site rewards from being claimed twice if you change devices.
Your LINE identifier is never sent to, or combined with, advertising or the play counts. Connection information involved in authentication is processed by LINE and Supabase. Saves are kept until you ask us to delete them or the service ends, and the previous save is replaced at the next save. To delete your authentication data or cloud save, contact us at the address below. We will act after verifying your identity; the data may remain for a certain period in the provider's history kept for failure recovery. Supabase Privacy Policy
Automatic Counting of Play Activity
For the trial summon, we count only the number of times each of the following happens: choosing the camera, the camera starting successfully or failing to start, choosing to play without a camera, scanning, gaining a teammate and failing to save. For battles, starts, first actions, ultimates, wins and losses are counted separately from the same stages of Hikari's introductory battle. We also count the number of times the introductory battle was cleared after gaining a teammate from the trial summon, within the same measurement window in the same tab. We do not collect the reasons a screen was closed or any per-person history.
The dedicated ad links A and B are counted as fixed categories. The old shared link cannot be told apart, so it is not assigned to A or B afterwards. Visits that come through a shared copy of a link fall into the same category, so the counts do not prove the number of people gained through paid ads or any effect on purchases. The URL and ad click IDs themselves are not stored.
To improve photo-taking, we also count only the number of times the scanner is opened, a shot is started, a shot is completed and the pre-summon check is passed, together with the rough reasons for stopping (permissions, GPS check, camera, image quality, AI assessment, re-exploration limits, save failures, etc.). Photos, location data, numbers and the original error text are not sent or stored in these counts.
After insufficient GPS accuracy, we also count the number of times the recheck button is pressed on the same scanner screen, the number of times accuracy recovers on that recheck and the number of times a summon can then be saved. The ON/OFF state of settings itself is not collected. These counts are not linked to actions after a screen is closed or after moving to another browser.
Tapping “Agree and Play” when you start the game includes consent to counting for the purposes of improvement and checking advertising effectiveness. After you agree, this site automatically counts visits, play starts, battle wins and on-site summons. You do not need to press a separate measurement button. Counting does not start on the basis of an earlier consent alone; existing users are also shown the changes and asked to confirm once. Screen views and actions before you agree are not sent.
Starting September 27, 2026, we also count, as counts only, whether the game is played again on a later day (return visits). On this device we store only “the first day counted (date in Japan time)”, “the category of the first entry point”, “how play began (first time / had earlier progress / moved from an in-app browser / Home Screen app)”, “the last day a return visit was counted” and “the types of first-time events already sent”. We send one event for each day you open the game, and one event each, once only, for your first teammate, first win, first on-site summon, first reunion and first launch from the Home Screen. No ID is created, and the server stores only total counts per date.
The number of times the ad pages (/x, /x/a, /x/b) are opened is counted on the server even before consent. Only totals per date (Japan time), entry point and rough browser type (in-app / Safari / Chrome / other) are kept; nothing is stored on or read from your device, and IP addresses, detailed browser information and cookies are not used. Automated access such as link-preview fetching and prefetching is excluded.
Consent and Settings for This Device
If you withdraw consent, you will return to the confirmation screen the next time you start the game. Your saved progress and purchase rights remain. Total counts already received cannot be withdrawn individually.
The “Withdraw Consent” button is available on the website: https://denchu-collection.com/privacy (Japanese).
For Operators and Testing
The setting “Exclude this browser's activity from the counts (return visits are counted separately as ‘Test’)” is available on the website: https://denchu-collection.com/privacy (Japanese).
What Is Sent and How It Is Counted
We send only the version number of the explanation you agreed to, a flag showing that you have agreed, the traffic-source category (X ad link / X / other / direct or unknown), a category showing whether free progress existed when measurement started, and the type of action. The server stores only total counts by date (Japan time), category and action. Photos, GPS data, numbers, names, personal IDs, save contents, and the original URL or referrer are not included in what is sent, and the counts are not linked to purchases, feedback or accounts. We do not use ad pixels or third-party analytics services.
Thirty minutes in the same tab (or until the date changes in Japan time) counts as one window, and each action is counted only once during that window. A play start is when indoor practice or the scanner is opened, or when a win or summon is achieved. Wins include indoor practice, and on-site summons are recorded only after they are successfully saved to the device. “First” means the first time within this measurement window, not a person's first time ever. Actions may be counted again in a new tab, on another device or after storage is cleared, so this method does not show numbers of people or retention rates (return visits are counted separately, as described below). Loaded saves and actions before consent are not counted retroactively. Failed transmissions are not resent, and use without consent is not included, so the counts are lower than actual use.
For return visits, we send only the version number of the explanation you agreed to, a flag showing that you have agreed, the category of the first entry point, how play began, the rough browser type (in-app / Safari / Chrome / Home Screen / other), the type of action (start, use on that day, first teammate, win, on-site summon, reunion, launch from the Home Screen) and how many days it has been since the first day counted. The server stores only total counts by the date received and by the “first day” obtained by subtracting that number of days from it. Different browsers (such as X's in-app browser and Safari) are counted separately. When the game shows the “Open in browser” prompt, a move marker (containing no date or ID) is added to the end of the address of the in-app browser page that has already been counted, and the destination counts the visit as a “move” rather than as new. Return visits from a browser with the operator/testing exclusion turned ON are counted separately in a “Test” category and are not included in the actual figures. If you withdraw consent, the return-visit records on this device are also deleted. If they cannot be saved or sent, they are not counted and are not resent.
The traffic source is fixed at the start of this window. For the dedicated ad URLs, the X ad category is recorded, but ordinary X links cannot distinguish ads from regular posts, and in browsers that drop the referrer they become “direct or unknown”. Shared copies of the dedicated ad URLs also fall into the same category, so the counts do not prove visits gained through ad spending.
Your consent, the explanation version and whether counting is enabled are stored in this browser; the start time, rough categories and the names of actions already sent are stored in the tab's temporary storage. No tracking ID is created, and none of this is included in game backups. The tab's stored state is replaced at the next measurement after checking whether 30 minutes have passed or the date has changed. Global Privacy Control, the operator/testing exclusion and states in which storage is unavailable take priority and stop count submissions. We do not circumvent these restrictions, and not being counted makes no difference to rewards or purchase rights. If you withdraw consent, submissions in progress are cancelled as far as possible, and you are asked again the next time you start the game. If the deleted or stopped state cannot be saved to the device, a warning is shown and counting stops only on that screen. Daily totals that cannot be traced back to individuals are kept to check trends, with no automatic deletion deadline. Connection information needed for the communication itself is processed by the hosting platform, but it is not stored in these count tables or in the app's measurement logs.
Pass SSR Draw and Training Records
To provide the product, enable restores and prevent re-draws, we store on the server, together with the purchase record, the purchaser's matching value, the order number, the environment category, the product version, the IDs of the 5 Denki chosen, the grant number and the date and time the draw was finalized. The draw result is kept even after a refund; the retention period and deletion contact are the same as for the purchase records below. This is not linked to the game's play counts. Training stats and equipment are saved on the device per grant number and included in game backups. Purchase rights cannot be restored from this device data alone.
Initial Confirmation and Per-Feature Permissions
When you first tap “Agree and Try It” or “Agree and Continue”, the version number and the date and time of your agreement to the Terms of Use and the explanations on this page are saved in this browser. This is not linked to your name or any account, and the consent date and time on this device are not sent to the server. It is kept for as long as site data remains, so that you are not asked to agree to the same explanation every time. It is not included in game backups. If it cannot be saved, consent is accepted only on the screen that is open, and counting does not start. You may be asked again next time. If an important change requires renewed consent, we will explain what has changed.
This consent covers the counting described above and the sending of photos to the number-reading AI described below, but it does not enable camera or location permissions. The camera for the trial summon starts only when you choose “Show a pole on camera”; it only displays the image, and nothing is captured, recorded or sent. GPS is not used either. For on-site summons, camera and location access are requested only when you start taking a photo, and the browser's permission screen appears as needed. Even without granting permissions, you can use indoor battles, training and purchase-rights checks. Without location data, exploration rewards from on-site photos are not available. Shooting stops when you close the scanner or leave the screen. We do not continuously track your walks. You can revoke permissions in your browser's site settings. Deleting site data on your device also erases your consent record and game progress, so if you want to keep your progress, save a backup first.
About This Web Version
“Denchu Collection”, provided under the operator name “Sanraku”, is a browser game that does its own counting without using external ad-tracking or analytics services. No login is needed for free play, and game progress is saved in the browser you are using.
Purchases and Restoring Purchase Rights
Purchases and the restoring of purchase rights use ChatGPT login, and we receive identity verification information from the hosting platform. No login is required for free play. Whether sales are open is shown on the purchase screen. The sandbox is for testing, and no real money changes hands. Test purchases and real purchases are managed in separate tables, and rights do not carry over between them.
The app's purchase table stores a matching value created from your user ID on this site, the order ID, Stripe checkout and payment IDs, product and price IDs, the environment category, the purchase status, and the dates and times of creation, update and payment. In production, it also stores a record of status changes and a category used to exclude developers, tests and the like from actual results. Names, email addresses, card numbers, game save data, photos and locations are not stored in the purchase table. Information that Stripe receives on its payment screen is managed by Stripe. Stripe Privacy Policy
This information is used to check and restore purchase status, prevent duplicate purchases, stop perks after refunds, manage sales and prevent fraud. While perks are displayed in the game, their status is rechecked periodically online. Purchase counts are tallied from orders verified on the server and kept separate from the game's play counts. Withdrawing consent to counting is separate from deleting purchase rights or getting a refund.
Purchase-rights matching records are kept while perks are being provided. After provision ends, they are kept for inquiries, refunds and fraud handling, and, as a rule, an administrator deletes them, or converts them into aggregates not linked to individuals, within 5 years. Records that must be kept under law or for dispute handling are retained only for as long as necessary. Test records are deleted by an administrator within 90 days after testing ends. There is no immediate automatic deletion feature. Please send requests for disclosure, correction or deletion to the contact below. Where retention is required by law, or where deletion would make it impossible to verify your purchase rights, we will first explain the impact and then respond. Deleting improvement data in the game is separate from deleting purchase records.
Camera, Photos and Plate Detection
For photos from the on-site camera, image quality is checked on the device, and AI determines whether a number plate is present. The first time, about 36 MB of AI data is loaded. The assessment score is not a probability of being correct. After you give the latest start consent, number reading is carried out in parallel. The AI alone does not grant rewards; GPS at the time of the shot, movement and usage counts are also checked. Saved photos and samples are for practice only and are not sent to the AI. Video and photos are not saved in the browser. A matching hash and exploration code for each shot, and the pole numbers read and meeting records, are saved in your save data. This does not completely prevent misreadings or location spoofing. The camera is used only when you explicitly start it, and it stops when you close it or after 75 seconds.
Plate Number Reading (Included in the Consent at Start)
To read the number, the photo inside the frame is sent to a reading AI (Google Gemini). This game does not store your photos. This is explained on the first consent screen, and existing players also re-consent to the new explanation once. No photos are sent before consent, and there is no separate check before each shot. The indoor trial and practice with saved photos or samples are also excluded from sending. You can withdraw consent from the settings on this page.
The area inside the frame of the on-site photo and its surroundings is cropped, converted to a JPEG no larger than 1024 px on its long side and sent via this site's server. Location data and EXIF are not included. Because it is sent after the image quality check, in parallel with on-device plate detection, transmission begins before it is confirmed whether a plate is present. Frame your shot so that faces, house nameplates, car license plates and the like are not inside the frame.
Numbers that are read are shown on the confirmation screen, in summon results and in the Index. The character and rarity are fixed by the combination of prefecture and number, and from the second time onward at the same pole, it counts as a reunion and increases affinity. The number, prefecture, Denki, date and time of first meeting, and reunion reward dates are saved in your device's save data and backups. If you use the optional LINE cloud save, these meeting records are also included in the dedicated storage. GPS coordinates and photos are not included. Because numbers can give clues to your whereabouts, do not make your backups public to third parties.
Only if the number cannot be read does the game fall back to the normal random draw. Because of misreadings, identical numbers within the same prefecture and differences in region determination near prefectural borders, real poles may not always be identified exactly. Photos and numbers do not appear in diagnostic logs or the play counts. The reading server does not store photos or numbers.
Storage and processing on Google's side follow the Gemini API Additional Terms of Service and are separate from this game's non-storage. On the free tier, data may be used for service improvement and human review. Even with paid services, data may be processed for a certain period for purposes such as abuse prevention, so we do not guarantee “no storage at all”, including on Google's side.
To curb repeated submissions, a matching value derived from the connecting address is used in the server's temporary memory to limit the number of readings per minute. It is valid for up to about 1 minute and is discarded when a request is received after it expires.
AR-Style Camera Effects
The web version uses screen compositing that overlays GPU-rendered graphics on the camera image. It is not a spatial-awareness feature of ARKit or WebXR that anchors objects in real space or performs plane detection, depth sensing and the like.
Location Data When Taking Photos
With “Snap a Plate”, the camera can start first, and the GPS check runs in parallel. The shutter button first locks in the live camera frame and the time of the shot, and only GPS readings from within 8 seconds before or 15 seconds after it are combined with them. The location of an old photo cannot be updated later. If accuracy exceeds 30 m, the position is out of date or fast movement is detected, the shot is put on hold. On devices that cannot report speed, the change between the last two positions is used.
The latitude and longitude of the place where a summon succeeded (to 5 decimal places, about 1 m units), GPS accuracy, the times of shooting and claiming, and the exploration code are saved in this browser's save data. They are not sent to the server or to external AI. There is no minimum travel distance and no limit on claiming again at the same spot. You can summon with a retaken photo, but the same shot cannot be claimed twice, and new summons are limited to 10 per day (reset every morning at 4:00 AM). If the number is read and it is the same pole, it counts as a reunion, and rewards are given once per day per pole. Reuse of the same photo whose number cannot be read is prevented. This history is kept as long as the save exists, and when an old backup is restored, it is merged with the claim history remaining in this browser. Backups also contain location information, so do not make them public to third parties. Deleting site data deletes this history and your game progress. Preventing repeat claims after deletion or across different browsers or devices is not supported.
The walk-tracking feature has ended, and no new distance traveled or step counts are recorded. Previously saved daily and total distances and region codes remain in your device's save data and backups as past progress. Continuous movement routes are not stored or sent.
Partner Conversations, Adventure Log and Quiz
Conversations with Hikari proceed through prepared lines and choices. Your walk preference (one of 3: scenery, snacks or a quiet walk), identifiers of the conversations you replied to, your total distance when you started the Log (for compatibility with the old format) and your summon and win counts when you last talked are saved in your device's save data. We do not collect free text, recordings or exact locations, and we do not send conversations or preferences to our servers or to generative AI. Conversation choices do not increase or decrease currency, abilities or purchase rights. The Adventure Log unlocks free short stories based on your total number of summons and wins. Stories unlocked through earlier walks are kept, and there are no deadlines or consecutive-play requirements. These records are included in game data backups. Local Quiz answers and bond ranks are also processed and saved on the device.
Voices in Conversations and Battles
Partner conversations and some battles use pre-produced Japanese synthesized voices. Voices are ON by default, and only the recordings needed are loaded from this site when you open a conversation or use a move. Nothing plays just from opening the page. The voice ON/OFF setting is remembered in this browser and is not included in game backups. Battle voices also stop when sound effects are OFF. The microphone is not used, and conversation text, location data and personal information are not sent to external speech synthesis services. Voices stop when you close the conversation, go on to take a photo or leave the screen. A playback failure does not change the ON/OFF setting or your game progress.
Music & Voice
The BGM setting is ON at first. The start screen tells you that there is audio, and the BGM for each scene is loaded after you tap “Agree and Play”. A saved OFF setting is kept, and music does not start just from opening the page. You can stop the music or change the volume in the Music & Voice section. It stops while you are taking photos and while you are away from the screen.
Read-Aloud Assist
The read-aloud function of your device or browser is used only when you open “Read-aloud assist (device voice)” in the Local Quiz and tap “Read Displayed Text Aloud”. This is a separate feature from the synthesized voices in short partner conversations. It is an assist feature independent of the game's sound-effect settings. How the speech is processed depends on your OS, browser and selected voice. Reading stops when you stop it, close the assist panel, the displayed text changes or you leave the screen.
Previous ID-Linked Improvement Data (Suspended)
The previous measurement linked to user IDs, the automatic sending of purchase interest and new server-side intake have been stopped. Having had this setting ON in the past does not mean you have consented to the new counting. Plate detection and game progress run on the device. The following describes the data sent by the earlier limited-release version. Deletion remains available.
Measurement, retention and deletion in the earlier limited-release version
To make the game easier to play, a random matching ID specific to this browser is created only after the user chooses “Send” on screen. Predefined types of events (starting to use the page, completing practice, whether a permission check succeeded, verified on-site scans, completing real battles, the install guide, and viewing, expressing purchase interest in or sharing the Founder's Pass) are sent to this site's server with random IDs for each session and each submission and the consent version. The server converts each ID it receives into an irreversible, purpose-specific matching value and does not store the raw IDs. Earlier consent to “total counts without IDs” is not carried over to this method; the choice is reset so that you can choose again. If you previously chose not to send, that setting carries over and sending remains stopped. Practice and partner joins already completed at the time of consent are recorded once as the current state, but for on-site scans and real battles, only those that actually occur after consent are recorded in the flow used for sales decisions.
What is sent is limited to the event name, rough progress stage, action result, the identifier of the product idea and the random IDs above. Photos, photo hashes, entered numbers, prefectures, latitude and longitude, movement routes, pole matching codes, character names, detailed game progress or save contents, advertising IDs, names, email addresses and full URLs are not included in the event body. In the private test version, the browser may automatically send a same-site authentication cookie needed for the hosting platform's login check, but it is not stored in the app's improvement count tables. Game progress saves and backups are kept separate from the improvement IDs, which are not used for accounts or advertising. If browser storage is unavailable, safe locking between tabs is unavailable or improvement data is OFF, no browser-wide matching is performed. Purchase interest is likewise sent only when a safe resend-prevention ID can be stored.
On the server, in addition to totals by UTC date, a scheduled deletion date within 180 days is set for browser ID matching values, the exact times of first and last receipt, and the confirmation time and status of each first-time achievement. Matching values of consented submission IDs (used so that resent transmissions are not double-counted) and their exact receipt times are given a scheduled deletion date that, because of rounding to 4:00 AM Japan time, falls at least 44 and at most 45 days after receipt. Purchase interest that is not linked to a browser also gets a new random ID for each submission, and only its matching value and date, not the raw ID, are used for resend prevention for the same period. This purchase-interest ID is not linked to the browser, session, game progress or the receipt time to the second. On the device, the same submission ID is kept for retries until successful sending of purchase-interest and first-achievement events is confirmed, but retrying is cut off at 30 days so that, even allowing for normal device clock corrections, it is unlikely to go beyond the server-side resend-prevention period. At the next periodic check after 30 days is reached with the page open, or, if the page was closed, the next time you use this site or when the same first achievement is checked again, the raw ID is deleted, leaving only an on-device state of “result unconfirmed”, and to avoid duplicates nothing is resent with a new ID. If the clock moves back to before the time of the previous check, the same on-device state is also applied. On success too, an on-device state of “sent” is saved first, and then the raw ID is erased. Retention days use 4:00 AM Japan time as the boundary: based on the day of the first consented event accepted and confirmed in the database, only return visits in which session_started is accepted exactly 1, 7 or 30 days later are recorded as D1, D7 and D30. Even if simultaneous submissions are processed out of order, the base day is not rolled back to an older receipt time confirmed later. This measures the retention of “browser environments that consented to measurement”, not first-time visitors or unique individuals. A regular browser and the Home Screen version, different devices, private browsing, and use after deleting site data may count as separate environments. The reference metric “Activated” is met only if, within 24 hours of the start of measurement, both a verified on-site scan and a non-practice battle occurring after that start are recorded; it is not met through Controls Practice or past save states.
The current private test version deletes expired rows in small batches whenever new submissions are received, so even after a long period without use, it cleans up gradually without halting intake. However, if there is no further use, data may remain past its scheduled deletion date. Before public release, we will add and verify an independent deletion process that runs on schedule even without use. The database keeps point-in-time history for disaster recovery, so data deleted from the tables in normal operation may still be included in states within the recoverable period. The exact recoverable period of the plan we adopt will be stated on this page before public release. Because restoring to an earlier point in time could bring deleted rows back, before public release we will implement a deletion process that first commits, to external ledgers with different purposes and access rights, the matching values used to re-delete browser rows and the matching values used to prevent revival. We will rehearse a procedure for restores in which new intake is stopped, deletion of expired rows and both ledgers are reapplied, and intake resumes only after confirming that no targeted data remains.
From “⚙ Settings” at the top right or the controls on this page, you can stop or resume sending new improvement data at any time, regardless of your game progress or whether you have a partner. If you choose “Stop Sending & Delete Linked Data”, the stop is first applied to all tabs; this browser's raw random ID is then sent only for the same-site deletion process; the browser matching rows and short-term resend-prevention rows created from that ID are deleted; and then the ID on the device is also erased. So that deleted rows are not revived by submissions arriving late from other tabs, a scheduled deletion date at least 44 and at most 45 days after receipt is set only on purpose-specific deletion-record matching values that are not linked to the original data. If the history is very large, it is processed in small batches, so retries may be needed until it completes; however, the deletion-record matching values are recorded first and prevent revival by delayed submissions in the meantime. Counts that have already been separated from the browser and added to totals cannot be individually reversed, so they remain. If deletion over the network fails, then as long as on-device storage is available, sending stays stopped and the on-device ID is kept so that you can retry. If on-device storage itself cannot be updated, sending is stopped on this screen, but because the stop and the deletion of the on-device ID cannot be reliably applied to other tabs or after a reload, success is not shown; instead, you are guided to check free space and browser settings and try again.
When Global Privacy Control is enabled, it takes priority over the on-screen setting, and optional events are not sent. Only when you yourself press the purchase-interest button is that one explicitly expressed interest accepted. If improvement data is ON, it is recorded against the same browser matching value; if it is OFF or GPC is enabled, it is recorded as a daily total not linked to the browser; and the matching value of each submission's resend-prevention ID is given a scheduled deletion date at least 44 and at most 45 days after receipt. In the current private version, deletion happens progressively on access, so actual deletion may occur after the scheduled date. When GPC converts an already-prepared consented measurement request into this detached form, the event ID is reused as the resend-prevention ID for the same transmission, and the session ID is discarded. The raw browser ID is used temporarily during request processing only to check the deletion-record matching values, and is not used to create or update browser rows. The converted resend-prevention rows do not store the browser ID and cannot later be singled out per browser, so they are treated as subject to deletion based on their scheduled deletion date. Purchase interest is not a purchase, reservation or sale, and not sending it makes no difference to game content or progress.
To curb abusive rapid repeated requests, a separate matching value created from the connecting address received by the hosting platform is used in the server's temporary memory. For deletion, rapid repeated requests for a single deletion target and mass submissions from the same connection as a whole are limited separately, to reduce the impact on other users who share the connection. These values are valid for up to about 1 minute, and expired values are discarded at the next receipt. They are not attached to stored totals or browser matching rows, and are not used for advertising or to identify users. Standard communication logs generated in delivery follow the retention period of the hosting platform used.
Deleting Previous Improvement Data
Deleting Previous ID-Linked Data
Previous ID-linked data is separate from the current counting, which does not use IDs.
Previous ID-linked measurement is suspended. Linked data sent from the limited-release version can be deleted with the button below. To withdraw consent for the current game, use the controls near the top of this page.
The “Stop Sending & Delete Linked Data” button is available on the website: https://denchu-collection.com/privacy (Japanese).
Quick Feedback Form
Only when you tap “Send Feedback” are the text you entered (up to 600 characters) and a random receipt number for each submission sent to this site's server. The receipt number, text, date and time received, and scheduled deletion date and time are stored in a database and used by the operator to consider improvements. No login, name or email address is needed, and there are no individual replies. Photos, GPS data, save data, device information and account information are not attached automatically, and feedback is not linked to advertising, purchase records or behavioral analysis. Do not write your address, pole numbers, passwords or card details. Using or not using the form does not change gameplay or rewards.
Text you are in the middle of entering and the receipt number used for resending are kept in this tab's temporary storage. When the page is shown again, a draft more than 24 hours past the last input or first submission is discarded; it is also erased when the submission is accepted. If your browser restores the tab, the draft may come back too. If storage is unavailable, a message says so. Nothing is sent merely by typing, and nothing is automatically resent when the connection returns. When resending, the same receipt number is used to prevent duplicate storage.
Text on the server is given a scheduled deletion date 90 days after receipt, and expired entries are deleted in small batches when new submissions are received. If use stops or the deletion process fails, entries may remain past the scheduled date. There is no independent scheduled deletion process. If you would like your feedback deleted, send the receipt number shown to you to the contact below. The hosting platform's history for failure recovery may retain the state before deletion.
As a measure against mass submissions, the overall number of submissions accepted is limited, but IP addresses and their matching values are never stored in the feedback table. Connection information involved in the communication itself is processed by the hosting platform. Even while the game's play counting is stopped, feedback you explicitly send is accepted for its separate purpose.
Inquiries and Feedback by Email
Sending email is optional. Simply opening your email app does not send anything. If you do send an email, your sender address and message reach the operator's contact desk and are used to respond to your inquiry and consider improvements. An email does not place an order or reservation for the game or register you for release notifications. Do not include photos, your exact location, pole numbers or payment information.
Data Stored on Your Device
Characters you own, energy, event progress and similar data are saved in the browser's local storage. This storage may be cleared depending on device or browser settings, and deleting site data also deletes your progress. The Safari version and the version added to the Home Screen may be treated as separate save data.
Safety
Do not look at the screen while walking, and stop in a safe place when taking photos. Do not run out into the road, enter private property, railway tracks or restricted areas, or touch or climb utility poles or power equipment. Cells and signals in the game do not indicate the exact locations of real power equipment.
Future Features
If we add features such as cloud saves or usage measurement and the data we handle changes, we will update this page before collection begins and provide the necessary consent, settings to stop it, retention periods and means of deletion.
Contact
Contact for operations and data handling (operator name): Sanraku
wakahisamk@gmail.com
For the seller's name, address and phone number, see How to Request Disclosure (Japanese). For help with how to play, see the Support page.
© 2026 Sanraku