How Promisd works

A promise is any public statement from the company about what customers will get and when: an email to customers, a help center article, the product page, an order confirmation, a press interview, a social post, a support reply, or the legal terms.

• We quote the words exactly, in italics, and record who said it, where, and the date it was said.
• Every entry links to its source. Where we can, we also link an archived copy in case the page changes.
• If a promise names a time window (for example "mid 2026"), we record the label as written and the calendar dates we read it as. The timeline chart draws those dates.
• A new promise never overwrites an old one. When a date moves, both stay in the ledger.

Each promise gets one outcome. We update it when something changes, and note the date and reason.

Kept

It happened within the promised window.

Partly kept

Some of it happened as promised, and some of it did not.

Slipped

It happened, but after the promised window.

Overdue

The promised window has passed and it has not happened yet.

Broken

An explicit commitment that was not honored and no longer can be. For example, a promised update date that passed with no update.

Disputed

The company's claim is contradicted by credible independent reports.

Pending

The promised window has not been reached yet.

Superseded

Replaced by a newer promise before its window ended.

A promise with no window, or one we cannot date, stays Pending until it clearly happens or clearly fails.

The scorecard is the only opinion on a product page, and it is labeled as opinion. It scores 7 dimensions from 0 to 5, for a total out of 35. Each score must be backed by evidence bullets that link to sources. Dimensions we cannot judge yet are shown as not scored and left out of the total.

Overall label

• 30+ of 35Kept its word
• 23+ of 35Mostly reliable
• 16+ of 35Mixed record
• 9+ of 35Often fell short
• 0+ of 35Did not keep its word

• Nothing anyone sends us is public until a person reviews and approves it.
• We check that dates are plausible and consistent, remove personal details from free text, and reject reports that look like duplicates, spam, or attempts to skew the numbers.
• Owners sign in with Google before adding a report. Each account can have one active report per product, which makes it much harder to stuff the numbers.
• The account email and the optional order number are private. We use them only to run the account, to spot duplicates and to check plausibility (below). They are never shown on the site.
• Owners can update or delete their own report from Your reports, and can delete their whole account there too. Changes to an approved report go live and are flagged for a reviewer to check. Reports sent before accounts existed can still be changed with their private edit link.
• Each account can send a limited number of reports per hour, to slow down abuse.

Owners can verify a report by uploading the original email the company sent them, such as the order confirmation, as an .eml file. Reports backed this way are marked Verified. Reports sent with the form alone are marked Self-reported. Both are reviewed by a person before they appear.

How the check works

• Companies that send email at scale add a digital signature to every message, called DKIM. It is made with a private key only the company's mail system holds, and anyone can check it against a public key the company publishes in its domain records.
• We accept an email only if the signature checks out, it was made by the company's own domain (for the TM-B, ridealso.com), the sender shown in the email matches that domain, and the signature covers the sender, the recipient, the subject, the date and the whole message body. If any word in the signed parts is changed, the check fails.
• The email must have been sent to the same address you signed in with. That stops someone from uploading another person's confirmation.
• From an order confirmation we take the order date (the day the email was sent, Pacific time), the trim, and the ship window quoted in the email. These become read-only on your report. A shipping confirmation adds the shipped date. A reservation confirmation adds the reservation date.
• One order confirmation can back only one account. We store a one-way fingerprint of the order number to enforce this.

Plausibility checks

The company appears to number orders in sequence. We keep the order numbers from verified emails privately, so editors can check whether a self-reported order number fits the date it claims: numbers far out of line with verified orders from around the same date are flagged for a closer look. The same numbers give a rough estimate of how many orders the company is taking. Those sales-volume estimates are private for now.

Limits

• We check the signature once, when the email is uploaded, and store the result. Companies change (rotate) their signing keys from time to time, after which an old email can no longer be checked. A report verified before that stays verified.
• Forwarded emails usually fail the check, because forwarding changes the message. The original has to be downloaded from the inbox it was sent to.
• A verified order proves the order was placed on that date with that quoted window. It does not prove the order was not canceled later. Owners update the current state themselves.
• We cannot verify a delivery date yet. Delivery dates are always reported by the owner.
• We have not yet seen a shipping confirmation from the company, so we read those more loosely and an editor checks the first ones by hand.

• Every figure on the "On the ground" panel uses approved reports only.
• By default the figures and the chart use verified reports only. A switch above them adds self-reported reports. The table of reports always lists both, each with its badge.
• Median days from order to delivery uses delivered reports that have both an order date and a delivery date.
• "Delivered within quoted window" compares the delivery date with the last day of the window the owner was quoted. We read a month as its last day, a quarter as its last day, early as the end of April, mid as the end of August, late as the end of December, and a span of weeks or months as counted from the order date. Reports with a window we cannot read are left out, and the panel says how many were counted.

The "At a glance" panel at the top of each product page is worked out from the published ledger every time the page loads. "Today" means today's date in Pacific time.

• Days late, per trim. We take the earliest published promise for that trim that has a delivery window end date (earliest by the date it was said), and count the days from the end of that window to the day shipping began. If shipping has not begun, we count to today. A count below zero is shown as zero, and "On time so far" means the first window has not ended yet.
• When shipping began. The earliest outcome date among that trim's delivery window promises judged Slipped or Kept. Promises with no delivery window, such as a promise to send an invitation to order, do not count.
• Now. The most recent promise for that trim. When several were made on the same day, we show the one with a delivery date, and of those the soonest.
• Promises kept. Promises judged Kept, out of every promise whose outcome is decided. Pending promises are left out. Every subject counts, not only delivery dates.
• Delivery date changes. Launch Edition, Performance and Standard promises judged Slipped, Overdue or Superseded.
• Open owner issues. Published issues not marked Fixed or Will not fix. The note counts those rated high or safety.
• Verified owner reports. Approved owner reports checked against the company's email.
• Next promised milestone. The pending promise whose window ends soonest, today or later.
• Transparency score. The scorecard total. It is our opinion, so it is labeled that way and kept apart from the facts.
• On your account page, "owners who ordered when you did" counts approved, verified reports for the same trim with an order date within 14 days of yours, not counting your own. We show it only when there are at least 3 such owners, and only as counts.

• For a self-reported report, we cannot confirm that the person really placed an order. We rely on review and volume. Verified reports are checked against the company's own email, within the limits above.
• Owner reports are a self-selected sample. People with problems may be more likely to report.
• We only see public statements. Private messages to individual customers may say something different.
• Sources can change or disappear. Archive links help, but not every source can be archived.

If you can show us something is wrong, please request a correction.