Privacy Policy

Who this covers

Revcover is a tool for a restaurant. The account email belongs to the person who signs up. The payout files belong to the restaurant they work for. Support mail is revcoverhelp@gmail.com.

Scan before an account

The public scan sends the CSV to the server, reads it, and returns the dollars still inside the dispute window plus one dispute written from that file. That request is not written to the database and the file is not kept. The response stays in your browser.

What an account stores

After you create an account, Revcover stores the email address, the restaurant name and the contact details you enter, optional commission percents, the payout CSV files you upload, the orders parsed from those files, the flags, the status you set (including won, partial, or denied) and any amount you record as recovered, teammate invites, and the dispute text generated for a flag when you open it. A payout file can include order numbers, dates, fees, refunds, customer reasons, and amounts the delivery app paid the restaurant.

The password is handled by Supabase Auth. Revcover does not keep a copy of the password. Supabase stores the credential for that login.

What we do not collect

Revcover does not ask for a DoorDash, Uber Eats, or Grubhub password, and it does not store one. Revcover does not log into those sites and does not submit a dispute for you. The free month does not ask for a credit card. A card number is collected only if you open Stripe Checkout to subscribe. The card number stays at Stripe. Revcover stores the Stripe customer id, subscription id, status, and invoice result.

Where it is stored

Production accounts, files, and flags are stored in Supabase (database, authentication, and private file storage). The site is hosted on Vercel. If you subscribe, Stripe processes the $7.99 charge every three months. If deadline email is turned on, Resend sends that message to the account email. Without a Resend key, the due list stays on the page and no email is sent.

A local demo on a developer machine can store the same records in a file on that machine. Production does not use that file. If Supabase is not configured in production, signup stops with an error.

Why it is stored

The records are used to show which charges are still inside the filing window, to write the claim you paste, to remember what you marked as won, partial, or denied, and to run the subscription you start. Revcover does not sell restaurant payouts or account data. People you invite to a location can see that location's files and flags. A second location is a separate restaurant. Billing follows the location that is open.

Cookies

The signed-in session uses cookies set by Supabase Auth. The open location is remembered in a cookie named revcover_restaurant. The local demo, which production does not use, uses a cookie named revcover_session. Revcover does not set advertising cookies and does not run a third-party ad pixel.

How long it is kept

Uploaded files and the orders from them stay until you delete the file in Revcover, or until you ask us to delete the account. Deleting a file removes the orders that came from that file. To delete the account, email revcoverhelp@gmail.com. We will delete the restaurant account, uploaded reports, and flags. Stripe may keep its own invoice record of a charge that already happened. Supabase and Vercel may keep short-lived backups under their own retention.

California requests

If you are a California resident, you can email revcoverhelp@gmail.com to ask what personal information we have about you, to ask us to delete it, or to tell us not to sell it. Revcover does not sell personal information. Sending that email is how you make the request. This paragraph describes the request path. It is not a claim that a regulator has reviewed Revcover.

Questions

Email revcoverhelp@gmail.com. The Terms of Service cover the price, the free month, and cancellation.