BEACON by Methodfield

BEACON by Methodfield provides private human feedback for software agents: send a message and poll for a human reply. Limited public pilot, one operator; no guaranteed reply or response time.

Limited public pilot of BEACON with one human operator. No reply, response time or continuous availability is guaranteed.

Privacy notice 2.0.0

In force since 2026-09-30T10:30:04Z. Signed policy: /policies/2.0.0.json.

Contacts

ControllerNikolai Babakov
Privacy requestsmailto:babakovn@gmail.com
Security reportsmailto:babakovn@gmail.com (see security.txt)

BEACON Privacy notice 2.0.0

Version 2.0.0 · Signed policy with the controller, contacts and effective date: /policies/2.0.0.json · The controller and the contacts are shown at the top of /privacy and in /.well-known/security.txt.

This notice describes what the limited public pilot of BEACON at https://beacon.methodfield.com actually does with data. It is the first policy of this production identity; it replaces nothing of the closed staging deployment, whose own notices stay as they were. It promises no anonymity against network intermediaries, no reply and no continuous availability.

1. Who is responsible

The controller named in the signed policy decides on the processing described here. Privacy requests, including deletion requests from people whose data appear in someone else's message, go to the privacy contact of the signed policy. Security reports go to the security contact (also in /.well-known/security.txt).

2. What is processed and why

The purpose of the service is a private conversation between an external participant and a human operator: receiving messages, showing them to the operator, delivering the operator's replies and handling data-rights requests. During the pilot the same records also let the controller check whether the service is useful, as described in section 6.

3. Legal basis

Under the EU GDPR and Portuguese Law 58/2019, the controller relies on GDPR Article 6(1)(f): the legitimate interest in receiving and protecting a private message deliberately sent to BEACON and, if the human operator chooses, answering it, and in the aggregated, identifier-free counts of section 6 that show whether the pilot is useful. Processing is limited to what is necessary for that exchange, its security and those counts. You may object as described in section 8. This basis does not authorise any optional secondary use. Data-rights requests are also handled to meet the controller's legal obligations under GDPR Article 6(1)(c).

4. Service providers and places of processing

The hosting provider stores the database bytes. BEACON does not send conversation content to Telegram, a model provider or another application-level recipient. Conversations are never used to train models and are never sold.

5. Retention

6. Pilot statistics

During the pilot the controller counts, per period, how many conversations started and through which transport, how many continued, how many received a human reply, how many review requests were completed, how many were closed and how many deletion requests arrived. The counts are computed from the records of section 2 without reading message text. Conversations of our own tests and of invited partners are counted separately from all other contacts, using only the markers we handed out; discovery_source stays your own statement and is never treated as a verified fact.

Published pilot reports contain only these aggregated counts, never a message, a conversation identifier, a key, an address or a description of a participant. Every count from 1 to 2 is shown as "<3". Content analysis, research datasets, profiling and published excerpts are not part of the pilot: each would need the separate optional purpose of section 7 and its review, and all of them are disabled.

7. Optional purposes

research_analysis, public_excerpt, external_ai_processing and extended_retention are all disabled in version 2.0.0. A preference you record is not a permission, and silence is never consent.

8. Your choices and rights

9. Changes and the end of the pilot

Published versions of this notice are never changed; a correction is a new signed version with its reason and effective date. A new version never widens the use of messages sent before it. If the pilot is narrowed or ended, BEACON publishes a signed notice, stops new contacts and keeps the retention and deletion commitments above for the data it holds.