Legal
Privacy Policy.
For RLSAND Inc. and the RLSAND JSON Editor app.
RLSAND Inc. ("we", "us") respects your privacy. This policy describes the limited information we collect, how we use it, and how to contact us.
What we collect
RLSAND JSON Editor app
The short version: nothing. The app collects no analytics, no telemetry, no crash reports, and contains no third-party analytics, advertising or tracking SDKs. We have no account system and no server that ever receives your data.
Your documents are files on your device, opened in place through Apple's document system. They are never transmitted to us. API keys, tokens, and other credentials you save in the app are stored only in the device Keychain — never in exports, logs, or sync records.
Apart from optional iCloud sync (below), the app connects to the network only when you ask it to:
- Fetch from URL retrieves a document from a URL you enter.
- API Projects sends requests to the endpoints you configure, with the credentials you supply.
- Importing or refreshing an API Project from an address fetches that address and, for a documentation page, up to 8 addresses linked from it, to find the API description.
- AI help sends a request you start to Apple's Private Cloud Compute or to the AI provider whose key you added, as described in Optional AI Help below. If you tap Fetch for a documentation address in suggested sign-in settings, the app downloads that page. Requests handled on your device by Apple Intelligence don't use the network.
iCloud sync is optional and off by default. If you enable it, API Project structure syncs through your private CloudKit database, saved credentials through iCloud Keychain, and recent files / snippets through iCloud key-value storage — all inside your own iCloud account, managed by Apple, not by us.
Optional AI Help
RLSAND JSON Editor includes optional AI help: plain-English questions about your JSON (Ask Your JSON), plain-English edits (AI Assist), descriptions of your data, AI repair of invalid JSON, missing-key suggestions, plain-English queries and table filters, explanations of errors, comparisons, scan results, contract checks and failed API requests, and generated code, sample data and field descriptions. The rest of the app works without AI, and you can turn AI off in Settings (Disable AI).
Where AI requests are processed. In Settings you choose how AI help answers: with Apple Intelligence, or with your own AI provider key. Every AI screen tells you where a request will go before anything leaves your device. A few on-device actions start right away; nothing is sent to Apple's private cloud or to your AI provider until you tap.
- Apple Intelligence — used when your device supports it and you haven't added a key, or when you switch back to it in Settings. The app tries these in order:
- On your device — on eligible iPhone, iPad and Mac models running iOS, iPadOS or macOS 26 or later. The request does not leave your device.
- Apple Private Cloud Compute — on iOS, iPadOS and macOS 27 or later, when a request is too large for your device or the on-device model isn't available, it can go to Apple's Private Cloud Compute servers. The Apple Private Cloud setting in Settings decides how: Ask First (the default) shows a message before a request goes there — in Ask Your JSON, once per conversation — and nothing is sent until you choose (Always Use Private Cloud there switches the setting to Always; Cancel sends nothing); Always sends without asking; Never keeps requests off Apple's private cloud. Apple processes these requests under its Private Cloud Compute privacy commitments; RLSAND Inc. does not receive their content. Apple applies a daily usage limit to each iCloud account, and the app shows when you are near it or have reached it.
- Your saved key, as a last resort — if you have also saved a key and neither Apple option can handle a request (for example, after today's limit is reached, or when Apple Private Cloud is set to Never), that request goes to your AI provider as described below.
- Your own AI provider key — if you add an API key for Anthropic, OpenAI, Google Gemini or xAI Grok, the app switches to that key, and AI requests go directly from your device to that provider (api.anthropic.com, api.openai.com, generativelanguage.googleapis.com or api.x.ai) with the relevant JSON and your instruction. Private Cloud Compute is not used in this mode, and on-device AI is used only for Private documents. The provider processes the request under its own privacy policy and may bill your account. The app keeps one key at a time, stored only in this device's Keychain and never synced. Ask Your JSON labels each answer with where it was answered.
Private documents. If you mark a document Private (“Private — AI stays on this device”), its AI help runs only on your device. It is never sent to Apple's Private Cloud Compute or to any AI provider, whichever way you chose above.
Failed API requests. “Why Did This Fail?” sends a short report built from the saved response: the request method, the address without its query string or any user name and password, the status, up to 30 response headers, and about 4,000 bytes of the response body, with passwords, tokens and keys masked. Your request headers and request body are not sent. The “What will be sent” section shows the exact text before you send it.
Suggested sign-in settings. When you ask AI to suggest an API Project's sign-in (auth) settings, which uses your own key only, the app sends your provider the project's name, its base URL, its variable names, up to 40 request names, methods and URLs, and any notes you type. If you enter a documentation address it is sent too, and if you tap Fetch, the app downloads that page and includes its text.
What RLSAND Inc. receives. Nothing. RLSAND Inc. operates no AI proxy or server and does not receive, store or log the content of any AI request. AI suggestions are previews; nothing changes in your document until you choose to apply it. (Asking in plain English for a query or a table filter changes only what you see, not your document.)
Website & support
If you submit the support form or contact form on this site, we receive the information you provide (name, email, the issue you described, optional device and version metadata). We use this only to respond to your request and may retain it in our support email archive.
Standard server logs (IP address, user agent, requested URL) are kept for short periods to support security and debugging.
How we use it
- To respond to your questions and support requests.
- To keep our website running and secure.
How we share it
We do not sell, rent, or share your information with third parties for their own purposes. The only companies that ever handle it are the providers that operate this website on our behalf — our email-delivery service (which transmits your form message to us) and our hosting provider — strictly to run the service, and only the minimum required. We disclose information only if required by law.
Retention
Your documents stay on your device (and, if you enable sync, in your own iCloud account) until you delete them. Support correspondence: kept while it's useful for ongoing support. Server logs: short-lived. You can ask us to delete your support correspondence at any time.
Your rights
Depending on where you live, you may have rights to access, correct, or delete information we hold about you. Because your documents and credentials live on your own device, you control them directly. For anything we hold (support correspondence), reach us through our contact form and we'll respond.
Children
RLSAND JSON Editor is a developer tool intended for adults and is not directed to children. We do not knowingly collect information from children under 13.
Changes
We'll update this page when our practices change. Material changes will be highlighted at the top.
Contact
Questions about this policy: use our contact form.