Privacy Policy
This policy explains how Premsan Inc (“Premsan”, “we”, “us”) handles personal
data in inqry.link — this website, every page at inqry.link/
1. What we collect from owners
- 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.
- Your links. Each link’s name and page — the name, the line about you, your links, your photo, the greeting and the suggested questions — your instructions to the assistant, and how it answers.
- Your library. The files you add and the notes you write, the text we read out of them, and the passages we cut that text into so the assistant can search it. A photo or image is read by the model to write out its text and describe it.
- Notifications. When you allow notifications on your phone, we keep the push token the operating system gives the app, the platform, and the language the app last used, so we can tell you when a visitor needs you.
- 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. 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. Per link and per month, how many answers were written, how many tokens they took and what they cost us, and how many files were read, kept inside the link’s own storage for our books.
2. What we collect from visitors
- Your conversation. What you write to a link, the replies — the assistant’s and the owner’s — and when each was sent. When the assistant cannot answer and you give a name and an email or phone number, or type them into the page, we keep them with the conversation so the owner can reach you.
- Your browser. The page keeps a random token in your browser’s own storage so you can come back to the conversation; the conversation is known to us only by that token’s hash. The language your browser asks for decides the page’s words.
- Your address. The IP address of each request is used to pace how fast one address can write to a link, and appears in server logs for a short time. Opening a conversation passes Cloudflare Turnstile, which tells a person from a script.
- Nothing else. No account, no tracking across sites, no advertising.
3. What we do with it
We use an owner’s data to run inqry.link: to show their pages, read their files, answer their visitors from them, tell them when a visitor needs them, sign them in, send the emails the account needs — a verification link and a password reset — take payment and keep their subscription’s state, keep the service up and abuse out, answer them when they write to us, and meet legal obligations. We use a visitor’s data to answer them, to hand their conversation and contact to the owner of the link they wrote to, to email them the owner’s reply when they left an address and the owner answered personally, and to stop abuse. We do not use anyone’s data or conversations to train models, we do not sell personal data, and we do not share it for advertising.
4. Why we are allowed to
Where the GDPR or a law like it applies, we rely on these bases:
- Performing our contract with the owner — their account, their links, their library, their inbox, and the subscription.
- Processing for the owner — what a visitor writes to a link, and the contact they leave, we process on the owner’s instructions, to run their link; the owner decides why they collect it and answers to the visitor for it. A visitor who wants a copy of their conversation, or wants it deleted, can ask the owner, who can delete it from their inbox, or ask us and we will pass the request on.
- Our legitimate interests — keeping inqry.link up, finding failures, and stopping abuse, automated messages and automated sign-ups, held to the usage counts, the logs, the pacing and the bot check.
- A legal obligation — payment records and anything else the law requires us to keep.
5. Who else processes it
inqry.link runs on Cloudflare: the servers, the storage that holds every account, link, library and conversation, the model that reads images and writes every answer, the conversion of documents into text, the email that leaves, and the bot check are all Cloudflare services on our own account. Nothing 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. A notification to an owner’s phone is handed to Expo’s push service, which passes it to Apple or Google to deliver; it carries the push token, the link’s name and the visitor’s words it is about. 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.
The owner of a link sees everything written to it. What an owner does with a visitor’s conversation and contact once they have it is up to them, under their own obligations to that visitor.
6. Where it is
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.
7. On the phone
The app keeps on the owner’s device a sign-in token, the language and appearance they picked, and the random token its update check is known by. It asks to send notifications once, when the first link is made, and they can be turned off in the operating system’s settings. It asks for access to photos or files only when the owner chooses to add one, carries no advertising or analytics library, and purchases go through the store’s own sheet.
8. Cookies
On the web we set the cookies the product cannot work without: the one that keeps an owner signed in, and the ones Cloudflare Turnstile sets to tell a person from a bot. The site, the console and each page keep the theme, the language and a visitor’s conversation token in the browser’s own storage. That is the whole list: no advertising cookies, no cross-site trackers, and no analytics that follows anyone between sites.
9. How long we keep it, and deleting it
We keep an owner’s account and everything in it for as long as the account exists, and a conversation for as long as its owner keeps it. An owner can delete any file, note or conversation, and deleting a link deletes its page, library and every conversation on it.
An owner can delete their account at any time, from the console’s Account page or from Account in the app. Everything we hold for them is erased at once — every link, page, file, note, passage, conversation, contact, push token, usage count and the subscription’s state — and then the account itself. It cannot be undone.
Four things outlive that. 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. Stripe, Apple and Google keep their own records of a payment under their own obligations. Cloudflare keeps restorable copies of our databases for up to 30 days, so they can be brought back after a failure, and then they expire. Server logs age out on their own after a short time.
10. Your rights
An owner can read, export by copying, and delete everything above from the console, 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, and to move your data elsewhere. Write to support@inqry.link and we will answer within one month; a visitor’s request about a conversation we pass to the link’s owner, and act on it ourselves where the owner cannot be reached.
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. We do not sell or share personal data as those laws define the words, so there is no opt-out to offer.
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.
11. Security
Every connection is encrypted in transit. Passwords are stored as hashes. A visitor’s conversation is reached only with the token their browser holds, and we keep only its hash. Each account and each link 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. Credentials never enter our logs. If you find a weakness, write to security@inqry.link and give us a chance to fix it before you tell anyone else.
12. Children
Accounts are not for anyone under 16, and we do not knowingly hold a child’s account. If you think a child has an account, tell us and we will delete it.
13. 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.
14. Contact
Premsan Inc — 530-0001, 12-12, Osaka Ekimae Dai-2 Bldg., 1-2-2 Umeda, Kita-ku, Osaka-shi, Osaka, Japan. support@inqry.link.