Privacy Policy
This policy explains how Premsan Inc (“Premsan”, “we”, “us”) handles personal data in PerSQL — this website, the console, the API, and the PerSQL apps for iPhone, iPad and Android. Premsan is the controller of that data. A database is often the most personal thing a person keeps, so this page is written to be read, not skimmed: it says what we hold, why, who else touches it, and how to make us stop.
1. What we collect
- Your account. Your name, your email address, and either a password — stored only as a hash — or, when you sign in with Apple or Google, your identifier there and the sign-in tokens they hand us. Each session records the IP address and the browser or device it was opened from, and when it expires. We also record the date on which you accepted the Terms, and which version.
- What you bring. Your databases — every table and every row in them — the files you import to make them, the backups taken of them, the queries you save, the notes you write about your data, and the messages you exchange with the assistant. What goes in is your choice; PerSQL holds it exactly as you gave it, in a database that is yours, and you can change or delete any row, table, backup, query, note or database at any time.
- What the assistant reads. When you ask the assistant a question, the names of your tables and columns, the notes you wrote about them, a few sample rows, and the rows a query returns are sent to the model so it can answer. A change it proposes is written down for you to approve or discard, and nothing changes until you approve it.
- Keys and agents. A developer key you make is stored only as a hash, with the name you gave it and when it was last used. An agent you allow in through the browser is recorded with the name and address it registered, the tokens it holds, and the day you allowed it, until you remove it from your Account page or it stops asking.
- Exports and backups. When you export a database as SQL, SQLite or CSV, or take a backup, the file is written to our storage under your account until you delete it or the database it belongs to.
- The plan. The day your free week began, and the state of your subscription. On the web, payment is taken by Stripe: it receives your email address and your account id, and your card details go to Stripe and never reach us. We keep the subscription’s id, its customer id at Stripe, when it runs to and whether it renews. In the app, payment is taken by the App Store or Google Play; we receive the transaction’s id, confirm it with Apple or Google, and record it against your account.
- Usage. Counts of runs, queries and model tokens per month, kept inside your own account’s storage for our books. Server logs hold request metadata, your IP address among it, and error reports for a short time, for security and debugging.
- The bot check. Cloudflare Turnstile runs on our sign-in and sign-up pages, and in the app’s sign-in screen, to tell a person from a script.
- Nothing else. There is no advertising, no analytics, no tracking across sites or apps, no advertising identifier, and no data broker.
2. What we do with it
We use personal data to run PerSQL: to keep your databases and answer your questions about them, to import and export your files, to sign you in, to send you the emails the account needs — a verification link and a password reset — to take payment and keep your subscription’s state, to keep the service up and abuse out, to answer you when you write to us, and to meet legal obligations. We do not use your data or your conversations to train models, we do not sell personal data, and we do not share it for advertising.
3. Why we are allowed to
Where the GDPR or a law like it applies, we rely on these bases:
- Performing our contract with you — your account, your databases, your conversations, and the subscription. Without them there is no service to give you.
- Our legitimate interests — keeping PerSQL up, finding failures, and stopping abuse and automated sign-ups. We hold this to what running the product needs: the usage counts, the logs and the bot check, not profiling and not advertising.
- A legal obligation — payment records and anything else the law requires us to keep.
- Your consent — for anything the law treats as special that you choose to put in a database or a conversation. You give it by putting it in, and you withdraw it by deleting the database or the account.
4. Who else processes it
PerSQL runs on Cloudflare: the servers, the storage that holds your account and your databases, the model that answers your questions, the email that leaves, and the bot check are all Cloudflare services on our own account. No question of yours, and no row of yours, goes to any other AI provider. Email may instead be sent through Resend where we route it there. Stripe takes payment on the web and keeps the card; Apple and Google take payment in the app, and each tells us when a subscription you bought there renews, is cancelled or is refunded. When the app opens it asks Expo’s update service whether newer code of ours is waiting; that request carries the operating system, our project id and a random token the app made for itself — no account and no device identifier — and Expo sees the IP address it came from. These providers process data only on our instruction, and we give notice here before a new one starts.
Signing in with Apple or Google sends us your identifier and email from that provider. Each acts on its own behalf there, not as our processor, and its handling of your account with it is governed by its own privacy policy; if you hide your email from us with Apple, mail reaches you through Apple’s relay. The App Store and Google Play are the sellers of what you buy inside the app, and their handling of your payment is governed by theirs.
5. Where it is
Your data is processed on Cloudflare’s network, which spans the world, and stored on it under Cloudflare’s own commitments for international transfers. Premsan is in Japan, a country the European Commission recognises as protecting personal data adequately.
6. On the phone
The app keeps on your device a sign-in token, the language and appearance you picked, the random token its update check is known by, and, when you export a database or a table, a copy of that file in the app’s own cache for the share sheet. It reads your files only when you tap Import and pick something; nothing is read in the background, and it asks for no other permission. Purchases go through the store’s own sheet. The app carries no advertising or analytics library, and the one review prompt it may ever show is the operating system’s own, asked for once after you have exported your first database.
7. Cookies
On the web we set the cookies the product cannot work without: the one that keeps you signed in, and the ones Cloudflare Turnstile sets to tell a person from a bot on the sign-in and sign-up pages. The site and the console keep your theme and language in your browser’s own storage. That is the whole list: no advertising cookies, no cross-site trackers, and no analytics that follows you between sites, which is why nothing asks you to accept anything on arrival. Clearing them signs you out.
8. How long we keep it, and deleting it
We keep your account and everything in it for as long as the account exists. Deleting a backup, a saved query or a note removes it. Deleting a database removes it, its rows, its backups, its exports, its saved queries, its notes and its conversation. Verification and reset links expire on their own.
You can delete your account at any time, from the console’s Account page or from Account in the app. Everything we hold for you is erased at once — every database, backup, export, query, note, conversation, usage count and the subscription’s state — and then the account itself. There is no recovery window and no undo.
Three things outlive that, and we would rather name them than let you find out. A subscription bought in the app leaves a record of the store’s transaction id, the date, and the id of the account it was kept for, so that the store replaying the receipt cannot credit it to someone else and because payment records must be kept by law; the account it names no longer exists. Stripe, Apple and Google keep their own records of a payment under their own obligations. Server logs age out on their own after a short time.
9. Your rights
You can read, correct and delete every row, table, backup, query, note and database yourself, export any database as SQL, SQLite or CSV, and delete your account, without asking us. Depending on where you live, you may also have the right to a copy of the rest of what we hold about you, to restrict how we process it, to object to processing we base on legitimate interests, to withdraw consent where we relied on it, and to move your data elsewhere. Write to support@persql.com and we will answer within one month.
If you live in California or another U.S. state with a law like its, you have the right to know what personal data we hold about you, to delete it, and to correct it; the controls above do that. We do not sell or share personal data as those laws define the words, so there is no opt-out to offer, and exercising a right gets you the same service on the same terms.
If you think we have handled your personal data wrongly, you can complain to a data protection authority — in the EEA or the United Kingdom, the one where you live or work or where the problem happened; in Japan, the Personal Information Protection Commission. We would rather you told us first, but you do not have to.
10. Security
Every connection is encrypted in transit. Passwords are stored as hashes. Each person’s account, and each of their databases, lives in its own isolated storage object, and every byte of it is deleted with the account. The app keeps its sign-in token in the operating system’s secure store, never a cookie. Credentials never enter our logs. If you find a weakness, write to security@persql.com and give us a chance to fix it before you tell anyone else.
11. Children
PerSQL is not for anyone under 16, and we do not knowingly hold a child’s data. If you think a child has an account, tell us and we will delete it.
12. Changes
We may update this policy. When a change matters we will say so in the console or the app, or by email. The date at the top is the version that stands.
13. Contact
Premsan Inc — 530-0001, 12-12, Osaka Ekimae Dai-2 Bldg., 1-2-2 Umeda, Kita-ku, Osaka-shi, Osaka, Japan. support@persql.com.