Electronic Communications Consent

6membership may provide application notices, policy documents, payment records, information requests, decisions, membership documents, renewal reminders, security alerts and other official communications electronically.

Electronic delivery may replace paper delivery where lawful, appropriate and accepted through the applicable process.

An applicant or member may electronically submit information, select a tier, accept a policy, approve a declaration, confirm an email address, authorise a payment or request an administrative action.

The legal and operational effect depends on the wording presented when the action is taken.

A separate channel or document may govern a specialised transaction where additional formalities are required.

Agreeing to electronic communication does not waive a mandatory right, consumer remedy, privacy right or legal requirement that cannot lawfully be excluded.

It does not prevent a person from requesting an accessible alternative where applicable.

The Membership Terms govern the underlying application and membership relationship.

The Privacy Notice governs information used to send and record communications.

The Policy Updates document governs later policy versions and renewed acceptance.

By continuing through an electronic application or another process that clearly presents this Consent, the person agrees that relevant records may be provided electronically.

The agreement applies to the application, membership or request connected with the presented notice.

Consent to receive membership records electronically is not consent to optional marketing, advertising tracking, public use of photographs or unrelated data processing.

Separate optional permissions must be requested where legally or operationally required.

Electronic delivery does not automatically include a physical paper copy.

A printable electronic copy may be supplied where appropriate.

A physical document may be offered separately and may involve production or delivery conditions disclosed in advance.

A person who cannot reasonably access an electronic communication because of disability, technical limitation or another protected circumstance may request an appropriate alternative.

The alternative may include accessible electronic formatting, assisted communication or another reasonable method.

Where applicable law, a court, regulator, financial institution or separate agreement requires a particular physical, witnessed, notarised or formally signed record, the electronic process will not be treated as automatically satisfying that additional requirement.

Policy acceptance may be recorded through a clearly labelled checkbox, button, signature field, OTP confirmation or comparable affirmative action.

Silence, inactivity or merely opening a page will not ordinarily be treated as acceptance where an affirmative action is required.

The acceptance interface must identify the relevant policy or group of policies.

Where several documents are accepted together, their names or understandable short labels must be displayed or linked before acceptance.

The interface must not conceal a material policy behind an unrelated button, preselected optional permission or generic statement that prevents reasonable review.

The principal 6membership application acceptance set is presented in a controlled order so that the applicant can review the documents governing the application, information processing, payment, verification and future policy changes.

Where the production application requires this complete set, the acceptance record should preserve the individual policy identifier and version for each document rather than recording only a generic statement that policies were accepted.

The acceptance record should identify the applicable policy version or publication record.

This allows 6membership to determine which terms were presented when an application, payment or membership action occurred.

A later public version must not overwrite the historical version connected with an earlier acceptance event.

Policies should be accessible before the person completes the acceptance action.

Links should open the correct current document and should not lead to an empty, inaccessible or materially different policy.

Application policy links may open separately so the applicant can review them without losing entered application information.

A mandatory contractual acknowledgement may be presented as a required action before the person proceeds.

An optional consent must not be pre-selected where affirmative consent is required.

Required contractual acceptance and optional marketing consent should not be disguised as one inseparable choice where separate treatment is appropriate.

The person should be able to access or retain the accepted policies through the Legal & Trust Center, application confirmation or another reasonable method.

The public current version may later change, while the historical acceptance record remains connected to the version originally presented.

An electronic signature or acknowledgement may include typing a name, drawing a signature, selecting an acceptance control, entering an OTP, confirming through a secure link or completing another clearly identified action.

The appropriate method depends on the transaction, risk, identity requirements and applicable law.

The interface should make clear that the action is intended to confirm, accept, authorise or declare the identified matter.

A routine navigation button should not be treated secretly as a signature.

6membership may use the registered email address, authenticated session, OTP, device information, timestamp, application reference and related evidence to determine who performed an electronic action.

No single technical record is guaranteed to prove identity in every circumstance.

