Privacy Policy

Gsheet CRM is operated by Libromi (“we”, “us”). This page explains what data the service touches, where it lives, and who else is involved. The short version, which is also the product’s design: your customer records live in your own Google Sheet, not on our servers.

The one-file Google permission

When you connect Google, we request drive.file — Google’s narrowest Drive permission. It lets the app open only the spreadsheet created for or connected by you, and nothing else in your Drive. We cannot see, list, or open any other file. We also receive your Google account’s email address to identify you at sign-in.

What stays in your spreadsheet

Your leads, their names and phone numbers, notes, follow-up text, activity history, and linked-table rows are stored in the Google Sheet you own. Delete the app or cancel your subscription and every row stays exactly where it always was — in a spreadsheet that keeps working without us.

What we store on our servers

• Your account: name, email, and — for password accounts — a salted, hashed password (never the password itself).
• Your workspace’s configuration: which spreadsheet is connected, what its columns mean, stage colours, automation rules, team members and roles.
• Follow-up times (so reminders can fire) — the reminder’s text stays in your sheet.
• An audit trail of actions (“lead created”, “stage changed”) — field names, never field values.
• The encrypted key Google gives us to open your one file, encrypted again at rest with a per-workspace key.
• Company details you give at signup (company name, country, website, team size) and billing state (plan, trial and subscription status).

A short-lived working copy

To keep the board fast, recently viewed sheet data passes through a cache for up to ten minutes. It is encrypted per-workspace, expires on its own, is deleted when you make a change, and is never used as a store of record — it exists so we don’t re-read your sheet on every click.

Who else is involved

We use a small set of service providers, each for one job:

• Google — sign-in, and the Sheets/Drive APIs that read and write your spreadsheet.
• Vercel — hosts the application and tells us the country of a visit (for showing prices in the right currency).
• Neon — the database holding the configuration listed above.
• Upstash — the encrypted short-lived cache.
• Brevo — sends transactional email (password resets, reminder notifications).
• Libromi’s billing platform and its payment gateways (Stripe, Razorpay) — subscriptions, invoices, and payments. Card details go directly to the gateway; we never see or store them.

We do not sell your data, and we do not use your data — or your customers’ data — for advertising or to train AI models.

Cookies

One session cookie keeps you signed in. Browser storage remembers small preferences — your theme, your chosen workspace, a dismissed notice. There are no third-party advertising or tracking cookies.

If you connect Team Inbox

A workspace can also run inside Libromi Team Inbox. Linking the two shares only identifiers — never your leads, notes, or teammates’ emails — and either side can be disconnected without touching your spreadsheet.

Retention and deletion

We keep the data above while your account exists. Disconnecting Google immediately removes our ability to open your sheet. To delete your account and workspace configuration entirely, email us — we’ll confirm and remove it. Your spreadsheet is yours and is never deleted by us, ever.

Security

Google access keys are encrypted at rest with per-workspace keys, every database table enforces tenant isolation at the database level, sign-in attempts are rate-limited, and all traffic runs over HTTPS. No system is perfect; if we learn of a breach affecting your data we will tell you promptly.

Children

Gsheet CRM is a business tool and is not directed at children under 16.

Changes and contact

If this policy changes materially we’ll note it here with a new date. Questions or requests: support@libromi.com.