PRIVACY POLICY

Privacy and measurement consent. ConsentLayer manages browser privacy choices for cookies, optional analytics, advertising measurement, Global Privacy Control, and applicable Do Not Sell or Share preferences. These choices control optional tracking and measurement only.

Case publication consent. Separately, each case participant controls whether an anonymized version of that specific case may be published to The Courtroom. Publication requires the product's bilateral case workflow and, where required, independent consent from both parties.

The two systems are independent. Accepting or rejecting cookies or marketing measurement never publishes a case. Granting or withdrawing case-publication consent never grants analytics, advertising, or marketing consent. Neither consent system may be used as a substitute for the other.

Account information. Base44 authentication processes your account identifier, email address, profile/name fields supplied through authentication, session information, and role needed to sign you in and authorize app features.

Case information. When you file or join a case, the app stores the case title, category, display aliases, consent choices, case status, and participant identifiers.

Testimony. The written statements you submit are stored as private case records and are used to decide the fictional ruling. File attachments are disabled in the Google Play release because the current Base44 UploadFile service does not expose a verified per-file deletion operation.

Votes and preferences. If you vote on a published ruling or change account settings, the app stores your vote, display preferences, and notification choices.

Notifications and technical reliability data. The app stores case-event notifications and limited error/reliability information such as the affected app surface, expected behavior, observed error text, timestamps, and internal account identifier when authenticated. The app does not intentionally collect precise location, contacts, SMS, or call logs.

Optional advertising measurement. THE VERDICT uses ConsentLayer as the browser consent authority for optional measurement. OpenAI Ads measurement is disabled unless the marketing category has a valid ConsentLayer consent record. Global Privacy Control or an applicable sale/share opt-out signal is treated as a denial for marketing measurement even if a stale category value says otherwise. When allowed, the measurement path may record privacy-limited page-category and case-created conversion events using a pseudonymous event identifier derived from the internal case identifier, a trusted source URL stripped to origin and pathname for server conversion reporting, and OpenAI attribution context when available. Private testimony, invite secrets, aliases, names, email addresses, phone numbers, and raw case identifiers are not sent as conversion data.

Privacy inquiries. If you use the privacy form on this page, the app stores the email address, request category, and message you provide so the request can be reviewed and answered.

We use account and case information to authenticate users, enforce participant/admin permissions, operate case workflows, prevent duplicate or conflicting mutations, provide notifications, and maintain security and reliability.

Case titles, categories, aliases, and testimony text may be processed through Base44's AI integration to classify whether a dispute is appropriate for the service and, for eligible low-stakes disputes, generate the fictional ruling.

We use privacy-inquiry information only to administer the submitted privacy request and related security or compliance work.

When you allow advertising measurement, we use the resulting measurement events only to understand whether advertising leads to useful product actions and to measure campaign performance. Dynamic private routes containing case, evidence, account, administration, or notification identifiers are excluded from page-view measurement.

Your private testimony is not directly published to the public courtroom. A case can be published only after an eligible ruling and the required case-publication consent. This publication consent is separate from ConsentLayer privacy or measurement consent and is enforced by the case workflow. Publication uses a separately generated, validated, anonymized representation that refers to the participants as Party A and Party B.

Public pages may show the anonymized case title, summary, ruling, findings, responsibility percentages, aggregate jury votes, publication date, and related public ruling fields. Internal account identifiers and vote ownership are not included in the public DTO.

THE VERDICT runs on Base44. Base44 provides hosting, authentication, database services, backend functions, file/integration infrastructure, and AI integration services. Information is sent to Base44 and the service providers or AI providers Base44 uses as necessary to deliver these functions.

ConsentLayer manages browser consent choices and the privacy-preference surface. If valid marketing consent is absent, THE VERDICT does not initialize the OpenAI Ads Pixel and does not dispatch the corresponding Conversions API event. When marketing consent is valid, limited measurement events may be sent to OpenAI Ads through the browser Measurement Pixel and the server-side Conversions API. Browser and server copies of the same case-created event use the same pseudonymous event identifier so OpenAI can deduplicate them.

Billing. If you purchase a case pack or Verdict+ subscription, your email address and an internal account identifier are sent to Stripe, our payment processor, to create the checkout session and manage the subscription. THE VERDICT does not receive or store your full card number.

Optional social publishing. If you choose to connect a Facebook Page or Instagram professional account from a published verdict, you are redirected to Meta to authorize that connection through a Base44-managed connector. If you then choose to publish, the anonymized ruling headline, case title, summary, and public verdict URL are sent to Facebook or Instagram to create the post. This only happens when you press "Connect" and then "Post," and only for content already anonymized for public publication.

