Privacy Policy
Reloquent — reloquent.ai and the RLQ API
Effective date: 2026-09-23 Last updated: 2026-10-02
This policy explains what personal data Adelaide Endeavors LLC, an Arizona
limited liability company doing business as “Reloquent,” collects and how we
handle it across the reloquent.ai website, the customer dashboard, the website
demos, and our spatial enrichment API, RLQ. For personal data about other
people that you send through the API, see
“Enrichment content” below and our Data Processing Agreement, available on
request.
We are the controller of the personal data described here. Contact: privacy@reloquent.ai.
What we collect and why
Account and identity data. When you sign up, our identity provider (Clerk) collects your email address and authentication credentials and assigns a user ID. In our own systems we store that user ID, your email, your plan and subscription status, and the timestamps of account events. We use this to create and operate your account, authenticate you, and contact you about the service, including the subscription notices the law requires (for example, confirmations and renewal reminders).
Billing data. Payments are processed by Stripe (via Clerk Billing). We do not receive or store your full card number. Stripe holds your payment method and billing details; we store only a Stripe customer reference and your subscription status, which we use to manage your plan.
Checkout consent records. Before you subscribe to a paid plan, you agree to its automatic renewal terms by ticking a box. We record that agreement: your user ID, the exact terms shown, the billing period, the time, and your IP address and browser user agent. We keep the record as proof of your consent, which subscription laws require us to be able to show.
API key data. When you create an API key we store a non-reversible hash of it, plus a short prefix and the last four characters so you can recognize it. The full key is shown to you once and not kept in readable form.
API usage and request metadata. When you call the API we process operational metadata — which key made the request, when, which endpoint, request counts, and network information such as IP address — to authenticate requests, enforce allowances and rate limits, prevent abuse, debug, and bill correctly. Our infrastructure providers (Cloudflare, DigitalOcean) also log standard request metadata as part of delivering and securing the service.
Enrichment content (RLQ input and results). The coordinates you send to RLQ and the results we return are handled only to perform enrichment. This content is usually not personal data, but it can be: coordinates can reveal where a person has been, and some results include third-party business contact details (for example, a place’s phone number or address from OpenStreetMap or Overture). We delete your input when the job that processes it finishes. Result files are available for 48 hours and then deleted. Job records, which hold metadata and never your geometry, are deleted after 30 days. We do not use enrichment content to build our own datasets or to train models. If you submit personal data of others through the API, you are the controller of that data and we act as your processor under the Data Processing Agreement.
Website demos. The demos on reloquent.ai run through the same API on our
own internal keys, which never reach your browser. The demo maps load their
base map from our own servers, which receive the standard request metadata
described above. The enrichment demo follows
the retention above: its input is deleted when the job finishes, its result file
(with the geometry you drew removed) within 48 hours, and its job record after
30 days. We do not log the coordinates you use in the road-lookup demo. To
prevent abuse we apply a
per-IP rate limit and a daily cap, which means we briefly process your IP
address.
Cookies and similar technologies. We use only cookies needed to run the service: our identity provider’s cookies keep you signed in, Cloudflare may set security cookies and run a bot check (Turnstile) when you sign up, and Stripe sets cookies in the checkout to prevent fraud. We do not use advertising cookies, and we do not run third-party analytics or ad tracking. Cloudflare’s bot check and Stripe’s checkout (whose address field may use Google’s address autocomplete) collect information about your device and activity to protect against fraud and abuse, under their own privacy policies; we do not let any third party track you across websites for advertising. Because we do not track visitors across other websites, we do not respond differently to browser “Do Not Track” signals.
What we do not do
We do not sell your personal data or your enrichment content, and we do not share it for advertising. We do not use your API input or results to profile you or to build marketing audiences.
Legal bases (EEA and UK users)
Where the EU or UK GDPR applies, we process account, billing, key, and usage data to perform our contract with you; request and security metadata for our legitimate interests in securing the service and preventing abuse; and billing records to meet our legal obligations, such as tax and accounting.
Subprocessors
| Provider | Role | Data it handles | Location |
|---|---|---|---|
| Clerk | Identity, authentication, billing orchestration | Email, credentials, user ID, plan and subscription state | United States |
| Stripe | Payment processing and fraud prevention | Payment method, billing address, invoices, customer reference | United States |
| Cloudflare | Hosting, network, file storage, bot protection, email delivery | Request metadata (including IP), RLQ input files while a job runs, result files for 48 hours, demo rate-limit counters, the email address and content of the account and billing emails we send you | Global network; files stored in North America |
| DigitalOcean | Compute and database | Account records, usage and quota data, job records, request processing | United States (San Francisco) |
We will keep this list current and give notice of material changes as described in the Data Processing Agreement.
Where your data is stored
Our database server runs in DigitalOcean’s San Francisco region, and our files are stored in Cloudflare R2 in North America. Cloudflare processes requests at network locations worldwide on the way to our servers.
Retention
- RLQ input: deleted when its job finishes.
- RLQ result files: deleted 48 hours after the job finishes.
- Job records (metadata only, never geometry): deleted after 30 days.
- Account and billing records: kept while your account is active and afterward only as needed for legal, tax, and accounting obligations.
- Checkout consent records: kept for three years, or until one year after your subscription ends if that is later.
- Operational logs and usage metrics: kept for a limited period for security, debugging, and billing, then deleted or aggregated.
- Backups: if our hosting provider keeps backups of our database server, deleted records can remain in those backups until they expire.
How we share data
We share personal data only with the subprocessors above, when required by law or valid legal process, to protect our rights, users, or the public, and in connection with a merger, acquisition, or sale of assets (with notice as required). We do not otherwise disclose it.
International users and transfers
We operate the service from the United States. If you use it from outside the U.S., including the EEA or UK, your data is transferred to and processed in the U.S. For those transfers we rely on appropriate safeguards, such as our providers’ participation in the EU–U.S. Data Privacy Framework and Standard Contractual Clauses.
Your rights
Depending on where you live, you may have rights to access, correct, delete, or port your personal data, to object to or restrict certain processing, and to withdraw consent. You can delete your account at any time from the account portal; we then deactivate your API keys and delete your account data, except records we must keep by law. Because we do not sell or share personal data for advertising, there is no opt-out of sale to provide. To exercise a right, email privacy@reloquent.ai; we will verify your request and respond within the time the law requires. You may also lodge a complaint with your local data protection authority.
Security
We protect data with measures appropriate to its sensitivity, including encryption in transit (TLS), storage of API keys as non-reversible hashes, signed and authenticated internal service-to-service calls, and secrets held in a managed keychain rather than in code. No system is perfectly secure; we will notify affected users and authorities of a breach as required by law.
Children
The service is for business and professional use and is not directed to children. We do not knowingly collect personal data from anyone under 16. If you believe a child has provided us data, contact us and we will delete it.
Changes
We may update this policy; we will revise the “Last updated” date and, for material changes affecting customers, provide reasonable notice.
Contact
Adelaide Endeavors LLC d/b/a Reloquent 4539 N 22nd St, Ste N Phoenix, AZ 85016 Privacy: privacy@reloquent.ai