WEBSITE INFORMATION
PRIVACY NOTICE
CURRENT WORKING NOTICE
This notice explains how the AfRA website handles messages, optional audience analytics, and the technical data needed to operate the service. Some legal assessments and account-specific hosting details are still being verified.
1. Who is responsible for your data?
Data controller: Zoltán Vörös, currently operating the AfRA initiative as a private individual.
Contact: hello@voroszoltan.hu
2. What information is handled?
When you use a contact, participation, or partnership form, the site stores the fields you submit, such as your name, email address, message, interests, and collaboration proposal. The participation and partnership forms also require a country selection from a standard list of ISO 3166-1 country and territory names. That country is stored with the application and used to understand its geographical context and administer and respond to the request; it is not collected through the contact form. Form submissions are available in the private AfRA inbox and are not automatically forwarded or used for marketing.
For all visitors, the site keeps a daily total of public page loads without a cookie, browser identifier, page path, referrer, country, or device category. This is a count of page requests, not unique people; reloads, repeat visits, and automated requests may contribute. If you accept optional analytics, the site additionally records page views, broad traffic source, approximate country and broad region, device category, active time, form activity counts, and not-found page counts. Detailed analytics do not store form contents, names, email addresses, precise location, or full browser user-agent strings. The site also processes technical request information to provide the service and prevent abuse.
3. Why we use the information and the working legal bases
Contact and participation enquiries: the current working basis is legitimate interests (GDPR Article 6(1)(f)) so the initiative can respond to questions and handle requests to take part. A documented balancing assessment is still needed before this basis is treated as final.
Partnership enquiries: the current working basis is taking steps at the sender’s request before a possible collaboration arrangement (GDPR Article 6(1)(b)). This basis applies only where the enquiry is about a specific arrangement the sender wants to explore; it needs legal review against the actual partnership process.
Basic page-load totals: the current working basis is legitimate interests in understanding the site’s overall reach and improving it, subject to a documented balancing assessment and legal review. This counter stores only a daily total and does not use a browser or visitor identifier. Optional analytics: consent (GDPR Article 6(1)(a)). Detailed analytics remain off unless you choose “Accept analytics”. Rejecting or withdrawing consent does not limit access to the website.
Abuse prevention and service security: the current working basis is legitimate interests in keeping the forms and website available and limiting automated or repeated submissions. This should be included in the controller’s documented balancing assessment.
4. Who provides the hosting and network services?
The website is published and hosted through ChatGPT Sites. Under the Sites terms, the Site owner is the controller for information collected through the Site, and OpenAI processes that information to host, maintain, and support it. For an EEA-based individual user, the ChatGPT Sites Data Processing Addendum identifies OpenAI Ireland Ltd as the contracting OpenAI entity. OpenAI may use the subprocessors listed in its current subprocessor list, including infrastructure providers.
The current DNS configuration also routes web traffic for afra.community through Cloudflare’s proxy network. Cloudflare may therefore process request and connection data as traffic passes through its network. For more information, see Cloudflare’s privacy policy and Customer Data Processing Addendum.
The OpenAI Sites terms and Sites Data Processing Addendum provide for transfers outside the EEA where needed under Standard Contractual Clauses or an adequacy decision. Cloudflare may also process data internationally under its applicable terms. The exact data-centre location for this Site has not been confirmed, so this notice does not claim that all data stays in the EEA. See the ChatGPT Sites terms for the current service terms.
5. How long information is kept
Form submissions, including the selected country: up to 12 months after the latest meaningful contact about the enquiry. If there is no later exchange, the submission date starts that period. When a meaningful exchange happens elsewhere, the administrator can use “Record latest contact” in the inbox to update the date. Information may be kept longer while an active collaboration or legal obligation requires it, and should be deleted sooner when it is no longer needed.
Expired messages are removed when the backend next performs its retention cleanup, including when the inbox is opened, a form is submitted, or an accepted analytics request is received. There is currently no separate scheduled cleanup job, so deletion can be delayed if the site receives no such requests after a record expires. You may request deletion at any time using the contact email below.
Basic page-load totals: daily totals are kept for up to 24 months and contain no visitor identifiers. Cleanup runs when optional analytics are next recorded or an administrator opens the analytics dashboard; deletion can be delayed during inactivity. Optional analytics: pseudonymous visitor and session records are kept for up to six months. Daily page-view and event statistics are retained for up to 24 months only after each group contains at least five distinct random browser identifiers. The system first stores individual contributions in a short-lived pseudonymous buffer for the current UTC day; groups that do not reach five identifiers are deleted after the day closes. Cleanup runs on the next accepted analytics request or when the admin analytics page is opened; there is no separate scheduled cleanup job, so deletion can be delayed during inactivity. Rate-limit hashes used to limit form submissions are deleted after 24 hours when the next form request performs cleanup.
6. Audience analytics and cookies
Basic page-load count: the site records one aggregate total per UTC day for public page requests, including visits from people who reject optional analytics. It does not retain page paths, visitor identifiers, referrers, country, or device data for this counter. Repeated page loads and automated requests may contribute, so this is not a unique-visitor count.
A first-party cookie remembers whether you accepted or rejected analytics for up to six months. If you accept, a random visitor identifier cookie is also stored for up to six months, and a session identifier is kept in the browser’s session storage. The session identifier is rotated after 30 minutes without activity. The database stores one-way hashes of the visitor and session identifiers, so these records are pseudonymous rather than anonymous. Referrers are reduced to a hostname; location is limited to approximate country and broad region; devices are grouped as mobile, tablet, or desktop.
You can reject optional analytics or change your choice using “Cookie settings” in the footer. Withdrawing consent stops future analytics and deletes your linked pseudonymous visitor and session records, plus any pending daily page-view or event contributions. A daily group that has already reached five distinct browser identifiers is retained only as a non-linked aggregate count; it cannot be removed by identifier afterward. Groups below five are not included in retained aggregates or shown in the dashboard. The five-identifier threshold is a disclosure safeguard, not by itself a guarantee of legal anonymity. The site does not use advertising cookies or cross-site tracking.
7. Technical data and security
The AfRA analytics tables do not store raw IP addresses. Separately, the form rate limiter uses a short-lived hash derived from the request IP address and a 15-minute time window to enforce a limit of five submissions per window. The raw address is not saved in that rate-limit table. The hosting and network providers may process IP addresses and other technical request data to deliver and protect the service.
The private inbox uses the hosting platform’s sign-in service. The backend checks the authenticated email against an administrator allowlist; it does not display inbox data to an unauthorised account. The sign-in provider may use strictly necessary authentication cookies.
8. Your rights and complaints
Depending on the applicable law and circumstances, you may request access, correction, deletion, restriction, or portability of your personal data, and object to processing based on legitimate interests. You may withdraw analytics consent at any time through “Cookie settings”. Contact hello@voroszoltan.hu to exercise a right or ask a question.
You may complain to the Hungarian National Authority for Data Protection and Freedom of Information (NAIH) at naih.hu. Depending on the circumstances, you may also have a right to seek a judicial remedy.
9. Changes to this notice
This notice will be updated if the website’s data processing, service providers, or retention practices change. The controller will complete the open legal assessments and confirm account-specific provider details before treating this working notice as final.
