PROMPTLENCE AI / LEGAL

Privacy Policy

What PromptLence AI collects, why, and what you can do about it.

Version 1.0Effective 10 August 2026English is authoritative
This document is published in English. If a future translation and this English text disagree, the English text applies.
01

What this covers

This policy describes how PromptLence AI handles information when you use the application. It describes the product as it is actually built, not as a general template. Where something is a limitation rather than a promise, it is written as one.

02

Account information

Accounts are handled by Firebase Authentication. Depending on how you sign in, this means either your email address and a password you set, or a Google sign-in.

From your account we hold an account identifier, your email address, the display name and profile image associated with the account, whether the email is verified, and when the account was created. We do not receive or store your Google password. If you use email and password sign-in, the password is handled by Firebase Authentication and is never stored by us in readable form.

03

Content you submit

When you use the prompt generator, chat, image or video studios, the text you write is sent to our backend and forwarded to the AI provider to produce a response.

Your prompts, the generated responses, your chat history, and your saved or favourited items are stored under your account so the application can show them back to you.

  • Do not put passwords, payment card numbers, government identifiers, or other people’s personal details into prompts.
  • Anything you submit is processed by an external AI provider, so treat it as leaving your device.
04

AI processing

Generation is performed by Google’s Gemini models. Your prompt is sent to that provider through our backend in order to produce a result. We do not control, and do not make promises about, how the provider operates internally beyond the terms it publishes.

Requests reach the provider through our server rather than directly from your device, so the provider API key is never present in the application you run.

05

Usage and quota information

To enforce plan limits and protect the service, we record counts of generation requests per account per day, along with the studio or category a request belonged to and the plan in force at the time. These records are operational, not advertising, data.

06

Billing information

Paid plans are processed by Razorpay. Payment is completed on Razorpay’s side. Card numbers, UPI credentials and bank details are entered with Razorpay and are not received or stored by PromptLence AI.

We store the subscription reference Razorpay gives us, the plan purchased, the subscription status, and the period the subscription is paid through. We use this to decide what your account is entitled to and keep it as a financial record.

07

Support messages and attachments

If you send feedback or a support report, we store the message, the category and rating you selected, basic application and device information you chose to include, and any screenshot you attached. This exists so support requests can be answered.

08

Security and diagnostic records

Our backend logs the type of an error when a request fails, so faults can be diagnosed. These logs are written deliberately to exclude prompt content, provider keys and payment secrets. Standard infrastructure logs are also produced by Google Cloud as part of running the service.

09

Storage on your device

The application stores your preferences—theme, language, model and workspace defaults—and a cache of your history on the device so it can start quickly and work offline. Firebase Authentication stores a session token so you stay signed in.

On the web, offline/PWA caching is deliberately switched off, and the application shell is revalidated on every load so you are not left running an outdated version.

10

Who else is involved

These providers process data in order to deliver the parts of the service they are responsible for. We do not sell your information, and we do not send your prompts or conversations to advertisers.

  • Google Firebase — authentication, database, file storage, and hosting.
  • Google Gemini — AI generation.
  • Razorpay — subscription payments.
11

How long we keep things

Your profile, prompts, chats and saved items are kept until you delete them or delete your account. Usage counters are operational records tied to your account and are removed with it.

Payment and subscription records are kept after account deletion. They are the accounting record of payments that happened and the evidence needed to answer a disputed charge, so they are retained rather than destroyed. They contain subscription and amount information—not your prompts, chats or generated content.

12

Deleting your account

You can delete your account from Settings. Deletion asks you to confirm, requires you to sign in again first, and is then carried out by our backend.

It removes your profile, prompt history, chats, notifications, usage counters, generation records including generated text, entitlement records and support attachments. Support tickets are anonymised rather than deleted. Payment records are retained as described above. Your sign-in identity is removed last, once everything else has genuinely succeeded.

13

Your choices

  • Access and correct your profile information in Settings.
  • Delete individual prompts and chats, or clear your history, at any time.
  • Delete your entire account from Settings.
  • Contact us with a privacy question using the Support page.
14

Security, honestly stated

We take real measures: authentication is handled by Firebase, our database and storage rules restrict every record to its owner, privileged billing and quota records can only be written by our backend, payments are verified server-side before any paid access is granted, and the web application is served with strict security headers.

No online service can promise perfect security. We do not claim to be unbreachable.

15

Children

PromptLence AI is not intended for children under 13, and accounts should not be created for them.

16

Changes

If this policy changes materially, the version and effective date at the top of this document will change. Continuing to use the service after an update means the updated policy applies.

17

Contact

Privacy questions can be sent through the Support page in the application.