Privacy Policy

2.1 Who is responsible

Mohammad Amaan, Indiranagar, Bengaluru, 560008, India, is the controller of personal data processed through Runsheet. Data questions go to privacy@runsheetforyou.com.

Where you use Runsheet to hold information about other people — a couple's names, another vendor's phone number — you are the controller of that information and we process it on your behalf. Section 2.10 covers that arrangement.

2.2 What we collect

You give us:

• Account: your email address, and your name if you provide one.
• Business profile: business name, category, base city, service area, and optionally a logo, website and Instagram handle.
• Events you create: couple names, dates, venue, timezone, guest count.
• Timelines: each item's label, time, duration, notes, who is responsible and who may see it.
• People you invite: the email addresses you enter, and the role you assign.
• Documents: files you upload — contracts, floor plans, shot lists, certificates of insurance — and their type and visibility.
• Messages: what you write in an event's thread.
• Payment milestones: labels, amounts, due dates and status. These are your own records of what a couple owes you. We do not verify them and no money moves.
• Directory listing: anything you choose to publish, including photographs.
• Support: what you write to us.

We collect automatically:

• Sign-in and session data, so we know it is you.
• Product analytics — pages visited, features used, and a pseudonymous identifier — through PostHog, subject to your cookie choice.
• Error reports through Sentry when something breaks, which may include the page you were on and technical details of the failure.
• Server logs including IP address, for security, abuse prevention and debugging.

We do not collect: card numbers or any payment instrument details. Those go directly to Dodo Payments and never reach our systems. We also do not collect government ID, health data, or any special-category data, and you should not put any into Runsheet.

2.3 Why we use it, and on what basis

We do not sell personal information, and we do not share it for cross-context behavioural advertising. If we later run advertising on the public directory and guide pages, those ads will not be targeted using anything from inside the application, and the cookie banner will govern them.

2.4 Who else sees your data

Other people on an event. This is the point of the product, so it is worth being precise.

• Everybody on an event sees the event's details, the timeline items marked visible to them, the vendor list, and the message thread.
• Your email address and phone number are not shown to other vendors on an event unless you turn contact sharing on, and that choice is per event, not per account.
• A couple's read-only link shows only items marked visible to everyone, and no vendor's contact details unless both the event owner and that vendor have opted in.
• Documents are visible according to the visibility set on each one.

Our sub-processors. The companies that host, send, monitor and bill on our behalf. They are listed with what each one receives at /sub-processors.

The public. Only what you publish to your directory listing.

Others, when we must. If the law requires it, to enforce our terms, to protect somebody's safety, or in connection with a sale of the business — in which case you would be told beforehand.

2.5 Where your data lives

Runsheet's database and file storage are hosted in the United States. Our sub-processors operate in the United States and the European Union. Runsheet is operated from India, which means personal data is accessed from there.

Where personal data of people in the UK or EEA is transferred out of those areas, we rely on the European Commission's Standard Contractual Clauses, which are in place with the sub-processors that handle it.

2.6 How long we keep it

• Account and business profile: while your account exists.
• Events, timelines, documents and messages: while the event exists in an account that has not been deleted. Deleting an event deletes its content.
• Uploaded files: deleted from storage when the document record is deleted.
• Invitation tokens: expire after 30 days and can be revoked sooner.
• Change history: kept for the life of the event, because "who moved the ceremony" is part of what the product is for.
• Billing records: kept for as long as tax and accounting rules require.
• Server logs: short-lived, weeks not years.
• Backups: routine backups are retained on a rolling basis and overwritten; data you delete disappears from backups as they roll.

2.7 Your rights

Wherever you are, you can ask us to give you a copy of your data, correct it, delete it, or stop a particular use of it, by writing to privacy@runsheetforyou.com. We will respond within 30 days.

If you are in the UK or EEA, you have the rights to access, rectification, erasure, restriction, portability and objection, and the right to withdraw consent at any time without affecting processing already carried out. You may complain to your national data protection authority.

If you are in California, you have the rights to know, to delete, to correct, and to opt out of sale or sharing. We do not sell or share personal information as those terms are defined, so there is nothing to opt out of, and we will not discriminate against you for exercising a right.

Deleting your account removes or anonymises your personal data. Content you contributed to another vendor's event — a comment, a timeline item you created — is anonymised rather than removed, because deleting it would silently alter somebody else's record of their wedding.

2.8 Security

What we actually do:

• Every request is authorised in the database itself through row-level security, not only in the application. A vendor cannot read another vendor's event even by calling the API directly.
• Uploaded documents live in a private bucket with no public URL. They are served only through short-lived signed links issued per request against the caller's own access to that event.
• Traffic is encrypted in transit; the database is encrypted at rest by our host.
• Sign-in is by emailed link or Google. There are no passwords to leak.
• Invitation tokens are long random values, single-event, expiring and revocable.
• Sending of emails and invitations is rate limited.

What we do not do, stated plainly because you should know: we do not currently scan uploaded files for malware, and we hold no security certification such as SOC 2 or ISO 27001. No service is perfectly secure. If you find a vulnerability, write to support@runsheetforyou.com and we will take it seriously; see /security.

2.9 Children

Runsheet is a business tool and is not directed at anybody under 18. We do not knowingly collect data from children. If you believe a child has given us data, write to privacy@runsheetforyou.com and we will delete it.

2.10 When you are the controller

Information you put into Runsheet about other people — a couple's names and dates, a co-vendor's phone number, a guest count — is yours, and you decide what goes in. We process it on your instructions to provide the Service, do not use it for our own purposes, keep it confidential, apply the security measures in §2.8, use only the sub-processors listed at /sub-processors, help you respond to any request from the person concerned, and delete or return it when you close your account. A data processing agreement on these terms is available at /dpa.

2.11 Changes

We will update the effective date when this changes, and will tell you by email if a change materially affects you.

2.12 Contact

privacy@runsheetforyou.com · Mohammad Amaan, Indiranagar, Bengaluru, 560008, India