Privacy Policy

Your name, email address and a hashed password — or, if you sign in with Google, what Google tells us when you allow it: your name, email address and profile picture. If you turn on two-factor authentication we hold the secret behind it and your backup codes. We hold sessions so you stay signed in, and a record of the devices you are signed in on so you can end one.

The name and address of the organization you bill under, your billing currency, your storefront’s handle, and everything you publish on it — titles, descriptions, images and the files you share.

If you are on the paid plan: your subscription, its renewal dates and its invoices. Your card or UPI details go to our payment provider, not to us. We do not hold your PAN, your Aadhaar or your bank account details.

• A payment account, only if you connected one before storefronts stopped taking payments. We hold its access tokens, encrypted, and the account identifier, and use them for nothing; write to us and we remove them.
• A Google Calendar, if you connect one for your sessions or webinars. We read your availability and write the events you schedule. We ask for no more than that and use it for nothing else.
• An Instagram account, if you use automatic replies. We hold the tokens and the rules you wrote, and we send only the messages those rules describe.

Disconnect any of them and we stop using it. Tokens are encrypted at rest and are deleted when the connection is removed; what an Instagram connection synced is deleted on the schedule in section 8.

Your email address, the name you gave, what you got, the answers to any question the creator asked, your timezone, and the IP address the request came from. Where you registered for a webinar, the session you chose.

Any card number, UPI ID or bank detail. Nothing on a storefront is paid for, so none is ever asked for.

A customer list: who got what from their storefront, and when, including everyone who signed up with an email address. They can add their own tags and notes. They can export it, because it is their customer relationship rather than ours — which is the whole point of the product, and the reason to think of them as the one holding your details.

We count visits to a storefront so its creator can see what is working: the page, the referring site, a device type and a coarse platform. To count a person twice in one day without identifying them, we store a hash that is scoped to a single day and throw the user-agent away — so the same visitor tomorrow is a different, unlinkable record, and there is no profile to build.

Signup is protected by Cloudflare Turnstile, which sees your IP address and some signals about your browser in order to decide whether you are a person. We receive its verdict, not its evidence.

If you accept analytics in the cookie banner, Google Analytics 4 tells us which pages were read and roughly where readers came from. It runs only after you accept, and never for advertising. If you decline, no Google script is loaded and no analytics cookie is set.

Mail sent to the addresses on this site, and our replies. We keep the thread so the conversation makes sense next time.

A session cookie keeps you signed in to the dashboard, and is set for admin.pullsy.store alone so it is never sent to a creator’s storefront. pullsy_cookie_consent records your answer to the banner so we do not ask again for 180 days. pullsy_theme remembers whether you chose light, dark or your system setting; it holds nothing but that word, and it is set for pullsy.store and admin.pullsy.store together so your choice survives signing in. Cloudflare Turnstile may set a short-lived cookie of its own while it checks a signup.

Google Analytics 4 sets _ga and _ga_<id>, and only after you accept. Choose “No thanks” and we delete them; change your mind later through Cookie preferences at the bottom of the page, and withdrawing clears them again.

Deletion is immediate and irreversible. Removing your workspace removes the storefronts, products, orders, customer records, uploaded files and connected accounts under it in the same operation — there is no state in which half of it survives, and no recovery window in which we could restore it. Export anything you want to keep first.

Two things stop a deletion rather than being swept up by it: an active subscription, which you cancel first, and something a customer was promised and has not yet received, which is owed to them rather than a record of ours.

We keep an audit entry that the deletion happened — its date, the workspace name, and the email address of whoever asked for it. It survives on purpose: without it we could not answer a later question about what became of an account, including from the person asking us to prove we deleted it.

Write to hello@pullsy.store and we will do any of the following: send you a copy of what we hold, correct it, or delete it. We answer within 30 days and we do not charge for it. Where the law requires us to keep a record — a paid invoice, for example — we will say so rather than quietly keeping it.

Ask the creator first: they decide what happens to their customer records, and they can act immediately. Write to us at the address above if you cannot reach them or would rather not, and we will pass the request on and follow it up.

You also have the right to restrict or object to processing, to receive your data in a portable format, to withdraw consent at any time without affecting what came before, and to complain to your supervisory authority.

You have the right to access, correction, erasure and grievance redressal, and to nominate someone to exercise those rights on your behalf. Grievances reach us at the address above and are handled by the people who run the service.