Who is responsible
The data controller is SoApp Social SAS, 27 Grande Rue, 78580 Les Alluets-le-Roi, France. For privacy questions or to exercise a right, email contact@soappsocial.com.
Data we handle
- Newsletter and waitlist registrations: the email address submitted, consent wording and version, signup source and timestamps. A waitlist address is not treated as mailbox-verified.
- Supporter and MOU submissions: identity, email address, role, affiliation or organisation, website, optional statement or proposed discussion, authority confirmation, chosen support status, publication choices, typed confirmation and timestamps.
- Review records: verification status, private reviewer notes, consent versions, supporting evidence, moderation decisions and withdrawal history.
- Public supporter profiles: only the approved name, status and optional fields the supporter has permitted SoApp to publish.
- Security and delivery data: IP address and request, browser or device information processed in technical logs. A one-way network identifier derived from request information may also be used to limit abusive submissions.
- Reviewer access: authenticated account identifiers and professional contact details used to restrict the private review area where that access is enabled.
- Financial contributions: the selected euro amount and one-off or monthly frequency, checkout and subscription references, payment and renewal status, cancellation state and related timestamps. Stripe collects the payment and contact details required for its hosted Checkout and billing portal. The website’s marketing database does not store full card details or copy a contributor’s billing email into the newsletter.
- Campaign attribution: where present in the page URL, short source, medium, campaign and content labels and the selected SoApp destination can accompany a waitlist or supporter submission. These tags help us understand which links bring responses. They are visible only to authorised reviewers, are not verified identities, and are never published on supporter profiles. We keep the first signup’s tags for a waitlist address; older or untagged entries remain unknown.
The form identifies which fields are required. Optional context is not needed to submit unless it becomes necessary for the status selected.
The supporter form includes a separate, optional newsletter and waitlist choice. Only selecting that choice adds the email address to the list; submitting support alone does not. Signing up is single opt-in, with no confirmation email. When newsletter delivery is enabled, the website synchronises opted-in addresses with Brevo, the mailing service used to compose and send updates. Unsubscribe, complaint and delivery-suppression information is kept in sync so excluded addresses are not deliberately mailed. This choice is independent of whether your support is public or private. Use the unsubscribe link in an email or contact us to leave the list. A website unsubscribe is saved before background synchronisation with the mailing service.
Why we use it, and the legal basis
| Purpose | Legal basis |
|---|---|
| Maintain the waitlist and send the requested product, launch and community updates | The subscriber’s consent, which may be withdrawn at any time |
| Receive, assess and verify support or collaboration enquiries | Legitimate interests in operating SoApp and responding to genuine enquiries |
| Discuss a possible MOU, research relationship or future pilot | Steps requested before a possible agreement and, where relevant, legitimate interests |
| Publish an approved supporter profile or statement | The supporter’s consent, which may be withdrawn at any time |
| Protect the website, limit abuse and control reviewer access | Legitimate interests in security and service integrity |
| Keep proportionate consent, review and withdrawal evidence | Legitimate interests in accountability and the establishment or defence of legal claims |
| Understand which campaign links lead to submitted registrations or enquiries | Legitimate interests in understanding and improving SoApp’s communications; you may object |
| Process the contribution you request, show payment status and manage recurring support | Performance of the contribution arrangement you request |
| Keep required payment/accounting records and address payment disputes or fraud | Legal obligations where applicable and legitimate interests in accountability, fraud prevention and legal claims |
Who can receive the data
Access is limited to authorised SoApp personnel and service providers that support website delivery, the SoApp API, database operation, authentication, communications and security. The public sees only an approved supporter profile’s permitted fields.
Supporter and MOU submissions are queued for an internal notification to contact@soappsocial.com so authorised staff can verify the person and review the request. When email delivery is configured, Brevo delivers that notification, including the submitted contact information and statement. This does not subscribe the submitter to updates. Publication remains subject to review and the relevant permission.
The public website is delivered through Amazon Web Services infrastructure and submits waitlist and supporter information to the SoApp API, which stores the website records in a dedicated marketing database. Professional advisers or public authorities may receive limited data where reasonably necessary or legally required. SoApp does not sell supporter or waitlist data.
When contributions are enabled, Stripe provides hosted payment processing and recurring-billing management. It receives the information needed for payment, authentication, fraud prevention and its legal obligations. Read Stripe’s privacy policy for its handling of information on those pages. A contribution does not automatically create a public supporter profile or newsletter registration.
International processing
Some service providers used by SoApp may process or support data from outside the European Economic Area. Where European data-protection law requires it, SoApp uses or requires an appropriate transfer mechanism and safeguards under the relevant service arrangement.
How long we keep it
- Active newsletter and waitlist registrations: while updates are requested, subject to a retention review and a limit of three years after the last meaningful interaction.
- After unsubscribing or a delivery suppression: delivery stops; a limited exclusion and consent record may be kept for three years to prevent accidental re-enrolment and document the choice.
- Campaign tags attached to a submission: retained with that submission and removed when it is deleted. No separate individual browsing history is kept for campaign attribution.
- Private, unpublished, rejected or inactive supporter and MOU submissions: up to three years after the last meaningful exchange or review.
- Published supporter profiles: while publication permission remains active.
- After a valid withdrawal: public display stops promptly; a limited record of the permission, verification, decision and withdrawal may be retained for three years.
- Security, abuse-prevention and server logs: retained only for the operational, security or legal period needed for their purpose.
- Contribution, checkout and subscription references: kept while needed to process the contribution, manage an active subscription, resolve a payment issue or meet applicable accounting and legal obligations. Stripe holds the full payment/billing record under its own retention arrangements. SoApp reviews the need for the related marketing records separately from newsletter consent.
SoApp reviews these periods operationally; personal records are not automatically purged on a timer. A verified deletion request removes the relevant supporter record and its notification job, or excludes the newsletter address from delivery and queues its removal from the mailing service. Staff also review any delivered notification copies in the contact mailbox and mailing service when handling deletion. Completed notification jobs discard their contact information and statement; their technical delivery reference expires after 90 days. Pending or failed notifications retain the information needed to deliver or investigate them until resolved or the submission is erased. For newsletter deletion, the address is retained while that removal is pending, then anonymised locally after the service confirms removal. During a service outage, cleanup can remain pending and is tracked for retry. Data may be kept longer where the law requires it or where it is necessary for an active dispute, investigation or legal claim.
Your choices and rights
Depending on the situation, you may ask for access, correction, deletion, restriction or portability of your data, object to processing based on legitimate interests, or withdraw publication consent at any time. Withdrawing consent does not affect earlier lawful processing.
Campaign tags travel in links without measurement cookies or browser storage. We omit them from submissions when the browser communicates Do Not Track or Global Privacy Control. You can also remove the campaign parameters from the page URL before submitting, or ask us to remove stored campaign tags.
The contribution return page uses a payment-status token in your tab’s session storage, described in the cookie notice. Monthly-support management uses Stripe’s authenticated customer portal. Cancelling recurring payments is separate from unsubscribing from the newsletter or requesting deletion of a SoApp account.
Email contact@soappsocial.com and include enough information to identify the relevant submission. SoApp may ask for proportionate identity evidence before acting on a request. You may also complain to the CNIL, the French data-protection authority.
Automation and changes
Supporter publication decisions are not made solely by automated means, and this public website does not use personal data for behavioural advertising or profiling.
This notice will be updated when the public website’s processing changes. Processing within an authenticated SoApp app or web account is outside the scope of this notice and is described separately. For current browser-storage information, read the cookie notice.