Privacy
How data is used — updated September 3, 2026
Controller and contact
Youth For Challenge, Lokossa, Benin. For data questions or access, correction and deletion requests: contact@youthforchallenge.africa. Institutional information and legal processing arrangements must be confirmed by the association before production launch.
Forms and requests
Information you submit is stored on the server to handle contact, volunteer and civic proposal requests. A notification may be sent to staff through Resend. Do not include medical information, identity documents or information about third parties in free-text fields.
Donations and orders
Orders record the amount, status, references and contact details needed for processing. Card data and payment codes are entered with FedaPay, never in our forms. The provider confirms transaction status. The shop is enabled only after delivery terms are defined.
Newsletter
Your email address remains pending until you confirm by email. Every campaign must provide an individual unsubscribe link. Confirmation links expire after 24 hours. You may also contact the association directly.
Registers and cards
Public verification shows only the approved recipient label, document title, dates and status of a verified record. Publication requires explicit consent recorded by an operator. Named cards require a private access token; no medical data is published.
Polls, local storage and security
A technical yfc_voter cookie, valid for up to one year, limits votes per browser; it does not verify a person’s identity. Theme, motion preferences and learning progress may be stored in your browser. Abuse prevention uses a network-address hash when the proxy is configured; counters expire after one minute. Offline caching stores only an unavailable page.
Access, providers and retention
Server data is restricted to authorized operators. Configured providers may include the host, Resend for email and FedaPay for payment; external links have their own policies. Retention periods for requests, orders and backups must be defined and documented by the association according to purpose and obligations before public launch. This notice describes code behavior and is not a compliance certification.