Privacy policy
Effective November 1, 2026
1. Who we are and what this covers
Fullsteem is operated by RDW LLC, a Kentucky limited liability company. This policy explains how we handle personal information through the Fullsteem website, the owner tools, the business websites and booking pages that Fullsteem hosts, and Anna. Fullsteem is offered to businesses in the United States.
We handle information in two roles. For business owners’ account and business details, and for waitlist entries, RDW LLC decides how the information is used and is responsible for it. For information about a business’s customers and website visitors, we act as a service provider, also called a processor, for that business.
Businesses control their customers’ information. The business decides which services to offer and how to handle its customer relationships. Fullsteem processes customer information to provide the tools that business uses. Ask the business about its own services, notices and use of your information.
2. Information we collect and use
- Owner account and business details. Account email and sign-in records; business name, contact details, location or service area, hours, website address, website content, service menu, prices and booking policies; and subscription status. We use these to provide account access, build and publish the owner-approved website, operate business tools, bill the subscription and provide support.
- Customer contact and booking details. The email a customer uses to sign in, their name, an optional phone number and their agreement to create a customer profile with the business; selected services, vehicle details, scheduled times, quotes and booking status. Mobile visits also require a service address and ZIP code. We use this information to handle booking requests, send booking emails and show the business its customer and booking records. Each business sees only the profile and bookings a customer has with that business.
- Website chat messages. Messages you type to Anna and the recent conversation are sent with each request so Anna can answer questions about the business, quote services and help you reach the booking page. Fullsteem does not save website chat transcripts to its database. Owner setup also sends relevant business details to Anna when the owner asks for AI suggestions. Please do not include sensitive information that the request does not need.
- Payments. Stripe account and transaction identifiers, amounts and payment status for subscriptions and customer deposits. Card details are entered into Stripe’s payment form and go to Stripe. We do not receive full card numbers.
- Emails. For the emails Fullsteem sends, the recipient address, message content and delivery status.
- Public business information. When an owner asks, Fullsteem searches public web sources using the business’s name, area, service labels and website address, and reads pages from the owner’s existing public website, to suggest setup details for the owner to review.
- Technical information. IP address, browser and device details and request logs that our hosting and authentication providers record when you use Fullsteem. We use these to deliver pages, keep sign-in secure, prevent abuse and fix problems.
- Support messages. What you send when you email us, which we use to respond.
- Waitlist entries. If you join the Fullsteem beta waitlist on our website, we collect your email address, your business name and, if you give it, your website. We use them only to contact you about the Fullsteem beta. Joining does not create an account. Each entry is sent by email to our team inbox and is not saved to the Fullsteem database.
We do not sell personal information, and we do not share it for targeted advertising. We do not use a business’s customer information for our own marketing.
3. Services that process information
Fullsteem uses these providers for the following functions when enabled:
- Supabase: account authentication and storage of business, customer, booking and integration records.
- Vercel: website and application hosting, which processes requests to serve the site and tools.
- Stripe: subscription checkout and customer payment processing through the business’s connected Stripe account. Fullsteem uses payment identifiers and status to reconcile bookings and activation. When you provide personal information to Stripe through Fullsteem, Stripe receives it and processes it under the Stripe Privacy Policy. The current beta uses test payments.
- Resend: sending business sender-verification and booking-confirmation emails, delivering waitlist entries to our team inbox, and reporting delivery events.
- Google Calendar: calendar connections for owners who choose to connect, as described below.
- OpenAI: AI processing for Anna. Website chat messages, recent conversation and relevant business information or tool results are sent to the model to generate a response. Owner-requested setup suggestions use business context. AI answers can be inaccurate.
- Exa: public web search for owner-requested business research, using only the public business details listed above.
These providers process information to provide their services to us, under their own terms and privacy policies. Some may keep limited copies, such as security and abuse-monitoring logs, under those terms.
We also share information with the business you book with, so it can serve you; when the law requires it or to protect the rights, safety and security of people and Fullsteem; with a buyer or successor if Fullsteem is part of a merger, acquisition or sale, in which case this policy continues to apply to the information transferred; and with your direction or consent.
4. Connected owners’ Google Calendar
Connecting Google Calendar is an owner choice. Fullsteem asks Google for two permissions: to see the list of the owner’s calendars, and to view and edit events. We use calendar names, identifiers, time zones and access roles to let the owner choose a calendar. From events in the selected calendar we read only each event’s identifier, status, start and end times and whether it shows as busy. We do not read event titles, descriptions, locations or attendees. We store connection details, encrypted refresh credentials and the resulting busy periods.
Busy periods block booking times. Fullsteem creates, updates and removes its own booking events in the selected calendar. Each event is titled “Fullsteem booking” and holds the booking time and a booking reference, not the customer’s name or address. The open times shown on the booking page, and checked by Anna, take busy periods into account without revealing any event details.
Fullsteem’s use of information received from Google APIs, and its transfer of that information to any other app, follows the Google API Services User Data Policy, including its Limited Use requirements. We use Google Calendar data only to show accurate availability and keep bookings in sync for the owner. We transfer it only as needed to provide those features, for security, or to comply with the law. We do not sell it, use it for advertising, use it to train generalized AI or machine learning models, or let people read it except with the owner’s permission, for security or to comply with the law.
The owner can disconnect Google Calendar in the owner workspace, which asks Google to revoke Fullsteem’s access, or remove access at any time in their Google Account settings. Stored calendar information follows section 6, and an owner can ask us to delete it sooner by emailing help@fullsteem.com.
5. Cookies and browser storage
Fullsteem uses only cookies that the service needs to work. Account sign-in uses cookies to keep you signed in. Security cookies that expire within seven days carry an invitation link, return you to the right step after sign-in and protect connection steps with Google and Stripe. If you join the waitlist, a cookie that expires after ten minutes holds a one-way fingerprint of your entry, not the entry itself, so an accidental second submission is not sent twice. Stripe’s payment form may set its own cookies to help prevent fraud. We do not use advertising cookies, analytics cookies or cross-site tracking. Because these cookies are needed to provide the service, we do not ask for cookie consent. You can block cookies in your browser, but sign-in and payment will not work without them.
The website draft you start on the Fullsteem build page is saved in your browser’s local storage on that device for up to seven days, so your answers can be restored. Unsaved booking-settings edits are kept in local storage until you save or discard them, and sign-up progress is kept for the browser session. You can clear this storage in your browser settings.
6. How long we keep information
We keep owner account, business, customer, booking, payment, calendar and email records for as long as the business’s account is open. After an account closes, we keep them for 90 days so the owner can ask for a copy, then delete or anonymize them. We keep information longer only where the law requires it, such as billing and tax records, or where we need it to resolve a dispute, prevent fraud or abuse, or enforce our terms. Copies in routine provider backups are removed as those backups expire.
Website chat messages are not saved to our database. Providers may keep limited copies, such as request logs, under their own terms. Browser storage on your device follows section 5.
Waitlist entries are kept in our team inbox only while we need them to contact you about the Fullsteem beta, or until you ask to be removed.
7. Your choices and requests
You can ask to access, correct or delete your personal information, or to get a copy of it, by emailing help@fullsteem.com. Self-service export and deletion tools are not yet available, so we handle these requests by email. We will respond within 45 days. If we need more time for a complex request, we may extend that once by up to 45 more days and will tell you why within the first 45 days.
We may need to verify your identity, usually by confirming that you control the email address on the account or booking. Someone you authorize may make a request for you if we can verify that authority. If we decline a request, we will explain why. You can appeal by replying to our decision, and we will respond to an appeal within 60 days. If you still disagree, you can contact your state attorney general.
If your request concerns a business’s customer records, we will tell that business and help it respond, because the business controls those records. You can also contact the business directly. We will not treat you differently for making a request.
Some state privacy laws, including those of Kentucky and California, give residents specific rights. We honor the requests described here for everyone, whether or not a state law applies to us. Because we do not sell personal information or share it for targeted advertising, no opt-out is needed.
Booking, sign-in and account emails are part of the service. If you join the waitlist, we will email you about the Fullsteem beta. You can unsubscribe at any time by replying to one of those emails or by emailing help@fullsteem.com, and we will remove you from the waitlist. We do not currently send other marketing emails. If we do in future, each one will include a way to unsubscribe.
8. Security
We use reasonable safeguards for the information we handle, including access controls that keep each business’s records separate and encryption of stored Google Calendar refresh credentials. No system is completely secure. If a security breach affects your personal information, we will notify you as the law requires.
9. Children
Fullsteem is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child has given us personal information, contact us and we will delete it.
10. Where information is processed
RDW LLC is based in the United States. Our providers may process information in the United States and in other countries where they operate.
11. Policy changes
We will post any update here with a new effective date. If we make a material change, we will email account owners at least 30 days before it takes effect, unless the law requires a change sooner. Before using Google user data in a new way, we will ask the owner for consent.
12. Contact
For privacy questions and requests, contact help@fullsteem.com. If your question is about a booking or a business’s customer records, contact that business as well.