An ordinary 6membership electronic signature or OTP confirmation is not a government-issued digital identity certificate.

It confirms only the action supported by the available evidence and process.

A substantial investment, equity, board, financing, private-tier or strategic relationship may require a separately drafted and signed agreement.

A standard membership checkbox does not replace signatures, witnessing, corporate approvals, professional advice or other formalities required for that separate agreement.

An OTP may confirm access to an email address, authorise a specific action, verify a session or strengthen confidence that the person completing an action controls the relevant communication channel.

The screen or message should identify the action for which the OTP is intended.

An OTP authorises only the action for which it was issued.

An OTP used to confirm an email address does not automatically authorise payment, public photograph use, marketing or a separate agreement.

An OTP must be entered only into the official interface associated with the requested action.

The recipient must not send the OTP to an administrator, reviewer, social-media account or another person.

An OTP or secure link may expire after a limited period and may be restricted to one successful use.

An expired or previously used code does not authorise a new action.

A person who receives an unexpected OTP or secure link should not complete the action.

The message may indicate an incorrect email address, attempted unauthorised access or another person’s mistake.

Successful email verification confirms control of the email channel at that time.

It does not independently prove legal name, age, photograph, guardian authority, beneficial ownership or payment ownership.

Selecting the final submission action may confirm that the applicant intends to send the displayed application for processing.

The interface should distinguish saving a draft from submitting the completed application.

The applicant may be required to confirm that the submitted information is accurate and not knowingly misleading.

The declaration applies to the information presented at submission and does not prevent correction of a genuine later-discovered error.

A person acting for a household, younger applicant, business or organisation may be required to confirm their identity, role and authority.

Electronic confirmation does not create authority where the person does not actually possess it.

Successful submission may generate an Application Reference.

The reference confirms that an application record exists but does not confirm payment, approval or active membership.

A submitted application may become restricted from direct editing to preserve record integrity.

Corrections may require an authorised update, new declaration, identity re-verification or supporting evidence.

Submitting the same application repeatedly does not create multiple approval rights.

Duplicate records may be linked, restricted or investigated where necessary.

Accepting membership policies does not by itself charge a payment method.

Where payment is required before review, the payer must separately complete the authorised Flutterwave checkout for the displayed amount and currency.

A payment action must remain linked to the correct application and must not be created merely from a policy-acceptance checkbox.

Before authorisation, the payer should receive the selected tier, billing period, amount, currency, tax treatment and material refund or renewal information.

The checkout should identify Flutterwave as the production payment integration and should state that payment does not guarantee application approval.

For a one-time membership option, the final duration and continuity conditions must be displayed before the payer can authorise payment.

Flutterwave, a participating bank, card issuer, mobile-money provider or another financial institution may require its own OTP, PIN, approval or authentication step.

That authentication is governed by the relevant provider or institution and must not be disclosed to 6membership staff.

6membership staff must not ask a payer to send a payment OTP, banking password, card PIN or card security code by email, telephone, social media or an administrator message.

An ordinary monthly, yearly or one-time payment does not by itself authorise future recurring charges.

Automatic renewal may occur only where the payer receives clear recurring-payment information and expressly authorises the arrangement.

A stored transaction reference or earlier policy acceptance must not be treated as a future recurring-payment mandate.

6membership may retain the Flutterwave transaction identifier and reference, the internal transaction reference, amount, currency, payer or customer details, verified status and other limited records necessary for payment administration.

A Flutterwave browser redirect, success page, screenshot, debit alert, applicant statement or webhook payload alone is not final proof that the correct payment succeeded.

Before an application is treated as paid or membership value is granted, trusted server-side logic must independently verify the transaction with Flutterwave and confirm the expected status, amount, currency, transaction reference and relevant customer or application relationship.

Flutterwave webhook requests must be authenticated using the provider-supported signature mechanism before they are trusted for processing.

Because provider callbacks and webhooks may be retried or delivered more than once, payment and refund event handling must be idempotent or use equivalent duplicate protection.

