Collect less. Explain it clearly. Keep control with the person.

Supporters

What the recurring support record contains

When you choose ACAIF support seats, the website records the information needed to create and administer the subscription: first and last name, city, email, WhatsApp number, individual or group status, group or organisation name where applicable, seat quantity, monthly or annual cadence, accepted terms version, communication preference and timestamps.

ACAIF also stores the Stripe identifiers and payment metadata needed to match checkout, subscription and invoice events to the supporter record. This can include customer, subscription, checkout-session and invoice references, subscription status, price, quantity, currency, amounts and receipt or invoice links. Full payment card numbers and card security codes are not stored by the ACAIF website.

Transactional messages about checkout, payment, failed payment, cancellation or other subscription administration do not depend on optional research and supporter-update consent.

Pledges

What a pledge record contains

ACAIF records the information needed to operate Pledge 1% for Human Progress: name, email, pledge type, pledge basis, optional organisation, title, location and public link, public/private preference, optional statement, the terms version accepted, consent timestamps and relevant source attribution.

Email is used to reduce duplicate person records and to send transactional pledge communication. Public pledge pages never expose the participant's email address.

Organisation and team pledges may be held for review before public publication to reduce impersonation. Public participation does not mean ACAIF endorses, accredits, certifies or formally partners with a participant.

Volunteering

Matching time and expertise to real work

Volunteer registration may include name, email, optional WhatsApp number, city, organisation, role, contribution area, availability, relevant expertise and information supplied for matching. ACAIF uses these details to assess fit, contact the person about suitable work and manage participation. Registering interest does not guarantee placement.

Broader ACAIF updates are optional and recorded separately from the information needed to manage a volunteer relationship.

Institutional participation

Information supplied by organisations

Institutional participation enquiries may include the contact person's name, work email and title, organisation, organisation type, geography, contribution route and the context provided about the intended work. ACAIF uses these records to route, assess and manage the conversation. Major Gifts records remain separate where the primary purpose is a larger, restricted, multi-year or endowed contribution.

Community

Marketing and community communication is optional

Community updates require a separate communication preference. A person can make a pledge or submit an institutional enquiry without agreeing to broader research, campaign or community email. Transactional messages needed to operate a pledge or enquiry do not depend on newsletter subscription status.

Community confirmation email includes a private preference link that can turn these updates off or on without affecting a pledge, payment or enquiry. After opt-out, ACAIF retains the minimum suppression information needed to respect the choice.

Enquiries

Information submitted to contact ACAIF

Standard website enquiries may include name, work email, organisation, stakeholder category, message and source page. Accepted website enquiries are normally retained for up to 90 days.

Major Gifts

Institutional giving conversations need context

Major Gifts enquiries may include name, work email, organisation, the type of giving structure being considered and the context you provide. ACAIF uses this information to manage the conversation.

Payments

Stripe handles payment credentials

Where ACAIF enables Stripe-hosted checkout, payment details entered into Stripe are processed within Stripe's systems. ACAIF may retain the payment references and financial metadata needed for receipts, reconciliation, refunds, recurring contribution administration, disputes and legally required financial records. The public website does not store full card numbers.

Retention

Records are kept according to what they are for

• Enquiries: up to 90 days in the website enquiry store.
• Volunteer records: retained while an offer is being reviewed, matched or used in active participation. Closed volunteer records may be retained for a reasonable period to preserve participation history, safeguarding, governance and future re-engagement context where appropriate.
• Institutional participation enquiries: retained while the conversation is active and for a reasonable relationship, governance or accountability period after closure.
• Active support subscriptions: retained while support is active and for the financial, audit, fraud-prevention and legal periods applicable after it ends. Payment and subscription references may remain even when optional communication preferences are removed.
• Active pledges: retained while the pledge is active so ACAIF can maintain the commitment, consent record and public/private state.
• Withdrawn pledges and public profiles: removed from public presentation; limited internal history may be retained where reasonably necessary to record withdrawal, prevent misrepresentation or meet legal obligations.
• Community preferences: retained while the person has asked to receive updates. On opt-out, the website removes unnecessary name, source and campaign-attribution fields and keeps the email, opt-out state, consent history needed to respect suppression and the private preference credential.
• Major Gifts enquiries: active conversations are retained while they are being managed. Closed Major Gifts enquiries are normally retained for up to 730 days unless a legal, financial or governance obligation requires longer retention.
• Data-rights requests: active requests are retained while being handled. Requests marked Completed or Closed are scheduled to expire from the website request store after 365 days.
• Team invitations: unaccepted invitation records expire after 180 days. Accepted invitation records expire 30 days after acceptance; team membership itself is held on the active team and pledge records.
• Journey analytics: privacy-minimised first-party event records expire after 180 days. They do not contain submitted email addresses, pledge statements, card details or Stripe customer identifiers.
• Operational alerts: private website failure alerts expire after 30 days. They are designed to record the problem, not copy the visitor's submitted form content.
• Financial records: retained for the periods ACAIF is legally or financially required to keep them.
• Unsubmitted form drafts: some guided participation forms may use browser session storage to prevent unnecessary retyping. Consent checkboxes are not restored automatically.

Your choices

Correct, update, withdraw or ask for relevant information

You may ask ACAIF to correct information, update a public profile, withdraw a public profile, change communication preferences, obtain relevant personal information or request deletion where legally permitted. ACAIF cannot promise deletion of records it is required to retain for legal, financial, fraud-prevention or governance purposes.

Use the data request form to ask ACAIF to correct, update, withdraw, access or delete eligible information. If the form is unavailable, write to partner@acyberschool.com and include a pledge or enquiry reference where you have one.

Providers and security

Service providers and security

Cloudflare hosts the website, Worker runtime and current website data stores. Resend is used for transactional email. Stripe provides hosted payment functionality where enabled. Public forms use server-side validation, same-origin checks, spam traps and rate controls. External URLs are limited to normal web links. API keys, payment secrets and administrator credentials are not placed in frontend code.

ACAIF does not intentionally send email addresses, private pledge statements, telephone numbers, private contribution information or Stripe identifiers into public analytics event names or page URLs.