Optional calendar sync. If you choose to connect Google Calendar from a case, you are redirected to Google to authorize that connection through a Base44-managed connector. If you then sync a case, the case title, case number, category, and party aliases are sent to Google Calendar to create a hearing-reminder event. This only happens when you press "Connect Calendar" and then add or sync an event.

We may disclose information when required to comply with applicable law, enforce security, investigate abuse or fraud, or protect users and the service. We do not sell personal information, and case testimony is not used by THE VERDICT for advertising.

The following third-party providers receive data only when you initiate the feature that requires them. Data is shared for the specific purpose described and is not sold or used by THE VERDICT for advertising. Meta Platforms, Inc. operates Facebook and Instagram; Google LLC operates Google Calendar; and Stripe, Inc. operates payment processing.

Stripe (payment processing). When you purchase a case pack, Case Encore, or Verdict+ subscription, your email address and an internal account identifier are sent to Stripe to process the payment, create the checkout session, and manage the subscription. Stripe may receive your billing name and postal code as entered at checkout. THE VERDICT does not receive or store your full card number, CVC, or Stripe token details.

Google Calendar (optional calendar sync). When you connect Google Calendar from a case and add or sync a hearing reminder, the case title, case number, category, and party aliases are sent to Google Calendar to create the calendar event. This data is shared only when you press "Connect Calendar" and then add or sync an event. Google Calendar does not receive your private testimony, account email, or internal identifiers.

Facebook (optional social publishing). When you connect a Facebook Page from a published verdict and choose to post, the anonymized ruling headline, case title, summary, and public verdict URL are sent to Facebook to create the post. This data is already anonymized for public publication. Facebook does not receive your private testimony, account email, or internal identifiers. This only happens when you press "Connect" and then "Post."

Instagram (optional social publishing). When you connect an Instagram professional account from a published verdict and choose to post, the anonymized ruling headline, case title, summary, and public verdict URL are sent to Instagram to create the post. This data is already anonymized for public publication. Instagram does not receive your private testimony, account email, or internal identifiers. This only happens when you press "Connect" and then "Post."

Data retention by third parties. Each third-party provider retains data according to its own privacy policy and applicable terms. THE VERDICT does not control third-party retention beyond the data we send. You can revoke a social or calendar connection at any time from Account Settings, which prevents future data sharing with that provider.

Data is transmitted using HTTPS. Access to private app records is restricted using authenticated backend functions, participant checks, administrator checks, and Base44 row-level security where applicable. Sensitive backend operations use service-role access only after server-side authorization.

No system can guarantee absolute security. If you believe information has been exposed or handled incorrectly, submit a privacy inquiry below.

Private case and account data is retained while needed to provide the service unless you delete your account or the data is otherwise removed. Archiving a case is an organizational action and is not deletion.

You can start account deletion from the account deletion page. The deletion workflow removes the account identity and directly attributable app records, removes the departing user's testimony and votes, withdraws/redacts shared cases without deleting another participant's own testimony, and removes public verdict material derived from the deleted participant's case.

Base44 documents that deleted custom table records can remain in its recoverable “Recently Deleted” state for up to 30 days before permanent removal. Platform backups or legally required records may also follow Base44's documented retention processes.

Security and reliability receipts may be retained after account deletion when needed to preserve tamper-evident operational history. Before the account identity is removed, the app replaces the receipt's account identifier with a one-way pseudonymous value so the receipt no longer contains the live account ID.

File evidence uploads are disabled in this Play release. This prevents creation of user-owned Base44 media that the app cannot independently prove it can physically delete through a supported per-file API.

You can update supported account preferences in Account Settings, withdraw eligible cases, control case-publication consent where permitted by the case state, and delete your account from the deletion page. Case-publication consent applies only to the relevant case and does not change your cookie or measurement preferences.

Browser cookie and measurement choices are managed separately through ConsentLayer's privacy controls, including the Your Privacy Choices link and the preference surface available from Account Settings when advertising measurement is configured. Those privacy choices do not change publication consent. If the consent service is unavailable or no valid consent record exists, optional measurement remains disabled.

You may also use the privacy form below to ask about access, correction, deletion, or other privacy matters. We may need to verify account ownership before acting on requests involving account-specific information.

THE VERDICT is not intended for children or for disputes involving minors, abuse, violence, self-harm, medical emergencies, serious crime, legal or regulated matters, or other high-stakes situations. The service includes a safety-classification step intended to decline such disputes, but users should not submit sensitive high-stakes information in the first place.

If the app's data practices materially change, this policy will be updated and the effective date above will change. The Google Play Data safety disclosure should be kept consistent with the practices described here.