bRAINdrop Privacy Policy
This Privacy Policy explains how bRAINdrop handles participant information, contributions and communications.
Last updated: 16 November 2026Who operates bRAINdrop
bRAINdrop is operated by Paul Downing for the purpose of this pilot. It helps groups contribute their thinking to a shared question, called a Drop, and brings approved contributions together into a collective report.For privacy questions or requests concerning your personal information, contact [email protected].
Information we process
Depending on how you use bRAINdrop, we may process your name, where supplied, and information about the Drop you participate in. If you choose to receive communications, we may process your email address or phone number. For invitations, the Drop organiser may supply your name and invitation contact details.Contribution information may include voice recordings, transcripts, original typed input, cleaned representations, your edits, approved contributions, and versions retained for provenance and pilot review.We also process Creator account information, Drop questions and supporting context, collective findings and report files, including generated audio where available.Operational information includes participation and approval status, timestamps, communication preferences, destination-verification records, private-access records, message identifiers and delivery status. Technical information necessary to host, secure and troubleshoot the service may also be processed. Session cookies support sign-in and private participant access.
Your contribution, review and approval
You can contribute by voice or text. Voice contributions are transcribed, and bRAINdrop prepares a cleaned representation for you to review. You can review and edit that representation before approving it.Preparing or saving a draft does not approve it for collective synthesis. Only eligible, approved contributions become part of the collective Evidence Set when a Drop closes. Incomplete and unapproved contributions are excluded. If an approved version exists alongside a later unapproved draft, the eligible approved version remains the source.Exclusion from synthesis does not automatically delete draft or source records. Approved contributions remain protected in a private source layer, with access restricted according to the service’s operational controls.
What the Drop Creator can see
The Drop Creator can see permitted participant names, participation statuses, aggregate lifecycle information and the released collective report.Operating a Drop does not give the Creator access to participant-managed private contact details, original recordings, full transcripts or individual private contributions. Creators can review contact information they themselves supply for invitations.Direct contact details and private-access credentials are excluded from collective outputs. Participant self-identification is not automatically reproduced in reports. Substantively necessary named entities may remain where context requires them, so we do not promise that every finding will be anonymous or impossible to recognise.Authorised bRAINdrop personnel may access approved representations for synthesis and review, and retained source material for limited controlled-pilot fidelity checks, troubleshooting or support.
Collective synthesis
bRAINdrop processes approved contributions to generate collective findings. These may describe agreement, disagreement, consequential minority perspectives, conditions, qualifications, missing information and other findings relevant to the Drop question.AI services assist this processing, and collective reports follow the pilot’s review and release controls. The purpose is to represent the group’s thinking, rather than rank participants or create individual personality profiles.Private contact information and communication records are not part of the synthesis evidence.
Optional email communications
You can select No return messages and participate without supplying contact details.Where selected and available, email may be used for destination verification, private return links, reminders and delivery of a copy of your approved contribution. Creator-reviewed invitations may also be delivered by email.Private communications use the service’s permission and destination-verification controls. Requesting or receiving a copy is separate from contribution approval and inclusion in collective synthesis.
Optional WhatsApp communications
WhatsApp is optional and is available only where the service is operational. It is not required to participate.If you choose WhatsApp, your phone number, message-routing information, verification records and delivery information are processed as necessary to provide the communication. If you request an approved contribution copy through WhatsApp, your approved contribution may be delivered as a private document through that channel.For incoming WhatsApp messages, bRAINdrop’s webhook retains limited operational information, including the sender number, message identifier, message type and timestamp. It discards incoming message text and media rather than treating replies as contributions. Restricted operational notifications support manual follow-up; they do not contain the sender number or message content. No automatic WhatsApp reply is sent.Meta/WhatsApp also processes information under its own privacy policy and applicable terms.
Service providers
We use service providers to perform relevant functions within bRAINdrop.OpenAI supports AI processing, including transcription, preparation of cleaned contribution representations, collective synthesis and generated speech where used.Supabase provides database services, authentication and private file storage.Vercel hosts and operates the pilot application.Resend provides transactional email delivery, including selected participant communications and operational notifications.Meta/WhatsApp provides optional WhatsApp messaging and document delivery.These providers receive information needed for their role. Information is therefore not held solely within bRAINdrop. Provider processing may take place outside your country, including outside the European Economic Area. Contact us for information about processing arrangements relevant to your pilot.
Security and restricted access
bRAINdrop separates private participant information from Creator-facing views and collective outputs. Server-side permissions and restricted staff roles limit access to private source material, contact information and operational records.These controls help protect information, but no online service can guarantee absolute security. Keep your private return link confidential because it provides access to your contribution. Do not include private access links or sensitive contribution content in an initial privacy enquiry.
Retention
During controlled pilots, original audio, transcripts, typed input, drafts and version history may be retained to evaluate fidelity, support the service and preserve provenance. Closing or cancelling a Drop does not automatically erase its underlying records.A fixed retention period has not currently been defined for the pilot. Data is retained only as necessary for operating the service, pilot administration, audit and integrity requirements, and applicable legal obligations.You may contact us to discuss retention or request deletion of information relating to your participation. Service providers also apply their own retention arrangements.
Your rights
Depending on applicable law and the circumstances, you may request access to your personal information, correction of inaccurate information, deletion, restriction of processing or a portable copy. You may also object to processing where applicable. Where processing relies on consent, you may withdraw that consent.You may raise a concern with us or lodge a complaint with the relevant data protection authority.To make a request, email [email protected]. We may need to confirm your identity and participation before disclosing or changing private information.Requests are assessed against applicable obligations, the rights of others and relevant record-integrity requirements. We will explain any limits that apply. Deletion requests are handled by the team rather than through an automatic deletion action on this page.
Changes to this policy
We may update this policy as the pilot develops. The date above identifies the current version.For questions about this policy or how bRAINdrop handles your information, contact Paul Downing at [email protected].