Where a webhook is delayed, missed or inconclusive, 6membership may re-query Flutterwave or use another authorised reconciliation process rather than assuming success or failure.

An internal decision approving a refund is different from submitting the refund to Flutterwave, Flutterwave accepting or processing it, and the refund reaching its final provider status.

A message must not state that a refund was submitted or initiated before the authorised Flutterwave process has accepted the refund request.

Provider statuses such as new, pending, succeeded or failed may be recorded where applicable, and a communication must not describe a refund as finally completed unless the verified provider record supports that conclusion.

A financial institution may require additional time to display a refund after Flutterwave reports the applicable completed or successful provider status.

The initial private 6clement Joshua consideration request does not require an immediate membership payment.

The electronic request must not contain a payment authorisation or imply that payment is required merely to submit the initial private consideration request.

Any later payment, investment, equity, financing or commercial arrangement requires the separate authorised process and documentation applicable to that relationship.

Payment verification, refunds, chargebacks, renewal rules and Flutterwave provider processing are governed by the dedicated payment and service-provider policies.

Where a permitted younger applicant requires parent or guardian involvement, the guardian may receive an electronic approval request.

The request should identify the younger applicant, relevant membership process and action being approved.

The guardian may be required to confirm their identity, relationship and authority.

Electronic approval does not validate a false guardianship claim.

The guardian should be able to review the relevant application information and policies before approving.

The younger applicant must not secretly complete the guardian confirmation using the guardian’s email or device.

The applicant’s submission and the guardian’s approval should remain distinguishable records.

One action must not be recorded falsely as though both persons completed it.

A guardian may request cancellation or withdrawal according to the applicable age, application, privacy and membership rules.

Withdrawal does not necessarily require deletion of payment, fraud-prevention, legal or historical records.

An electronic acceptance record may include the policy slug, version, acceptance time, Application Reference, Membership ID, user or applicant identifier, registered email and action performed.

The record may also contain an Internet Protocol address, browser or device information, session identifier, request identifier and security events where proportionate.

Technical information supports attribution and integrity but must not be treated as infallible identity proof.

Transactional email may be delivered through Resend. Official email records may include the sender, recipient, subject, message body, Resend or other authorised provider message ID, timestamps and delivery events.

Internal and provider records may distinguish generated, queued, provider-accepted, delivered, bounced, rejected and complained-about states where those states are available.

A provider-accepted or delivered status does not guarantee that the recipient personally opened, read or understood the message.

OTP records may identify that a code was generated, sent, expired, rejected or successfully used.

The ordinary record should not retain the usable plaintext OTP longer than operationally necessary.

Material acceptance and communication records should be protected against unauthorised alteration.

An ordinary applicant or member must not be able to rewrite an historical policy version, acceptance time or administrator action.

An electronic record may be challenged where there is credible evidence of account compromise, technical error, impersonation, unauthorised access or incorrect attribution.

6membership may examine the complete record and surrounding evidence rather than relying on one log entry alone.

Payment evidence may include the 6membership transaction reference, Flutterwave transaction identifier, verified amount and currency, verification time, authenticated webhook event, refund identifier, provider status and relevant reconciliation events.

The record should preserve enough information to establish the transaction outcome without storing full card numbers, card security codes, banking passwords, payment PINs or usable payment OTPs as ordinary 6membership records.

Repeated webhook or callback deliveries may be recorded for idempotency, troubleshooting and audit purposes without creating repeated payment value or repeated refund actions.

Policy documents, application notices, verification information and other communications may be displayed through the official 6membership website.

A copied page, unofficial domain or impersonating website must not be treated as an official communication.

6membership may send official communications to the email address registered with the application or membership.

The person is responsible for maintaining reasonable access to that address and reporting a material change.

A communication may contain a secure link to view or complete an action.

The recipient should verify the sender and destination before entering information.

A secure link may expire or become invalid after use.

Where implemented, an authenticated application or membership page may display notices, records and required actions.

