01Who we are
RowFold LLC ("RowFold," "we," "us") operates the RowFold workspace platform. We are the data controller for personal information collected through our marketing site and the data processor for information you store in your workspaces.
02What we collect
| Category | Examples | Why |
|---|---|---|
| Account data | Name, email, password hash, profile picture | Create and manage your account |
| Workspace content | Tables, records, fields, automations, forms, files you upload | Provide the Service |
| Usage data | Pages visited, features used, error logs, performance metrics | Improve and secure the Service |
| Billing data | Company name, address, payment method (via Stripe) | Process payments & comply with tax laws |
| Communications | Support tickets, sales conversations, in-app messages | Respond to you and improve service |
| Connected-app data | Events, spreadsheets and records you import from apps you connect, busy times from connected calendars, and the access tokens a connection needs | Run the integrations you connect (for Google, see section 13) |
We do not collect: biometric data, precise location, advertising identifiers, or browsing history beyond our own properties.
03How we use information
- To provide the Service: store and process your workspace content, deliver features, and respond to your requests.
- To improve: understand which features are used and where users get stuck, fix bugs, and inform the roadmap. Section 10 says what we measure, how long we keep it, and how to switch it off.
- To communicate: service announcements, security notices, billing receipts, and (with your consent) product updates.
- To secure: detect and prevent abuse, fraud, and security incidents.
- To comply: meet legal obligations including tax, accounting, and lawful information requests.
04AI features & your data
When you use AI features (workspace generation from a description, plain-English answers about your data, field suggestions, and import analysis), the relevant portion of your data is processed by our AI provider, Anthropic, via the Claude API. AI calls are made on a per-request basis — no persistent fine-tuning on your content. Search in the ⌘K palette is keyword matching that runs entirely in our database: search queries and results are never sent to an AI provider.
An automation’s AI step, and an AI teammate you hire, run on the schedule or the event you set up rather than at the moment you ask. A teammate reads only the tables you give it, writes what it finds on its own desk inside your workspace, and changes nothing itself: anything it suggests waits until a person in your workspace approves it. Its data goes to the same AI provider, in the same way, and is never used to train a model.
05Sharing
We share information only with:
- Sub-processors who help us operate the Service — each one, what it does, and what data it touches is listed on the compliance page, which is the authoritative list. We will update it before adding a new category of sub-processor.
- Workspace members you've invited — they see workspace content per the permissions you set.
- Legal authorities only when compelled by valid legal process, and we will challenge requests we believe are overbroad.
- An acquirer in the event of a sale or merger, with notice and option to delete your account first.
We never sell personal information or workspace content.
06Your rights
Depending on your location, you have rights including: access, correction, deletion, portability (export), restriction, and objection to processing. Use the in-app data tools (Settings → Privacy → Export / Delete) or email privacy@rowfold.com. We respond within 30 days.
07Data retention
We keep workspace content for the life of your account. After account deletion, content is removed from our active systems within 30 days and from backups within 90 days. Some records (billing, security logs) are retained for up to 7 years for legal compliance.
08International transfers
RowFold is operated from the United States. If you access the Service from elsewhere, your data may be transferred to the US. For EU/UK users we rely on Standard Contractual Clauses; full details are in our Data Processing Agreement, which sets out the transfer mechanism, the subprocessors and the security measures.
09Security
We encrypt data in transit and at rest, run continuous security monitoring, and limit employee access by role. Report vulnerabilities to security@rowfold.com.
10Cookies & analytics
We measure how RowFold's website and app are used, so we can see what's slow, what's confusing and where people get stuck. We do this ourselves. No analytics company, advertising network or other outside party receives this information, and it stays on RowFold's servers.
On our website we count visits to each page, where each visit came from (a search engine, or a link we posted, for example), how far down the page people read, how quickly each page loaded, and which country each visit came from. We work out the country from your IP address at the moment of the visit, using a database on our own servers, then discard the address. We don't store your IP address or set a tracking cookie to do any of this. To avoid counting you twice in one day, we use a code that changes every day. If you arrive by one of our links, a cookie set by RowFold itself remembers which link it was for up to 90 days, or until you sign up, so we know which of our posts brought you.
In the app, when you're signed in, we record which steps of RowFold you've reached, such as your first record, your first booking page or the first time you invited someone. We also record how long pages take to load for you, what kind of device and browser you use, and which country you're connecting from. We work out the device from your browser, and the country from your IP address at the moment of each request, using a database on our own servers. Then we discard both the browser details and the address. When something goes wrong, we record the error and the kind of page it happened on, so we can fix it.
We never record what you put into RowFold. That means your table and record names, your searches and filters, and anything your customers type into your forms, booking pages or chat. We record the kind of page, such as “a table”, never which table. On the pages your customers see, we record only how quickly the page loaded and the kind of device it loaded on.
Questions you ask RowFold's AI are part of your workspace, not our measurements. Ask keeps your conversations so you can return to them, and you can delete them. For other AI features we keep the question and the answer for 30 days, so we can investigate a wrong answer, then delete the text and keep only the cost and the timing. If you mark an answer as unhelpful, we keep that one for 90 days.
You can switch measurement off at any time in Settings → Privacy. When you do, we stop measuring your use and delete what we've already recorded about you. Page-load times still count toward our speed figures, with nothing that identifies you. Deleting your account does the same.
How long we keep it. We keep individual page loads, timings, errors and website visits for 90 days. After that we keep only daily and weekly totals, which aren't linked to any person. The record of which steps you've reached stays for as long as you have an account and measurement is on, because it describes your account's first months.
11Children
RowFold is not directed to children under 16. We do not knowingly collect information from anyone under 16. If you become aware that a child has provided us information, email privacy@rowfold.com.
12Changes
We may update this Privacy Policy from time to time. Material changes will be communicated by email and via in-app notice at least 30 days before they take effect.
13Google user data
This section covers the information RowFold receives from Google when you sign in with Google, or when a workspace connects Google Calendar, Google Sheets or Google Drive. It adds to the rest of this policy.
RowFold's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What we access, and why
| When you | What RowFold reads or does | Why |
|---|---|---|
| Sign in with Google | Your Google account ID, name and email address, and whether Google has verified that address | Create your RowFold account and sign you in |
| Connect Google Calendar, Sheets or Drive | The email address and Google account ID of the account you connect | Show which account is connected |
| Check staff calendars from a booking page | When those people are busy: the start and end of each busy period, with no titles, attendees or locations | Stop the booking page offering times they are already busy |
| Import a calendar | The events on it: title, times, location, description, status, organizer, attendees and the event's link | Make a table of those events in your workspace, kept up to date if you switch on syncing |
| Switch on “Put bookings on the connected calendar”, or add a “Create a calendar event” step to an automation | Creates events on your calendar, and moves or deletes the events it created | Keep your calendar in step with the bookings taken on your booking pages, and add the events your automation describes |
| Import from Google Sheets | Only the spreadsheets you pick in Google's file picker | Import them as tables, kept up to date if you switch on syncing |
| Save files to Google Drive | Only the folders and files RowFold creates in your Drive | Save a record's files to Drive when an automation says to |
How we store it
- The access tokens Google issues for a connection are stored encrypted, and deleted as soon as the connection is disconnected.
- Busy periods are kept in memory for at most two minutes and are never saved to our database.
- Imported events and spreadsheets become records in your workspace. Your workspace's permissions decide who can see them, and they are protected like the rest of your workspace content (section 09).
- For each event RowFold puts on your calendar, we keep Google's ID for it, so that the event can be moved or removed when the booking changes.
Sharing
We share Google user data only in the ways section 05 describes: with the people you give access to your workspace, with the sub-processors that help us run the Service, and when the law requires it. It passes to a new owner in a merger or sale only with your explicit consent first. We never sell it, never use it for advertising, and never pass it to data brokers or information resellers.
AI features
Imported events and spreadsheets are workspace content, so when you use an AI feature on them, the records it needs are processed as section 04 describes: for that request, to answer you. Google user data is never used to develop, improve or train generalized AI or machine-learning models.
Who at RowFold can see it
No one at RowFold reads your Google user data unless you ask us to (for example, to help with a support request), it is needed to investigate abuse or a security incident, or the law requires it.
Your controls
- Disconnect. A workspace admin can disconnect any Google app in Settings → Integrations. RowFold deletes that connection's tokens straight away and stops reading from and writing to the account.
- Revoke from Google. You can also remove RowFold's access from your Google Account at myaccount.google.com/connections.
- Delete what was imported. Imported events and spreadsheets stay in your workspace until you delete them. To have us delete Google user data for you, email privacy@rowfold.com.
- Events RowFold added stay on your calendar after you disconnect. Delete them in Google Calendar if you no longer want them.
14When RowFold support signs in
Sometimes the quickest way to help you is to see what you see. RowFold support can sign in to your workspace as one of its members, and only on these terms:
- You say yes first. Your workspace's owner or an admin either allows one visit when support asks, or allows support access for 7 days, in Settings → Privacy. An open support ticket is not permission on its own.
- Every visit has a reason, and a limit. Support writes down why it needs to look, and you see that reason word for word. A visit lasts at most 60 minutes. A second visit needs a new reason and a new sign-in check.
- Support sees what that member sees, and never more. A visit is view only unless you allowed changes. Some areas are always closed to support, whatever you allow: billing, security settings, API and app connection keys, data exports and account deletion.
- You can see every visit and stop one at any time. Every visit appears in Settings → Privacy and in your workspace's audit log, with anything support changed. You can end a visit in progress from Settings → Privacy. When a visit ends, the account's owner gets an email saying what changed.
- Without your permission, only for an emergency. Support can sign in without asking only to deal with a security problem, a report of abuse, or a legal demand. That visit is view only, the reason is recorded, and the account's owner is emailed as it starts.
15Contact
Privacy questions, access requests, or complaints: privacy@rowfold.com. Postal: RowFold LLC, 650 S Pearl St, Columbus, OH 43206.