What SIPLX stores, what leaves your device, and how to remove it.
Last Updated: 15 September 2026
SIPLX is a text-expansion app. Snippets you write are saved on your device and work without an account. Two features send data off your device, and both are optional: AI formatting, which you trigger one snippet at a time, and cloud sync, which uploads your snippet library continuously once you sign in and turn it on.
If you do not sign in, nothing is uploaded by cloud sync. SIPLX is fully usable as a guest: your snippets, folders and triggers stay on your device and are never sent to us.
Expanding a trigger into full text in another app is not something an ordinary Android app can do. To type for you, SIPLX uses an Accessibility Service — a permission Android grants only when you turn it on yourself, in your phone's system settings. It is off until you do, and turning it off again stops expansion immediately and does nothing else to your data.
While it is on, the service receives events from the text field you are currently typing in: that the text changed, that a field gained focus, and that you moved to a different screen. To decide whether what you just typed is one of your triggers, it reads the text immediately before your cursor.
Nothing you type in other apps is stored, logged, or sent anywhere. The comparison happens on your device, in memory, against your own snippet list. Text that does not match a trigger is discarded as soon as the check finishes. We never receive it, and it is not written to the app's database, to a file, or to any server — including when cloud sync is on. Cloud sync uploads snippets you wrote in SIPLX, never text you typed elsewhere.
Open your phone's Settings → Accessibility → SIPLX and switch it off, or use the shortcut in SIPLX's own Settings screen. Expansion stops; your snippets, folders and account are untouched. You can also pause expansion temporarily from the SIPLX notification without revoking the permission.
Collected only if you create an account.
When you sign in and enable cloud sync, the following is uploaded:
Attachments are never uploaded. Images, PDFs and any other files you attach to a snippet stay on the device you added them to. They are not sent to our servers and do not appear on your other devices. If you reinstall the app or move to a new phone, attachments are not restored — use Export to keep your own copy.
So that a change you make on one device shows up on your others without you waiting for the app to check, each signed-in device is registered with us to receive a wake-up signal.
The signal carries no content. None of your snippet text, trigger phrases, folder names, email address or account name is in it. Google is told that a device should wake up; they are not told what changed, and there is nothing in the message for them to read. Nothing appears on your screen: the app wakes silently and then fetches the change from us over its own encrypted connection.
We store the token, which platform it belongs to, and when it was first registered and last updated. Registering the same installation again replaces the stored token rather than adding another. The token is deleted when you delete your account, and it is removed when Google tells us it has stopped working — which is what happens when the app is uninstalled or its data is cleared. Signing out stops this device sending or receiving anything, but does not by itself remove the token from our server.
Cloud sync data is stored in a PostgreSQL database hosted by Neon, in Amazon Web Services' Asia Pacific (Singapore) region. Data is encrypted in transit using HTTPS.
The server our apps and our website talk to runs on Render, in its Singapore region. Everything sent to us passes through it: your email address and password when you sign in, the token that renews your session afterwards, and your snippet data when cloud sync is on.
Neon and Render process this data on our behalf as hosting providers. Google processes device wake-up tokens on our behalf, as described in section 2. None of them is given your data for their own purposes, and we do not sell it to anyone.
When you tap the AI formatting button on a snippet, the text of that snippet is sent to our own server, which forwards it through OpenRouter — an AI gateway — to the language model that produces the formatted result. We choose that model on the server rather than in the app; today it is DeepSeek V3.2, and it may change. So the text of that one snippet is seen by OpenRouter and by the provider of the model in use. This happens only when you explicitly ask for it — never automatically, and never for snippets you have not chosen.
Only the snippet's text is sent. Attachments — images, PDFs and any other file you attach — are never sent to the AI.
Our server does not log or store the text you send, or the result that comes back from a successful call. When the AI provider answers with an error instead, the first 400 characters of its response are recorded in our diagnostic log so the failure can be traced. Beyond that it records only metadata about the call: its size, whether it succeeded, and the usage counted in section 5. Your account credentials are not sent to OpenRouter or to the provider of the model.
There are two ways to pay, and both attach to the same SIPLX account. Purchases made inside the Android app — Pro and Team subscriptions and Ink top-ups — are handled entirely by Google Play Billing. Purchases made on siplx.com by Windows users — Pro and Team subscriptions — are handled by Lemon Squeezy, LLC, the merchant of record for those sales. In both cases we never see or receive your card number, bank details or billing address. Google or Lemon Squeezy tells us only that a purchase happened, and our server then updates the Pro or Team entitlement on the account the purchase belongs to.
To make a subscription or an Ink top-up work, our server stores:
| The purchase token Google issues | So we can ask Google whether the purchase is genuine and still valid, and so a refund can be applied |
|---|---|
| The subscription and customer identifiers Lemon Squeezy issues | For a website purchase: so we can ask Lemon Squeezy whether the subscription is still active, and so you can open its customer portal from the app or the site |
| Which SIPLX account a website purchase belongs to | Your account identifier is passed to Lemon Squeezy at checkout and comes back with its notifications, so the subscription lands on the account you were signed in to |
| Which product and plan you bought | Pro or Team, monthly or yearly, and the number of seats for a team |
| When it expires | To know whether your subscription is active |
| Your Ink balance | Ink is the credit that pays for AI use |
| A line per Ink movement | The amount added or spent, the balance afterwards, the reason, and — for AI use — how many tokens the request and the reply came to, and which model answered |
| How many free AI uses you have had this week | A count only, reset every Monday |
The Ink record counts your AI usage; it does not keep what you sent. The text of a snippet is not written to that record — see AI formatting above.
When you delete your account, the identifying details on it — your email address, your name, your password — are removed immediately. The purchase and Ink records above go with the account when the record itself is removed, thirty days later. They contain no snippet text at any point.
Google keeps its own record of an Android purchase under Google's privacy policy, and refunds for it are requested through Google Play rather than through us. Lemon Squeezy keeps its own record of a website purchase — including the email address, name, billing address and payment method it collects to take payment, issue invoices and handle tax — under Lemon Squeezy's privacy policy; refunds and cancellations for it go through the Lemon Squeezy customer portal or by email to us. Lemon Squeezy sends our server notifications about a subscription (created, paid, cancelled, expired, refunded); we act only on notifications whose signature we have verified, and a repeated notification is not applied twice.
If you join or create a team, content you place in that team's workspace is shared with the other members of that team.
@; if you signed in with Google, it is the name on
your Google profile. You can change your display name to anything you are
comfortable sharing.
When you expand a snippet inside a team workspace, that expansion is recorded and uploaded to the team: the trigger phrase you typed, when you typed it, and how many characters it saved, attributed to your account.
Delete a snippet in the app and it is removed from your device and, if cloud sync is on, from your cloud library on the next sync.
Open Settings → Profile → Delete account in the app. You will be asked to confirm who you are first — with your password if you registered with an email address, or by signing in with Google again if your account uses Google. This works for both kinds of account.
You can also delete your account from the web, without installing the app: siplx.github.io/siplx-privacy/delete-account/.
When you delete your account:
| Your personal snippets, triggers and folders in the cloud | Deleted |
|---|---|
| All active sign-in sessions | Revoked immediately |
| Your email address, display name and password | Removed from your account record |
| Snippets on your device | Stay on your device — deleting your account does not erase your phone |
| Team content you chose to leave with the team | Kept for the team, with your identity removed from it |
When you delete your account you are asked whether to also delete the snippets you contributed to teams. If you choose to leave them, they remain available to those teams and are no longer associated with you.
After deletion, a de-identified record of the account remains for 30 days — without your email address, display name or password — so that the account cannot be signed into or re-registered in the meantime. After 30 days that record is removed as well, along with the purchase and Ink records described above.
The sections above are about the SIPLX apps. The website is a separate thing and a much smaller one: it describes the product, and it lets you sign in to the account you already have. Your snippets are never on it.
The site sets no cookies, so there is no cookie banner to dismiss. Three values are kept in your browser's own storage:
siplx_refresh_token |
Kept while you are signed in, so that reloading the page does not sign you out. It is sent to our server to renew your session, and it is removed when you sign out. It has no expiry of its own — signing out is what clears it. |
|---|---|
siplx_user_cache |
The account details our server returns when you sign in — your email address and display name among them — so the page can show who is signed in without asking again. Cleared when you sign out, and when you close the tab. |
siplx-lang |
The interface language you picked. It is not tied to your account, and it stays until you clear your browser data. We do not send it to our own server, but it is passed to Google as the language for the sign-in button, at the moment you open the sign-in dialog. |
Creating an account sends your email address, your password and your display name to our server; signing in sends your email address and password. If you are already signed in, opening the site quietly asks our server to renew your session, and asks it whether your subscription is still active — nothing else is sent. Choosing Continue with Google loads Google's sign-in code, and only at the moment you open the sign-in dialog, not on an ordinary visit; Google sees that request. We receive an identifier for your Google account, never your Google password.
The main site loads its typefaces from Google Fonts as the page opens, so your IP address and basic browser details reach Google — before you sign in, and whether or not you ever do. This policy page and the refund page carry no such request: they use whatever fonts your device already has, and load nothing from Google. Google explains what it does with that in its own privacy policy.
SIPLX is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has given us personal information, contact us and we will remove it.
If we change what SIPLX collects or how it is used, we will update this page and change the "Last Updated" date at the top. Material changes to how we handle data that has already been collected will be announced in the app.
Questions about this policy, or requests about your data, can be sent to siplx.app@gmail.com.