What is stored here, and what is not.

Your account and sign-in

Glove uses Google for sign-in and keeps your Google account ID and email address, not your name. These identify your Glove account and its usage and credit records.

Sign-in and approval cookies last 10 minutes. One-time sign-in codes last 60 seconds and are stored only as a one-way hash.

Your assistant’s access

When an assistant connects, Glove issues an access key. Glove stores only a one-way hash and a short prefix of that key. Keys do not expire unless revoked; they can be revoked. Glove does not issue refresh tokens.

Connected-app registrations that are never used are deleted after 24 hours; idle registrations are deleted after 90 days. This cleanup is separate from the retention of your account, lookups and packets.

Property lookups and results

Glove stores the addresses or parcels you look up, the request time, the result and the returned property packets in its database. These records support the lookup service and usage and credit records.

Your chosen AI assistant sends the lookup details and receives the result. Its provider handles your conversation under its own terms and privacy policy. Glove itself does not call an AI service at lookup time.

How long records are kept

The selected retention policy is 12 months for lookups and packets, followed by deletion. Credit and usage counts, without lookup addresses, are kept for accounting.

Implementation status, September 25, 2026: the service code does not yet automatically delete lookups and packets. Without a separate deletion process, those records remain indefinitely. The 12-month policy must not be read as confirmation that automatic deletion is already running.

Server logs rotate when they reach 10 MB, with three files kept; their retention depends on log volume rather than a fixed number of days. The sign-in service strips request details from its access log and records only the page path.

Daily database backups are stored on the same server and kept for 14 days. Deleting a record from the live database does not immediately remove it from an existing backup.

Who handles service data

• Vultr: hosts Glove on a server in Atlanta, United States, including its database and local backups.
• Cloudflare: provides DNS, proxies service traffic and hosts the public website on Cloudflare Pages. Public page visits are measured with Cloudflare Web Analytics, described below.
• Google: provides service sign-in. The public website separately loads fonts from Google, as described below.
• County and city government websites: receive the address or parcel details needed to retrieve the public record.

The Glove lookup service does not run analytics or error tracking, has no email provider or payment processor, and calls no AI service during a lookup. Public website visits are counted with Cloudflare Web Analytics. This does not describe the separate services used by your chosen AI assistant.

Access, deletion and revocation requests

For a copy of your account information, deletion of account or lookup data, or revocation of an access key, email chris@sterlingdp.com from the email address you use to sign in. Do not include a password or access key.

Disconnecting Glove in your assistant does not itself delete your Glove account or stored results. Accounting counts are kept separately from lookup addresses, and existing database backups are retained for 14 days.

Website hosting

The public site is served by Cloudflare Pages. Cloudflare handles each connection, including the visitor IP address, to deliver the page and protect the service. Cloudflare Web Analytics also measures public page visits and performance. Glove service requests, including property lookup addresses, pass through Cloudflare separately.

Website counters

The property-records guide and field-study pages send daily counts of page views and selected actions, such as worksheet copies, citation copies and downloads. Each stored total contains the day, action, mode, version and count. The counter database stores no visitor or session identifiers, IP addresses, property addresses or free text. If a browser sends DNT: 1 or Sec-GPC: 1, the endpoint returns 204 without adding a count.

Field-study notifications

If you submit a field-study notification form, the separate sign-up list stores your email address, the market you select, the company name if you provide one, and the time you submitted it. It stores no IP address, browser details, referrer or identifier. When a study for that market is published, Sterling Digital Partners sends one email; the website does not send it automatically. To request removal, email chris@sterlingdp.com. There is no automatic unsubscribe.

Website analytics, cookies and tracking

We do not run advertising or cross-site tracking. Public information pages set no cookies; this statement does not cover the separate sign-in service at auth.glvtl.com. Pages load Newsreader and Manrope from Google Fonts, which sends font requests to Google’s servers.

Public pages use Cloudflare Web Analytics. Its beacon sends a page-load ID, landing and referring page details, and browser performance measurements, including page timing and Core Web Vitals; where supported, it can also report JavaScript memory use. Cloudflare lists host and path, referrer, visitor country, device type, browser and operating system as available dimensions. Cloudflare says it does not log query strings. Cloudflare’s collection documentation and its RUM beacon data fields describe the measurements.

The beacon loads from static.cloudflareinsights.com and sends measurements to this site’s /cdn-cgi/rum endpoint. Cloudflare says Web Analytics does not collect or use visitors’ personal data, does not track individual users across customers’ sites, and does not use cookies or browser storage. Cloudflare receives the source IP address to handle the request, then says it discards the address at the nearest data center and does not store it in core databases or logs. This zone excludes analytics for visitors connecting through Cloudflare data centers in the EU. See Cloudflare’s RUM privacy details and the dimensions it reports.

The published records

The datasets on this site are public property records. They hold no personal data about visitors. Owner and taxpayer names are deliberately left out of the published work: no owner name, mailing address, grantor, grantee or legal description is read or reproduced.

Contact

Questions about any of this go to chris@sterlingdp.com.

Last updated 7 October 2026.