A dashboard notice may be supplemented by email where the matter is important.

An informal social-media post or personal message is not ordinarily the official channel for policy acceptance, identity-document submission, payment instructions or final membership decisions.

A public social account may direct a person to the authorised website or official email but should not replace the protected process.

Resend supports transactional email delivery, while other approved hosting, network and infrastructure providers may support the electronic service.

An approved provider may process routing, delivery, security, diagnostic and limited message information necessary for its assigned role.

Flutterwave separately supports payment-related electronic events, transaction verification, refund processing and payment-status records.

A generated or sent status means 6membership created or submitted the communication through the authorised delivery process.

It does not necessarily mean that Resend or another authorised delivery provider accepted the message or that the recipient’s destination system received it.

Provider acceptance means Resend or another authorised delivery provider accepted the message for processing.

It does not guarantee inbox placement, personal review, successful display on every device or final delivery where a later bounce or rejection occurs.

A delivered status means the provider reports successful delivery to the destination system.

The recipient may still miss the message because of filtering, account access, mailbox rules or another issue.

A failed, bounced or rejected message may require correction of the address or another communication method.

6membership may ask the person to verify or update their contact information.

A communication takes effect according to the applicable policy, transaction, legal rule or date stated in the notice.

A policy change is not necessarily effective merely because an internal draft was created or an email was prepared.

For a material denial, refund, suspension, policy change, privacy incident or other important matter, 6membership may use more than one appropriate electronic channel.

The method should reflect the significance, urgency and available verified contact information.

The applicant must provide an email address they are authorised to use and can access.

Using another person’s address without authority may expose private communications and prevent proper verification.

A member should report a change or loss of access to the registered email address promptly.

A contact change may require identity verification before protected records are redirected.

The person should protect the registered email account and devices through reasonable security measures.

A compromised email account may allow another person to view notices or attempt unauthorised actions.

Applicants and members should review spam, junk and filtered folders where an expected message is missing.

Adding an official sending address to permitted senders may improve delivery but does not guarantee it.

A person using a shared or public device should sign out, close sensitive pages and avoid saving private records unnecessarily.

Local downloads and browser history may remain accessible to another device user.

A person should not follow an unexpected payment, password, OTP or identity-document request without verifying the sender and destination.

Suspected phishing or impersonation should be reported through the official security channel.

6membership may send communications reasonably necessary to administer an application, payment, membership, security matter, privacy request, complaint or legal obligation.

These messages may continue where their processing relies on contract, legal obligation, security, legitimate interests or another applicable lawful basis.

The fact that a necessary message is sent by email does not automatically make it marketing.

Promotional communications unrelated to necessary administration will use an appropriate lawful basis and provide an opt-out where required.

Optional marketing consent must not be hidden inside an unrelated mandatory application declaration.

A person may withdraw or opt out of covered optional marketing.

The preference may take a reasonable operational period to apply to communications already prepared or in transmission.

Withdrawing from optional marketing does not prevent essential application, payment, security, membership, privacy or legal communications.

Consent to optional browser technologies does not automatically authorise promotional email.

An email-marketing choice does not automatically alter browser cookie settings.

Where personal-information processing relies on consent, the person may withdraw that consent through the applicable privacy or preference channel.

Withdrawal does not invalidate processing that was lawful before withdrawal.

Withdrawal of consent does not automatically stop processing required for contract performance, fraud prevention, payment records, legal obligations, security, complaints or legal claims.

The applicable Privacy Notice explains the relevant processing grounds.

A person may request an available alternative delivery method for future communications.

The request may require identity verification and may not apply where the service can reasonably operate only through an electronic process.

Where electronic communication is essential to secure application or membership administration, refusing every available electronic method may make the service impractical or unavailable.

6membership should explain the material consequence before ending or restricting the process where reasonably possible.

Where an optional physical document is requested, a disclosed production or delivery charge may apply.

A charge must not be used to prevent access to a record that applicable law requires to be provided without charge.

