Privacy Policy
This policy explains how Premsan Inc (“Premsan”, “we”, “us”) handles personal
data in Inqry — 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 give 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, and the day you last used the account.
- 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 split 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.
- Your assistant. What you write to the assistant that works on your link, its replies, and the changes it proposes to your page and notes, with whether you approved or discarded each, kept with the link until you clear the conversation or delete the link. When you turn on voice mode, here or in Try it, what you say is recorded and sent to be written down as text; the text goes to the assistant as your message, and the recording is deleted once it is written down. Replies are read aloud by your own device’s voice.
- What the assistant remembers. The facts you tell the assistant about yourself, your work and how you want it to work, kept as memories so every later conversation starts with their titles and descriptions: each one’s kind, title, description and details, whether you or the assistant wrote it last, and when. You see and delete them in Settings, and correct one by telling the assistant; their titles and descriptions go to the model with every message you send it, and a memory’s details when the assistant opens it; an answer to a visitor reads none.
- 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 that we can tell you when a conversation needs you. We delete it when you sign out on that phone, or when the push service reports that it is no longer valid.
- The plan. The day you began using Inqry free, what the assistant’s answers have cost while free, 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, the number of links it holds, 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.
- Help. When an owner writes to us from Help, we keep their messages, the pictures they attach, our replies, and details that help us answer: whether they wrote from the web or the app, their browser or app version and operating system, their language, the page or screen they came from, the size of their window or screen, their time zone and their most recent failed requests to our servers. They are kept with the account until it is deleted.
- 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 accounting.
How far you get is recorded as you go: the day you sign up and each day you come back, whether on the web or the phone app and in which language; when you allow the assistant; when each request to it ends, which of its agents answered and whether it worked; when you reach what is free; when you pay, and through which store; when you make a link; and when your link’s assistant answers a visitor, never who they are or what they asked. Each record carries a random number kept in your account’s storage, never your name, your address or anything you wrote or made, and we read the records only as counts, to see where people stop. Deleting your account deletes the number; the records stay, with nothing in them that leads back to you.
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 voice. When you turn on voice mode on a page, what you say is recorded and sent to be written down as text; the text goes to the link as your message, and the recording is deleted once it is written down. Replies are read aloud by your own device’s voice. The page uses the microphone only while voice mode is on, and your browser asks your permission first.
- 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 requests sets the language of the page.
- 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, or speaking before one is open, goes through Cloudflare Turnstile, a check that 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: to show their pages, read their files, answer their visitors from them, work on their page and library with them through their assistant, show them the conversations that need them and notify their phones of those, 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 running and prevent abuse, 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 up, finding failures, and stopping abuse, automated messages and automated sign-ups, limited to the usage counts, the logs, the pacing and the bot check. Seeing where people stop, from the record of how far you get, rests on it too.
- A legal obligation — payment records and anything else the law requires us to keep.
5. Who else processes it
Inqry runs on Cloudflare: the servers, the storage that holds every account, link, library and conversation, the model that writes down what is said in voice mode, the conversion of documents into text, the email that leaves, and the bot check are all Cloudflare services on our own account. The model that reads images, writes every answer and works with owners on their links runs at Anthropic, reached through Cloudflare. Anthropic does not train a model on what it is sent and deletes it under its own retention policy; when Anthropic cannot answer, the same request goes to OpenRouter, which does not train a model on it and passes it only to a model host that keeps nothing once it has answered, or else to Cloudflare Workers AI. Nothing goes to any other AI provider, and we do not keep a recording of anyone’s voice. Some email may be sent through Resend instead. Stripe takes payment on the web and keeps the card details; Apple and Google take payment in the app, and each tells us when a subscription bought there renews, is cancelled or is refunded. A notice 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 and the notice’s text, which can be what a visitor wrote. When the app opens, it asks Expo’s update service whether a newer version of our code is available; that request carries the operating system, our project id and a random identifier the app created 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.
When the assistant searches the web, the words it searches for, which it writes from your conversation, go through Cloudflare to Linkup, or to Ceramic.ai when Linkup cannot answer; neither keeps them once it has answered. When the assistant reads a web page, our servers fetch it from its site in a request that names Inqry, and the site sees nothing else of yours.
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. A request that goes to Anthropic leaves that network for Anthropic’s servers, and one that goes to OpenRouter for OpenRouter’s servers and its model host’s, each under that company’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 your device a sign-in token, the language and appearance you chose, the last link you opened, and the random identifier its update check uses. It asks for permission to send notifications once, the first time you open a link on the phone; you can turn them off in the operating system’s settings. It asks for the camera only when you choose to take a photo for a link’s library. It reads a photo or a file only when you pick one, through the system’s own picker, which needs no permission, and it makes a photo smaller before sending it. It uses the microphone only while voice mode is on, and the operating system asks your permission the first time you turn it on. It asks for no other permission, 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. This website, the web app 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.
If your account goes unused for a month and has never had a subscription, we delete it and everything in it, as if you had deleted it yourself. One that has had a subscription becomes dormant instead: nothing it does on a schedule runs, and using it again restores it as it was; if it is still unused twelve months after it was last used, we delete it the same way. An account with an active subscription, or on a team whose owner has one, is never made dormant or deleted for going unused.
An owner can delete their account at any time: on the web under Account in Settings, or in the app under Account. Everything we hold for them is erased from the service at once — every link, page, file, note, passage, conversation, contact, Help message, push token, usage count and the subscription’s state — and then the account itself, and a subscription bought on the web ends. It cannot be undone.
These records remain after an account is deleted:
- A purchase made in the app. We keep the store’s transaction id, the date and the id of the account it was bought for, so that a store sending the same receipt again cannot credit it to another account, and because the law requires payment records to be kept. The account it names no longer exists.
- Payment providers’ records. Stripe, Apple and Google keep their own records of a payment under their own legal obligations.
- Backups. Cloudflare keeps restorable copies of our databases for up to 30 days, so they can be restored after a failure; they then expire.
- Server logs. They are deleted automatically after a short time.
10. Your rights
An owner can read and delete everything above in the web app or the phone app, 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. We pass a visitor’s request about a conversation to the link’s owner, and act on it ourselves when the owner cannot be reached.
If you live in California or another U.S. state with a similar law, 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. You can also contact us first, but you do not have to.
11. Security
Every connection is encrypted in transit. Passwords are stored as hashes. A visitor can reopen their conversation only with the token their browser holds, and we keep only that token’s hash. Each account and each link is kept in its own isolated storage, which is erased when the account is deleted, apart from the records listed in section 9. 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 web app or the phone 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.