1. Who this policy covers
Wall of Love is operated by Strawberry Labs LLC, Sharjah, United Arab Emirates (“we”, “us”). It provides a service for collecting, managing, and publishing customer testimonials at walloflove.net. Two groups of people use it:
- Customers — people and businesses with a Wall of Love account. For account data, we decide how it is used and act as the data controller.
- Respondents — people who leave a testimonial through a customer's form or are invited by a customer. The customer decides why and how that testimonial is used and is the controller; we process it on the customer's behalf.
2. Data we collect
Account data: your name, email address, a salted hash of your password (never the password itself), two-factor authentication settings, passkey public keys (never your biometrics, which stay on your device), notification preferences, and the projects and teams you belong to.
Testimonial data: what a respondent chooses to submit — typically name, rating, written or recorded testimonial (video and audio), and optionally email address, job title, company, website, photo, and company logo — plus the consent choice they made about public use.
Technical data: IP address and browser user agent, used for security, abuse prevention, and rate limiting, and stored with sign-in sessions so you can review and revoke them.
Usage data: counts of views of public walls, widgets, and forms, so customers can see how their testimonials perform. These counts are not tied to a visitor's identity and use no tracking cookies.
Website analytics: on our marketing and sign-in pages we use Google Analytics to understand which pages people visit and how they found us. It records pages viewed, referrer, approximate location, and device type. Advertising features and Google signals are turned off. In the EEA, UK, and Switzerland it runs without cookies. It never runs on public walls, widgets, or forms.
Billing data: if you subscribe, payments are processed by Stripe. We receive your subscription status and invoices but never your full card number.
3. How we use data
- To run the service: store, process, and display content.
- To process videos: transcoding into web formats and, only if a customer's deployment enables it, automatic transcription.
- To send service email: account verification, password resets, team invites, testimonial requests a customer sends, alerts about new testimonials, and billing notices.
- To keep the service secure: detecting abuse, enforcing rate limits, and investigating incidents.
- To bill subscriptions and comply with legal obligations.
4. Legal bases (EEA and UK)
We rely on performance of a contract for account and service data, legitimate interests for security, abuse prevention, website analytics, and aggregate usage counts, and legal obligation for billing records. For testimonials, the customer is responsible for having a valid basis, which is usually the respondent's consent captured on the form.
5. Cookies
We use these cookies to run the service:
wol_sessionkeeps you signed in (up to 30 days).wol_last_authandwol_last_projectremember your sign-in method and last opened project.wol_passkeyremembers that this device has a passkey so we can offer passkey sign-in (up to 1 year).wol_affrecords an affiliate referral for up to 90 days when you arrive through a partner link.wol_oauth_returnreturns you to an MCP connection request after sign-in. It expires after 10 minutes.
Outside the EEA, UK, and Switzerland, our marketing and sign-in pages also set Google Analytics cookies (_ga and _ga_*, up to 2 years) to count returning visitors. You can block them in your browser without affecting the service. Public walls, widgets, and forms set no cookies for visitors and respondents. We do not use advertising or cross-site tracking cookies.
6. MCP connections you authorize
You can connect an MCP client to one selected project through OAuth. The consent screen identifies the client and its requested permissions. Read access shares approved testimonials with public consent, their public customer identity, project tags, widget metadata and published wall metadata. It excludes customer email addresses, private testimonials and internal notes.
You can separately allow the client to create tags, apply tags to public proof, or create publicly embeddable widgets. A client may process shared content using its own AI provider under that provider's terms. Review the client's practices before connecting.
We store connection permissions, activity timestamps and hashes of access credentials. You can revoke a connection under Integrations → MCP. Revocation stops future access; it cannot remove content a client has already received.
7. Sharing and subprocessors
We do not sell personal data or share it for advertising. We use service providers who process data on our instructions:
- Convex — application database and backend.
- Amazon Web Services — email delivery (Amazon SES).
- Our cloud storage and hosting providers — media files and the web application.
- Stripe — payment processing for subscriptions.
- Google — website analytics on our marketing pages.
- Cloudflare — custom domains and network delivery.
- Deepgram — speech-to-text, only where transcription is enabled.
- Berrycrawl — fetching public review pages, only when a customer imports reviews from a public URL.
Testimonials a customer approves and the respondent agreed to share publicly are published on that customer's walls and widgets, where anyone can see them. We may disclose data when required by law.
8. Retention
- Account and project data: kept while the account is active and deleted when the account or project is deleted, apart from records we must keep for legal or tax reasons.
- Testimonials and media: kept until the customer deletes them. Deleted testimonials stay in the project's trash until emptied.
- Sign-in sessions: expire after 30 days.
- Password reset, verification, and two-factor codes: expire within hours to days and are purged automatically.
- Raw view counts: deleted after 180 days.
- Backups: deleted data can remain in encrypted backups for a limited period until they are overwritten.
9. Security
Data is encrypted in transit. Passwords are hashed; two-factor secrets and webhook signing secrets are encrypted at rest; sign-in and invitation links are stored only as one-way hashes. Access to production systems is limited to people who need it. No system is perfectly secure; if a breach affects your data, we will notify you as the law requires.
10. Your rights
Depending on where you live, you can ask to access, correct, export, or delete your personal data, object to or restrict certain processing, and withdraw consent. California residents have the right to know, delete, and correct, and we do not sell or share personal information as those terms are defined in the CCPA.
Customers can edit or delete most data directly in the dashboard. Respondents should contact the business that collected their testimonial; if you can't reach them, email us and we will help. Every invitation email includes an unsubscribe link.
You may also complain to your local data protection authority.
11. International transfers
Our providers may process data in the United States and other countries. Where required, transfers rely on safeguards such as the European Commission's Standard Contractual Clauses.
12. Children
The service is not directed to children under 16, and we do not knowingly collect their personal data. If you believe a child provided data, contact us and we will delete it.
13. Changes and contact
We will post changes here and update the effective date; material changes are announced by email or in the dashboard beforehand. Questions or requests: support@walloflove.net.