Changing future delivery preference does not require deletion of earlier electronic communications, acceptances or evidence that must lawfully be retained.

Applicants and members should verify that website links use the authorised 6membership domain and that official messages originate from recognised addresses.

A similar-looking domain or display name may be used for impersonation.

A person must not create or alter an email, approval, receipt, policy acceptance, card, certificate or verification page to make it appear that 6membership issued or accepted it.

A person who believes an application, acceptance, payment, contact change or other action occurred without authority should report it promptly.

6membership may restrict the affected process while the report is investigated.

Relevant email, OTP, session, device, payment, application and audit records may be reviewed to determine what occurred.

Access should remain limited to authorised personnel.

Use of a correct email address, device or OTP does not automatically resolve every allegation of compromise or coercion.

The complete circumstances and available evidence should be considered.

Protective action may include expiring links, disabling sessions, changing contact details, rotating credentials, pausing payments, restricting a card or requiring renewed verification.

Electronic communication records may contain names, email addresses, application references, Membership IDs, policy versions, message content, timestamps, delivery status, device information and security events.

Records may be processed to deliver communications, demonstrate acceptance, administer applications, resolve disputes, prevent fraud, respond to rights requests and comply with legal obligations.

Approved providers may process electronic records for assigned functions, including Resend for transactional email delivery and Flutterwave for payment, refund and transaction-status processing.

Hosting, database and network providers may also process communication metadata needed to operate, secure and record the service.

The relevant providers and their roles are described in the Third-Party Service Providers List.

Acceptance and communication records may be retained for application administration, membership history, payment disputes, security, accountability, legal obligations and claims.

The appropriate period depends on the record and associated relationship.

Applicable privacy rights may allow deletion or restriction of particular communication information.

A request may be limited where the record must remain to demonstrate a policy acceptance, payment authorisation, fraud event, status decision or legal obligation.

A person may exercise applicable access, correction, deletion, restriction, objection, withdrawal and complaint rights through the official privacy process.

6membership may publish a new policy version where legal, operational, provider, security or membership requirements change.

The new version should identify its publication and effective information.

A typographical correction, clearer explanation, updated contact address or change that does not materially alter rights and obligations may not require renewed acceptance.

A material change may include a substantial new obligation, payment term, public-information use, dispute provision, recurring charge or processing purpose.

The significance must be assessed according to the affected relationship and applicable law.

Where renewed acceptance is legally or operationally required, the member may be asked to review and affirmatively accept the new version.

The record should identify the new version and acceptance action.

A later policy will not be used retrospectively to authorise an earlier unauthorised charge, invalidate a mandatory right or convert an unlawful action into a lawful one.

Where a material policy update is necessary to continue a future service lawfully, refusal may prevent renewal or continued use of the affected feature.

The effect should be explained clearly and mandatory existing rights remain preserved.

A person may report an expected communication that was not received, was sent to an incorrect address or contained inaccessible or incorrect information.

6membership may review delivery and account records and may resend or correct the communication where appropriate.

A person may dispute an electronic acceptance, signature, OTP use or application submission they believe was unauthorised or incorrectly recorded.

The complaint should identify the affected action and available supporting information.

6membership may review the relevant policy version, acceptance record, email, session, OTP, payment and security evidence.

A confirmed error should be corrected while preserving an appropriate audit trail.

An applicant or member may use the official complaint process to challenge an electronic communication or record outcome.

A serious security restriction may remain temporarily while the complaint is assessed.

Nothing in this Consent removes a mandatory right to contact an applicable consumer authority, privacy regulator, court, financial institution or other competent body.

Application, acceptance, payment and decision communication questions may be sent to applications@6membership.com.

Approved-membership records, cards, certificates, renewals and status communications may be sent to admin@6membership.com.

Privacy requests may be sent to privacy@6membership.com.

Suspicious links, phishing, exposed credentials and unauthorised electronic actions may be reported to security@6membership.com.