Organisation terms
This text applies only to the organisation role. How the organisation pot is calculated from P sits in the terms. Which data the application stores sit in the privacy notice. The step-by-step interface sits in the organisation guide.
Information phase · Translations and operational release under reviewUpdated: September 15, 2026Who the contracting party is
The contracting party on your side is only the legal person named in the application. Umbrella bodies and legally separate national offices are reviewed separately. Membership of an association does not create a right to receive for its other members.
The acting person states that they are authorised to apply and later to accept allocated amounts. An application creates no right to admission, to a given visibility or to a minimum donation volume.
Organisation accounts do not buy. Guests and admin accounts do not buy either. Anyone who wants to buy from an organisation context needs a separate buyer or seller account.
Application, evidence and why submit can stay blocked
Submission checks required fields, evidence, at least one unblocked bank account and released agreement texts. The German drafts of the partnership and the extra organisation privacy notes are stored but deliberately not released. Without release, submit stays blocked. That is not a silent acceptance.
Among other fields, registered name, display name, form, country, founding, register authority, public-benefit status, receiving legal person, contact name, function, email, phone, language, seat, public email, short text, description, mission, website and scope of activity may not stay empty. A registration number or a reason for its absence must be present. Countries of activity or a confidential country reason must be present. The contact mail must match a confirmed member mail.
The server check requires valid documents for registration, statute, representation, public benefit and partnership. Supported types are PDF, JPG, JPEG, PNG and WebP up to 10 MB. SVG is rejected. Refused or expired files do not count. Public redacted versions need a separate release.
Which steps the application has
The application runs in eight steps: identity, contacts, locations and countries, description and media, documents, bank accounts, agreements and submission. Drafts are saved with a delay. Versioning detects competing changes. Submitted versions stay traceable.
You may add evidence after account creation in the organisation area. Photo and document choice including a mobile camera are available in the registration step. A stored draft is not certification and not a right to receive.
Country fields use a selector with the supported territories. Website addresses need no typed HTTPS prefix but must mean a reachable public page. The public username is checked for availability as you type.
Members and confidentiality
Owner, editorial, finance and read-only have separate rights. Invitations attach to the confirmed email and can be withdrawn. Memberships in several organisations are possible. There is one application per founder account.
Keep the list current and remove access for people who have left. Files already downloaded cannot be pulled back. Admins cannot approve their own organisation as members. Confidential bank data, protected locations and internal notes do not belong in public profile text.
Owners manage rights and submission. Editorial maintains public text, media and appeals. Finance sees accounts and evidence for payout. Read-only sees without editing. One person may hold several roles but cannot replace review of their own organisation.
Payout account
Payouts go only to reviewed accounts of the entitled legal person. SEPA requires euro and a valid IBAN. BIC may be missing on SEPA. International paths need IBAN or a local account number plus the remaining required fields. Do not enter passwords, PINs or TANs.
New accounts and changes need a new review. Confirmed payout also needs reviewed proof of account ownership and the later payment-provider state. That state cannot be set successfully without a connection. Different currencies are not added together without an agreed conversion.
The account must match the receiving legal person, not a private helper. Third-party client accounts without visible authority are not accepted. An internal finance release in your file does not replace the shared block check in the terms.
Receiving and payout are separate
Receiving needs certification and an active receive release. Payout needs a confirmed bank account, accepted evidence and the later provider state. Organisation shares also need the manual release in the organisation file. Prepared plans of blocked organisations get a review note, not a silent transfer.
The shared block reasons after receipt, return and open cases sit in the terms. Here only this: your internal release does not replace that check. An auction award or a calculator display is not money arrived with you.
Profile publication, receiving donations, payout, bank review and project status are independent decisions. A visible organisation card does not mean payouts are running. An internal administration note is not a transfer.
Purpose binding, appeals and general support
Sellers may choose you generally or with a released project. A one-country project uses funds only for the stated country and purpose. Several countries with shared use do not promise exclusive use in one of those countries.
In the dashboard you may create appeals with purpose, photo and countries or worldwide. General support without a single project can be switched on separately. The assignment then goes to the organisation, not to a purpose-bound country pot. An appeal is not a booked donation and not a tax certificate.
Later profile changes do not change earlier assignments retroactively. If use becomes impossible you inform LuxCharity at once and keep the affected funds separately traceable. There is no automatic redirect to other purposes.
Projects, contacts and translations
Projects need a purpose, a clear description and the permitted countries or the worldwide mark. Photos follow JPEG, PNG or WebP. The hint names 5 MiB. The server accepts up to 10 MB and rejects SVG. Images are re-encoded.
Several contacts per country with function, address, email and phone stay internal unless you expressly publish them. Changes check the version. Sensitive protected locations do not belong in public text.
Translations are reviewed as new records. The original language remains. There is no duty to file every language and no automatic translation on page view. An old translation release does not cover a changed source text.
Reports and tax limits
You use received funds lawfully and within the documented purpose. On a reasoned request you explain the use of project-bound funds. Sensitive data about beneficiaries do not belong in public reports.
A platform approval does not claim worldwide deductibility. Tax statements need country, issuing body, period and accepted evidence of the same organisation. Expiry withdraws a public tax statement. Payment confirmations distinguish planned share, assignment, confirmed money flow and arrival with you. That is not an automatically recognised donation certificate.
Public reports may describe results without making individual beneficiaries identifiable. You handle internal follow-up requests with a field reference and a deadline in time. Evidence not filed in time can stop receiving or payout.
Messages, name and media
Owner, editorial and finance may write to LuxCharity or to parties of a booked donation event. Text and an optional PDF or image leave only after send. PDF, JPG, PNG and WebP up to 10 MB. Images are stored as WebP. Private downloads last 60 seconds and only for current conversation members.
For the time of published participation you grant LuxCharity a simple right to show expressly released names, logos and media on the agreed surfaces. Uploading confidential evidence does not grant a publication right. After the end, new publicity uses stop. Legally required evidence may stay to the needed extent.
Logos and public images need rights details, author and alternative text where the surface requires it. A separate public redacted version is not a substitute for the complete private evidence file.
Review, follow-up and internal files
Administration may demand follow-up with a field reference and a deadline. Refusal is not certification. A new state stays versioned. Nobody releases their own organisation. Internal notes, review chat and document preview stay internal.
Branches and legally separate offices need their own evidence if they themselves want to receive. An umbrella mark in the logo does not replace that. Public empty result lists must not be filled with invented partners.
Technical access blocks for a missing session or a missing role are not a substance refusal. An HTTP error without login creates no right to a silent release.
Change, block and end
You report material changes to identity, representation, accounts, purposes and countries at once. Functions may be restricted on reasoned abuse, missing entitlement or an unsuitable payment path. New assignments to blocked recipients are prevented. Existing purpose bindings are not deleted and not redirected automatically.
You may ask to end participation through the organisation area or aifae.org@gmail.com. New assignments end after handling. Payments, reversals and evidence duties are closed in order. The guide does not invent a successful end while agreement texts are not released.
After the end, legally required evidence and financial history remain. Public appeals and new publicity uses end. Members lose access once the end is handled, unless a legal duty requires a mailbox for longer.