Privacy Policy
How Brĭmeli handles information submitted through this website and during website projects and continuity services.
Effective: November 2, 20261. Scope
This Privacy Policy applies to information Brĭmeli receives through brimeli.com, website assessments, project briefs, the project Start form, the project Review page, referral submissions, shared-folder links, payments, project communications and related Brĭmeli services.
It does not control how an outside website, payment provider, storage provider or other third-party service handles information under its own terms and privacy policy.
2. Forms currently used on the website
The site currently includes these Netlify Forms:
- website-assessment: the retired Website Check. /check now redirects to the website scorecard. Old submissions are kept. The site no longer collects new Website Check answers.
- website-inquiry: the homepage Project Brief. Receives name, email, business name, current website, the build or service the visitor is considering, what the website should help customers do and, when the visitor arrived from a situation link on the homepage, which situation they picked.
- website-scorecard: the public website scorecard. Receives name, email, business name, website, an optional phone number, twelve scored answers, five unscored answers, the score, category scores, a band, a tier, and any UTM tags from the link the visitor used (utm_source, utm_medium, utm_campaign, utm_term, utm_content). The score and the fix list are shown on the page after the form is sent. Brĭmeli may email the report and one short follow-up. The site code does not run an email sequence.
- project-start: the private Start form at /onboarding. Receives name, email, business name, current website, Project ID, what the business does, customer types and what each should do, the desired outcome, proof the client may publish, what to keep, reference websites, tools to connect, a shared-folder link, the approver's name and email, a deadline, the domain and where it is registered, and notes. It does not accept file uploads or passwords.
- project-review: the private Review page at /review. Receives name, email, Project ID, the preview version and link, the client's decision (request changes or approve for launch), requested changes, a shared-folder link, and for an approval the approver's name, the approval acknowledgement and a client-side timestamp. Brĭmeli confirms each approval directly with the named approver before requesting final payment.
- referral-submission: receives the referrer's name and email, the referred business and contact details and a note about the introduction.
Netlify processes these website form submissions as the form service used by the current site.
3. Information we collect
Depending on how you interact with Brĭmeli, we may receive:
- name, email address and business name;
- website/domain information;
- assessment answers and calculated assessment results;
- project package, Project ID, business description, customer information, primary actions, offers and project goals;
- company story, credentials, authorized testimonials/reviews and other source material you choose to provide;
- current-site or Version 1 feedback;
- integration/vendor information and project deadlines;
- links to folders or files you share through services such as Google Drive, Dropbox, OneDrive, iCloud or another provider;
- project approvals, review comments, support requests and service history;
- payment status, amount, purchased service and billing/contact information made available to Brĭmeli by Stripe or another disclosed payment provider;
- referral-program information where applicable;
- technical information that hosting, security or third-party service providers may receive automatically as part of operating their services.
4. How we use information
- respond to assessments and inquiries;
- determine project fit and prepare scopes, SOWs, proposals and invoices;
- create and manage a client project under its Project ID;
- review source material and build agreed website deliverables;
- reconcile Version 1 feedback and revisions;
- verify project facts, assets, integrations and launch requirements;
- process project installments, invoices and recurring payments through Stripe or another disclosed provider;
- provide continuity, maintenance and support services;
- administer the Referral Partner Program;
- operate, secure, troubleshoot and improve Brĭmeli services;
- maintain reasonable business, accounting and contractual records;
- comply with applicable legal obligations and protect against misuse or fraud.
5. Project IDs and internal project records
Brĭmeli uses a Project ID as the primary operational key for a client project. Forms also collect business_name and client_email so submissions can be reconciled to the correct project.
Netlify form submissions are capture records; Brĭmeli may maintain a separate internal project record and project folder that references or contains relevant submitted information and authorized project materials.
6. Files and shared-folder links
Project forms do not accept file uploads. Brĭmeli asks clients to share a folder or file link from a storage provider such as Google Drive, Dropbox or OneDrive, or to reply to an Brĭmeli email with files.
Clients should provide only material Brĭmeli needs for the project and should avoid sending passwords, full payment-card information, private customer records, government identification numbers, health information, tax records or other unnecessary sensitive data through ordinary Brĭmeli forms or shared folders.
Third-party storage providers control their own accounts, access rules and privacy practices.
7. Payments and Stripe
Brĭmeli uses Stripe-hosted payment services for approved project installments and may use Stripe for invoices or recurring service payments.
Stripe may collect payment, transaction, device and identifying information under its own privacy practices. Brĭmeli generally does not receive or store a full payment-card number through the Brĭmeli website.
Stripe's privacy policy is available at stripe.com/privacy.
8. Analytics, interaction events and cookies
At the effective date of this policy, the Brĭmeli site code reviewed for this policy does not have a general network analytics provider wired into it.
The site includes a browser-side interaction event layer that can identify events such as an email-link click, Stripe-checkout click, external-link click, project-brief click, build preselection, completed website scorecard, project-brief submission or form-submission attempt. That current event layer does not itself send a network request, set cookies, use browser storage, include query strings or include form values.
If Brĭmeli later connects an analytics provider or changes the site's cookie/storage behavior, this Privacy Policy should be updated to describe the actual provider and data practices.
Third-party pages or services you choose to open, including Stripe or a shared-folder provider, may use their own cookies or tracking technologies under their own policies.
9. Service providers and disclosures
Brĭmeli may disclose information to service providers and contractors only as reasonably needed to operate the website, process forms/payments, deliver client work, host/deploy sites, provide technical support or operate the business.
The current website implementation verifies Netlify as the website form/hosting platform and Stripe as a payment provider. Other project-specific providers may be used when a client supplies or approves them.
Brĭmeli may also disclose information when reasonably necessary to comply with law, respond to lawful requests, enforce agreements, protect rights or security, prevent fraud or complete a business transfer.
10. Data retention
Brĭmeli does not state a single fixed retention period for every record type because project, payment, accounting, contractual and operational records may have different requirements.
Information is retained only as reasonably necessary for the purpose for which it was collected, to provide services, maintain appropriate business records, resolve disputes, enforce agreements and satisfy applicable legal obligations.
We do not keep your logins after a project is archived.
11. Security
Brĭmeli uses reasonable administrative and technical practices appropriate to the information and services involved, but no online service, transmission method or storage system can be guaranteed completely secure.
Clients should use provider-supported collaborator, delegated-user, OAuth, API-key or similar controlled-access methods where available rather than sending passwords through ordinary forms.
12. Client responsibility for submitted material
Clients are responsible for providing only information and materials they are authorized to share. This includes photographs, logos, testimonials, customer information, documents and data from third-party systems.
13. Third-party links and systems
Brĭmeli websites and projects may link to or integrate with outside systems. Their own terms and privacy policies govern their handling of information.
A client project may also introduce additional privacy, cookie, consent, regulatory or data-processing requirements. The client is responsible for identifying legal requirements specific to its business, and Brĭmeli implements agreed technical controls within the approved scope.
14. Children
Brĭmeli services are directed to businesses and adults. The website is not designed to solicit personal information from children under 13.
15. Your requests
You may ask Brĭmeli to correct information you previously submitted, ask questions about how information is handled, or request deletion where legally and operationally appropriate. Brĭmeli may need to verify identity before acting on a request.
16. Changes to this Policy
Brĭmeli may update this Privacy Policy when the website, forms, vendors, project workflow or legal obligations change. The effective date above identifies the current version.
17. Contact
Privacy questions or requests may be sent to Melissa@brimeli.com.