Privacy Policy

Last updated: 15 November 2026

RunLite (“RunLite”, “we”, “us”) provides website hosting, a form backend, and a connector for AI coding tools (“the Service”). This policy explains what data we collect and why.

1. Who this policy is for

Three groups of people interact with the data RunLite handles, and this policy covers all of them:

  • Account holders — the developer, agency, or business that creates a RunLite account, deploys a site, and configures a form.
  • Visitors — anyone who fills out a form embedded on a site an account holder has deployed. Their form submissions are collected on the account holder’s behalf, not ours. RunLite acts as a data processor for this data; the account holder is the data controller and is responsible for how their own visitors’ data is used, consistent with whatever they’ve told their own customers.
  • Photo senders — anyone an account holder on a paid plan shares a photo link with, who uses it to send photos for the account holder’s site. The photos go to the account holder, who decides whether to publish them. We also keep a few details about the sender for our own abuse prevention, described below.

2. What we collect

About an account holder:

  • Email address, which you confirm when you sign up, with a one-time code or through Google sign-in
  • API keys — we store only a SHA-256 hash and a short display prefix; the full key is shown once, at creation, and never again
  • Site files uploaded for hosting, and form definitions
  • Photos you upload for your sites. We remove location and camera details (EXIF) from every photo when we process it
  • PDFs you upload to replace one on your site (a menu or a brochure, on a paid plan). We scan each one for malware and check that it has no scripts, attachments or form actions before it can be published; one that fails is deleted
  • If you report a photo someone sent through your photo link: the report, and any note you add
  • Billing details processed via Razorpay (we never see or store card numbers — see Section 5)
  • For invoices on a paid plan: your state, and a business’s GSTIN and legal name if you give them
  • How much each of your sites is used: daily totals of data served and requests, counted from the access logs below
  • If you turn on WhatsApp enquiry alerts: the WhatsApp number that receives them, when it opted in or out (by sending START or STOP to our WhatsApp number), and whether each alert was delivered
  • If you ask RunLite to build a website for you (Build for me): the business’s name, the email address for its enquiries, what you tell us about the business (the text you paste and your answers to our questions, with any contact details in them), and what we understood from it. Also a one-way fingerprint of your IP address (not the address itself), used only to limit how many free checks one connection can start

About a visitor submitting a form:

  • Whatever fields the account holder’s form asks for
  • IP address, user agent, and referring page, used for spam filtering and rate-limiting
  • A basic automated spam score

If the account holder has turned on WhatsApp enquiry alerts, the alert sent to them names the site and form and, when the form asks for them, the visitor’s name and phone number. Never the visitor’s message.

About someone sending photos through a photo link:

  • The photos, with location and camera details removed. They appear on the account holder’s site only if the account holder publishes them
  • Your IP address and browser (user agent), kept for 180 days and never shown to the account holder. If a photo is identified as child sexual abuse material, they are kept with the record of it and may be given to the police

About anyone visiting a site hosted on RunLite:

  • Our content delivery network (Amazon CloudFront) logs each request: IP address, user agent, the page asked for and how much data was sent. We use these logs only to measure each site’s bandwidth, and keep only the daily totals per site.

About someone reporting abuse through our Report abuse form:

  • The address and description you report, and your email address if you choose to give it
  • A one-way fingerprint of your IP address (not the address itself), used only to limit how many reports one person can send

3. Why we collect it

  • To provide the Service — hosting, form delivery, notifications
  • To prevent abuse — spam filtering, rate limiting, and automated checks of deployed sites for phishing and malware
  • To keep photo links safe — checking photos sent through them for explicit content, and keeping child sexual abuse material as evidence and reporting it to the police, as Indian law requires
  • To keep uploaded PDFs safe — scanning them for malware before they can be published
  • To build a website for you when you ask us to — an AI model reads what you tell us about the business and writes the site from it
  • To bill for paid plans and issue invoices
  • To measure each site’s use against its plan’s allowances, and tell the account holder as they approach them
  • To communicate with account holders about their account

