What is collected, and what happens to it

Giveaway data

We store item titles, descriptions, categories, conditions, areas, handover times, expiry dates, account associations, request messages and states, report reasons, AI decisions and timestamps for free in-person handovers and abuse handling. Only item information, states and dates are public; account identifiers, requests and reports are private.

Item text (title, description, category, condition, area and handover time) and request messages reach the operator's locally hosted model in Japan for AI-only publication decisions. No external AI service is used.

Only the giver and selected requester can read a handover note. It is never public or sent to the model. Include contact details only if you wish to share them with that person.

Closed items are deleted after 90 days; closed requests after 30 days; handover notes after 30 days from closure. Related requests are also deleted 30 days after item closure. Account closure deletes that member's items, requests and reports. Reopening, withdrawal and related transitions clear notes immediately. No payment information is collected and no payment ever takes place.

What is collected and why

Reading the site without an account collects nothing from you. The table describes what is stored once you create an account or submit a form.

What is published and what is not

Governance is AI-only with no human review. Allowed issues and proposals are published as submitted; doubtful ones are published with a visible marker and reason; blocked ones stay private with the AI rejection reason shown to the submitter.

Civic text is processed for publication governance by the operator's locally hosted model in Japan, not a third-party or external AI service. Help requests are always private and never sent to a model. Account data and submitted coordinates are never sent.

Published records do not carry the contributor's username. Help requests, contribution offers, profile images, coordinates and internal review notes are never published.

The public data page shows counted totals only — no text, no usernames, no locations and no small-group breakdowns.

Location

"Use my location" asks the device for a position only when you press it. Declining leaves the map and the list fully usable.

The position is kept in the browser session and is not sent to the server. It is not written to your account, to analytics, to logs or to any public record. Distances are calculated in the browser. It is discarded when the tab closes, and while the map is centred on it the position is kept out of the URL.

The visible map rectangle is sent to the server to select records for the current view. That is the extent being displayed, at the precision the display needs — not your position.

Submitted coordinates stay private, are never sent to the model, and are not copied to the public map by AI publication. Existing public locations are separate.

Sensitive categories and minors

Registration is limited to people aged 18 or over. No date of birth is collected — only the time of the confirmation.

Health, disability, criminal victimisation and family circumstances are not carried into published text. If you need to describe them in order to be helped, they stay private. Please do not write anything that identifies another person, and in particular a minor.

External transmission, cookies and processors

Cookies are used to keep you signed in. There are no advertising or tracking cookies.

If you switch notifications on, that device's push subscription endpoint is used with a browser push service — Google, Mozilla or Apple, all in the United States. The content of a notification is never sent. What travels is a signal saying an update exists; what it is stays on your account page, behind your session. You can switch it off at any time, and the subscription is deleted then, when the account is closed, and when the push service reports that the device no longer exists.

News notifications require member topic opt-in on your account page and noteworthy published information, at most one per day. Topic preferences and delivery days stay in the site database, are deleted on account closure, and never reach a model. Only published information reaches the local model for daily/weekly digests, published after deterministic date, number and place support checks and AI governance. Model unavailability retains the previous digest and sends no news notification.

The separate weather warnings topic is optional. Official JMA XML is conditionally fetched every two minutes. Newly issued warnings or emergency warnings enqueue content-free notifications once per member and kind per six hours; advisories and continuations do not. Kind codes and last delivery times stay in the site database until account closure. No model is involved in retrieval, parsing, display or notification, and JMA items are excluded from AI digests. No visitor data is sent to JMA during retrieval. Attribution: 出典：気象庁.

Traffic reaches the site through Cloudflare, Inc. (United States): a processor entrusted with delivery and protection, and a third party outside Japan. It is treated as a party maintaining the arrangements needed to apply protections equivalent to Japanese law on a continuing basis; the receiving country and information about its regime are provided on request. The map is drawn from geographic data served by this site; there are no external map tiles, no external fonts, no social embeds, no error monitoring, no CAPTCHA, no external AI service and no blockchain.

The full register is below and is also published in machine-readable form at /api/v1/external-transmissions/.

Security measures

Passwords and recovery codes are stored as hashes; the originals are not kept. Passkeys are available for sign-in. Connecting IP addresses are handled as hashes rather than as addresses.

In the browser, the origins a script may come from are restricted, framing is denied, form destinations are same-origin, and referrer disclosure is limited. Operator screens are restricted to accounts holding that role.

Sessions, authentication challenges, rate counters and exceedance records are deleted automatically once expired.

Requests about your own data

Disclosure, correction, addition, deletion, suspension of use and suspension of third-party provision are handled at [email protected], to the extent your identity can be confirmed. The operator's name and address are provided in answer to such a request.

You can close your account yourself, from your account page. It deletes the account, its registered passkeys, sessions, profile image, security history, private help requests and contribution offers, and the registration record tied to it. Already-published issues, proposals, decisions and projects remain as the record of a publication decision and are detached from you; they contain nothing that identifies the contributor. The passkey stored on your device cannot be removed from here — delete it in your device's settings.

If there is a breach

If personal data is leaked, lost or damaged, or may have been, the first priority is establishing the scope and stopping it spreading, followed by deciding whether the Personal Information Protection Commission must be notified and whether affected people must be informed. What was done is recorded.

Revisions

This policy is version 2.4, effective 2026-10-11. A revision that changes meaning updates both.