We do not sell personal data, and we do not use form-submission data for advertising.

4. Retention

  • Form submissions are retained for 90 days by default, then deleted automatically. An account holder can configure a different retention period for their own account.
  • WhatsApp alert records (which enquiry, which number, whether it was delivered) are deleted after 90 days.
  • Rate-limiting records (used to detect abuse) are deleted after 24 hours.
  • Content delivery access logs are deleted after 7 days.
  • Invoices, with the billing details on them, are kept for as long as Indian tax law requires (about six years), even after the account is deleted.
  • Abuse records — the reasons for any deployment we refused, site we flagged or took offline, or account we suspended, and what a deleted site contained (file names and fingerprints, never the files or form submissions) — are kept for 180 days to investigate abuse reports, then deleted.
  • Abuse reports sent through our Report abuse form, and photos account holders report, are kept for 180 days, then deleted.
  • Photos and PDFs that are never published, whether uploaded by an account holder or sent through a photo link, are deleted after 30 days. A PDF that fails its malware scan or checks is deleted at once; if it held malware, we keep a record of that (the name of what was found, never the file) with our abuse records.
  • Photo senders’ IP addresses and browsers are deleted after 180 days.
  • What you give Build for me (the text about the business, your answers, and what we understood from it) is deleted 30 days after the check or build it was for has ended. The website it made stays until you delete it, and so does what we understood about the business when we built it (its details, the plan of its pages and their words), with what you asked for in each change you made to it that is on the site, which we use to change the site when you ask; all of it is deleted with the site. We keep a record that the build ran and what it cost us.
  • Child-safety records — a photo identified as, or reported as, child sexual abuse material, kept unopened in locked storage, with the details of how it was found and who sent it — are kept for 180 days, then deleted, unless the police ask us to keep them longer.
  • Fingerprints of images we removed for abuse (never the images themselves) are kept so the same image can’t be uploaded or published on RunLite again.

5. Who else sees this data

We use the following service providers to run RunLite. Each only sees the data it needs to perform its function:

  • Amazon Web Services (ap-south-1, Mumbai) — hosting, file storage, compute; Amazon Rekognition, which checks photos sent through a photo link for explicit content; and Amazon GuardDuty, which scans uploaded PDFs for malware. Sees site files, uploaded photos and PDFs, and submission data.
  • Supabase — database and authentication. Sees account and submission data.
  • Razorpay — payment processing. Sees billing details; we never see card numbers.
  • Resend and Amazon Simple Email Service (part of Amazon Web Services) — transactional email delivery. See the content of the emails they deliver.
  • Meta Platforms (WhatsApp Business Platform) — delivers the WhatsApp enquiry alerts an account holder turns on. Sees the receiving number and the content of each alert.
  • Anthropic — provides the AI model that reads what you give Build for me and writes the site. Sees the business’s name, the email address for its enquiries, and the text and answers you give. It does not see form submissions, photos or billing details. While building, the model also searches the web for the words used in the business’s trade, from what the business does, what it sells and where it is. Anthropic processes this outside India, including in the United States. Its terms say it does not use it to train its models, and that it deletes it within 30 days, or keeps it for up to two years if its automated checks flag it as breaking its usage rules.

We give information to the police when Indian law requires it: for example, a report of child sexual abuse material, with the material and where it came from.

6. Your rights

Depending on where you’re located, you may have rights to access, correct, or delete your personal data. Account holders can request deletion of their account and its data at any time by contacting us. Visitors who submitted a form should contact the account holder whose form they submitted — the data controller for that submission. We can assist an account holder with a request but do not have an independent relationship with visitors.

7. Security

API keys are stored only as SHA-256 hashes, never in plain text. Database access that bypasses row-level security is limited to trusted server-side code; the dashboard itself never receives elevated privileges. Our Security page describes the rest.

8. Changes to this policy

We may update this policy from time to time. We’ll update the date at the top when we do.

9. Contact

Questions about this policy: support@runlite.in