B1. Who we are and what this covers
This Privacy Policy explains how The Foundery Group, LLC, a South Carolina limited liability company that operates LimitLine ("LimitLine," "we," "us"), collects, uses, shares and protects personal information when you use the LimitLine website at limitline.app, the LimitLine iPhone app, including its CarPlay and Apple Watch features where available, and the LimitLine Android app (the "Service"). The website and the apps are one service with the same account and the same content. Some sign-in options and features differ between them; where that matters, this Policy says so.
Questions and privacy requests: support@limitline.app, or by mail to The Foundery Group, LLC, attention Privacy Requests, 2267 Blakers Blvd, Bluffton, SC 29909.
Summary. We collect what we need to run LimitLine: your account details, what you create, location you choose to share, and billing status. Stripe handles your card. We do not sell your personal information, we do not use it for targeted advertising, and we do not use advertising or analytics trackers. Parcel cards show parcel boundaries and, on eligible plans, the owner names and addresses published in public parcel records; we display those details without storing them, and anyone can ask us to hide a record (section B7). Parcel cards do not show property values. If you use the LimitLine Assistant (paid plans and free trials started with a payment card) and give your permission, what you type to it and some information from the screen you are on or from your workspace are sent to our AI provider, OpenAI, to produce answers, and we save your conversations for you until you delete them (section B6). You can ask to see, correct, download or delete your information, and you can opt out without an account.
B2. Information we collect
Information you give us
• Account information: email address, name or display name if you provide it, password (stored by our authentication provider in hashed form), your 18+ confirmation, and your acceptance of legal documents. We do not collect your birth date or identity documents.
• Sign-in with Google or Apple: if you choose Google sign-in, Google shares your name, email address, profile picture and a Google account identifier with us. If you choose Apple sign-in in the iPhone app, Apple shares an Apple identifier, and your name and email address (or an Apple relay email address if you choose to hide yours). We ask only for basic profile and email information. We do not receive your Google or Apple password, and we do not access your Gmail, contacts, calendar, Drive or other Google or Apple data.
• Workspace content: properties, boundaries, waypoints, pins, routes, plans, tasks, notes, journal entries, harvest and Shot & Recovery records, pressure records, photos, gear lists and other content you create, and workspace membership and roles.
• LimitLine Assistant: the messages you send the assistant, the answers it gives you, and planning goals you enter when you ask for task suggestions (section B6).
• People you add: names, email addresses or other contact details of people you invite to a workspace or choose as Field Check-in contacts or guardians, and landowner names you type into your own outreach notes. Only add people when you have a right to share their details.
• Location you choose to share: see section B5.
• Support and requests: messages you send us, and information needed to verify and answer a privacy request.
• Billing information: your plan, trial and subscription status, and billing history. Your card number is entered directly with Stripe, not with LimitLine. Stripe may share with us the card brand, last four digits, expiration date, billing country and postal code, and a Stripe customer identifier.
Information collected automatically
• Device and log information: IP address, browser and device type, operating system, app version, pages and features requested, timestamps, and error and security events. Our hosting providers keep server logs.
• Push notifications: the iPhone and Android apps include the software needed to receive push notifications (in the Android app, Google's Firebase Cloud Messaging; in the iPhone app, Apple's push notification service). LimitLine push notifications are not turned on. Until we turn them on, the apps do not ask for permission to show push notifications or request a push notification token, and we do not collect one. Before we turn them on, we will update this Policy.
• Bot checks: when you sign up, sign in or reset a password, Cloudflare Turnstile checks that the request comes from a person. Turnstile processes your IP address and browser and device signals and gives us a pass or fail result. Cloudflare processes this information on our behalf to protect LimitLine, and also uses it for its own separate purpose of improving its bot detection (section B10).
• Cookies and device storage: we use cookies and browser or app storage that are needed to keep you signed in, protect your account, remember settings such as your chosen basemap, and keep drafts and offline data on your device (section B8). We do not use advertising cookies, analytics cookies, tracking pixels, or third-party advertising or analytics software. Stripe's checkout and billing pages, which are hosted by Stripe, may use Stripe's own cookies for fraud prevention.
Information from other sources
• Public parcel records from official county and state sources and, where its license permits, a licensed parcel-data provider: parcel boundaries and, on eligible plans, the owner names and addresses published in those records, which we display without storing, whichever source provides them (section B7).
• Map, weather, address and land-cover data returned by the public and commercial services listed in section B10.
• Stripe (payment status and fraud signals), Google and Apple (sign-in details above), Apple TestFlight (if you test the iPhone app: tester name and email if invited by email, build, device model, crash reports and feedback you choose to send), and Google Play (if you get the Android app from Google Play: the crash and performance reports Google provides to app developers and, if you test the app, your tester email address and feedback you choose to send).
B3. How we use information
We use personal information to:
• create and secure your account and confirm you are 18 or older;
• provide the features you use, including maps, parcel cards, analysis, Field Check-ins, shared workspaces and, on paid plans and free trials started with a payment card, the LimitLine Assistant (section B6);
• show eligible users the owner names and addresses published in public parcel records, to help them identify who owns land, for example to ask permission to enter or hunt (section B7);
• process your free trial, subscription, renewals, reminders, cancellations and refunds through Stripe;
• send account, security, billing, reminder and legal emails (and marketing emails only if you agree);
• prevent fraud, bots, trial abuse and misuse, enforce our Terms and Acceptable Use Policy, and investigate incidents;
• answer support and privacy requests, including requests to hide owner details on parcel cards and legally required protected-address notices;
• diagnose problems and improve the Service using our own server records (not third-party analytics); and
• meet legal, tax and accounting duties and protect rights and safety.
We do not use personal information to make decisions that produce legal or similarly significant effects about you (such as credit, housing or employment decisions), and we do not build advertising profiles.
B4. Sensitive information
Some information LimitLine handles is treated as "sensitive" under certain state laws, including precise geolocation and account sign-in credentials. We use precise location only to provide features you request and with your device permission (section B5). We do not use sensitive information to infer characteristics about you, and we do not sell or share it for advertising. Where a state law requires your consent to process sensitive information, we ask for it before collecting precise location. You can withdraw consent at any time by turning off location permission in your device settings.
B5. Location information
Location access is always permission-based and you can turn it off in your device or browser settings. Without it, features that need your current location will not work, but you can still use the map.
• Website and app map: with permission, we use your device location to show where you are, center the map and support features you start. Map tile requests can reveal the area you are viewing.
• Android app: the Android app asks only for permission to use your location while you use the app (on current Android versions, "while using the app") and does not ask for background location permission. On Android 10 and later, an app without that permission cannot get your location in the background. The Android app has no car or watch features.
• Field Check-ins and party locations: these store discrete location captures when you check in or share, not continuous tracking. A contact must accept the relationship before location is shared with them.
• CarPlay (where available): with permission, the iPhone app uses background location only while a CarPlay map, Dashboard or road-guidance session you started is active, to follow your position and give directions, and stops when those sessions end, location permission is revoked, you sign out, or CarPlay disconnects. CarPlay uses Apple MapKit for map display, search and directions, so Apple receives the viewed area, search text and route requests.
• Apple Watch (where available): if you pair the Apple Watch app, the iPhone app shares a limited snapshot of your current workspace with the Watch. Actions you take on the Watch, such as Field Check-in steps, shot marks and dictated notes, are passed to the iPhone app, which sends them to LimitLine. With your permission, the Watch captures one location only when you ask for a field action or a backtrack bearing; it does not follow you in the background. Notes you dictate on the Watch are converted to text by Apple's dictation service and sent to the iPhone app. The Watch app may also ask permission to show local reminders, for example when a recovery timer you set ends; these reminders are scheduled on the Watch and are not sent to LimitLine.
• Saved places: pins, waypoints, properties and routes you save are stored in your workspace and can reveal places you go.
• Directions: if you tap Navigate on a pin, a property, a parcel card or a Scout lead, LimitLine opens Apple Maps (in the iPhone app) or Google Maps (in the Android app and on the website) with that one point so you can get directions. LimitLine makes no request of its own for this and keeps no record of the tap. The maps provider receives the point, and its own privacy policy applies to what you do there.
Stale, offline or missing location never proves where a person is or whether they are safe.
B6. AI features
What it is. The LimitLine Assistant is an AI chat assistant in the signed-in website, the iPhone app and the Android app. It answers questions about hunting, your field notes and other LimitLine records, and how to use LimitLine, and it declines other topics. It can also suggest draft tasks, which are saved only if you add them. It is available to the owner and members (not guests) of a workspace on a paid plan or a free trial started with a payment card, within the usage limits in the Terms (section A5). It is not part of Founders Beta access. You never have to use it; every other feature works without it.
Our AI provider. We use OpenAI's API for businesses to produce the assistant's answers. Our server sends OpenAI only what is listed below, and only when you send the assistant a message or ask it for task suggestions.
Your permission. Nothing is sent to OpenAI until you allow it. The first time the assistant or task suggestions would send a request to OpenAI for your account on this device, LimitLine asks for your permission; one choice covers both. If you choose Not now, nothing is sent, and every other feature keeps working. You can turn it off at any time in the assistant's Saved conversations or in More, Privacy & data (/app/data); LimitLine then asks again before your next request. Signing out also turns it off on this device, so LimitLine asks again after you sign in. Turning it off does not recall what was already sent and does not remove your saved conversations; you can delete them as described below.
What we send to OpenAI when you chat:
• your new message and the earlier messages of the same conversation, up to the last 20 messages (yours and the assistant's); and
• information about the screen you are on: its name; the species, pursuit target and hunt style you selected and which pursuit-planner checks are still open; the selected property's name, acreage, county and state; the time of day you are planning for; the weather and solunar rating shown; the status of the property analysis, how many bedding, food and water areas it found, and up to 6 suggested travel routes and 6 suggested stand spots with LimitLine's reasons for them; and how many saved map markers of each type are on the map.
What we send to OpenAI when you ask for task suggestions:
• the planning goal you type, the kind of tasks and the month you chose, today's date, and the pursuit target and hunt style you selected;
• the selected property's name, acreage and state, and the selected project's title, type, status and dates; and
• the names and types of up to 60 stand, food plot and camera markers on that property, and the titles and due dates of up to 50 open tasks in the workspace (only those on the selected property or project, if you chose one). These can include markers and tasks other members of your workspace added.
With every request we also send a one-way code made from your account ID, which lets OpenAI detect abuse of its service without learning who you are.
What we do not send. We do not send OpenAI your name, email address, account or payment details, photos, parcel owner details, or map coordinates: not your location, the map position or where your markers are. The app sends the map position and marker locations to our own server with a chat message; our server uses them only to make the one-way request fingerprint described below and does not pass them on. But text you type is sent as you typed it, including your messages and the names you gave properties, projects, markers and tasks. If you type a name, phone number, address, health information or other personal details into them, that text goes to OpenAI. Do not include personal information about yourself or anyone else that your question does not need, and do not include information about children. LimitLine, including the assistant, is only for adults 18 and older (section B12).
How OpenAI handles it. OpenAI processes these requests on our behalf under its business terms. We tell OpenAI not to store the assistant's answers for later retrieval. Under OpenAI's published business terms, OpenAI does not use information sent through its business API to train or improve its models unless the customer agrees, and we have not agreed. OpenAI keeps requests and answers in abuse-monitoring logs for up to 30 days, or longer where the law requires, and then deletes them. Access to them is limited to authorized OpenAI staff and contractors who need it to investigate abuse and misuse, give engineering support or meet legal duties. If OpenAI's safety systems flag requests, OpenAI may block further requests linked to the same one-way code, and the assistant may then stop working for your account.
What LimitLine keeps.
• Your conversations. When the assistant answers, we normally save your message and its answer in your conversation (up to 200 messages in a conversation and 500 conversations for your account), with a title made from your first message, the times, the workspace and which AI model answered. We do not save the screen information sent with it. Task suggestions are not saved unless you add them as tasks. Other people in your workspace, including its owner, cannot see your saved conversations. We access them only to provide and secure the Service, answer your requests, investigate abuse or meet legal duties. You can reopen and continue them from the assistant panel.
• Usage and cost records. To enforce usage limits and our spending limit, we record how many assistant messages each person and workspace uses and, for each request, your account, the time, workspace, feature used, a one-way fingerprint of the request, the amount of text processed (tokens) and the cost. These records contain no message text.
Your choices. You can delete one saved conversation or all of them at any time in the assistant panel, and all of them on the Privacy & data page (/app/data). Your account data export includes your saved conversations. Deleting your account deletes them. Section B9 says how long we keep each kind of record.
We do not use your conversations to train AI models. Assistant answers can be wrong; they are guidance, not legal, safety, medical or other professional advice (Terms, section A3, and the Safety Notice).
B7. Parcel and public-record information
Parcel boundaries come from official county and state parcel services and similar public sources. The source for a location is named on the map and on the parcel card. When you tap a parcel or view parcel lines, our server sends the tapped point or the visible map area to that source. We do not include your name, email or account identifier in those requests.
Owner details from public records. A parcel card can show the owner of record (one or more names), the property (situs) address and the owner's mailing address that public parcel records publish. We get these details from official county and state sources and, where its license permits, a licensed parcel-data provider such as Regrid (operated by Loveland Technologies), which compiles public parcel records. We use a source for owner details only after we have reviewed its terms or license and approved it for this use. We do not get this information from you or from the people it describes. Parcel cards do not show property values. If we start getting owner details from another kind of source or start showing values, we will update this Policy first.
Who sees owner details. Only signed-in users who are the owner or a member (not a guest) of an active workspace that has parcel access and a free trial started with a payment card, an active paid subscription, or Founders Beta access. They are never shown on public pages, in marketing, to workspace guests or to signed-out visitors, and not to accounts whose trial or subscription has ended. Each account has a limit on how many owner lookups it can make in a period.
Why we show them. To help users identify the owner of record of land they are looking at, for example to ask permission to enter or hunt.
How they are shown. Exactly as the source publishes them at the moment you tap. We remove extra spaces at the ends and do not correct or complete values; we may join a record's separate name or address parts into one line. If the source leaves a value blank, uses a placeholder, or marks the record confidential or protected, the card says "Withheld by publisher", and we never fill it in from another field, record, source or provider. Where several assessor records share one parcel shape, the card shows one record and says how many others are not shown. Owner details may be outdated or wrong. They are not a title search, proof of ownership, or permission to enter land.
We do not store owner details, whichever source provides them. When you tap a parcel, our server asks the source for the owner fields along with the boundary and passes them to your device for the parcel card. LimitLine does not save them in your records or our database, does not keep them in the app's offline storage or caches, and does not add them to exports, saved properties, CarPlay or property analysis. Responses that contain them are marked so that browsers and the app do not cache them. If you type an owner name into your own outreach notes, it is saved like other content you create.
Ask us to hide a record. Anyone, including a property owner or someone acting for them, can ask us to hide the owner details on a parcel card. Email support@limitline.app with "Hide owner record" in the subject, or write to the address in section B1. Tell us which parcel: the source and parcel ID shown on the card, the property address, or the county and a map location. You do not need a LimitLine account, and we ask only for what we need to find the right parcel. We honor these requests and will confirm by email, normally within 10 business days. Because LimitLine does not store owner information or search it by name, we cannot find every parcel connected to a person, so please list each parcel you want hidden. We may decline a request that is clearly abusive, or that asks us to hide owner details in bulk rather than for particular parcels (for example, every parcel in a county), and if we do, we will tell you why. This does not apply to legally required protected-address notices, which we always handle as described below. A hidden parcel still shows its boundary; its owner name and addresses read "Not available". Hiding a record in LimitLine does not change the public source's records; to change those, contact the county or state office that publishes them.
Legally required protected-address notices. Some laws give certain people a right to make a business stop disclosing their home address or related information, even when a public record still shows it. For example, in New Jersey, a covered person (such as an eligible judge, law-enforcement officer or family member) or their authorized representative may send a written notice under N.J.S.A. 56:8-166.1, and a business that receives a qualifying notice must stop disclosing the covered information within 10 business days. When we receive a notice that meets the requirements of an applicable law, this is not discretionary: we will stop showing the covered information in LimitLine, including any owner name that would connect the person to that address, within the period the law requires. If we cannot reliably find every place the covered information could appear, we may turn off owner details for a whole source while we act. We may check that the notice meets the law's requirements, but we will not delay beyond the legal deadline to do so. Send these notices to support@limitline.app with "Protected address notice" in the subject, or by mail to the address in section B1. Other requests are handled under "Ask us to hide a record" above.
If your information appears in a public record. If you are not a LimitLine user and your name or address appears on a parcel card, we do not keep that information, so we usually have nothing to give you in response to an access, correction or deletion request beyond any message you sent us. You can ask us to hide the record as described above. To correct the record itself, contact the office that publishes it.
Not a consumer report. LimitLine is not a consumer reporting agency, and owner details and other parcel information are not consumer reports. They may not be used as a factor in deciding anyone's eligibility for credit, insurance, employment, housing, a government license or benefit, or any other purpose covered by the Fair Credit Reporting Act.
B8. Information stored on your device
Some information stays in your browser or the app on your device: unsaved planner drafts, your last property analysis, your remembered map address and basemap, and Apple Watch notes that have not reached LimitLine yet. Drafts are tied to the account that wrote them and stay on the device after sign-out so they are not lost; another account signing in on the same device does not see them. Older drafts created before drafts were tied to accounts can be seen or deleted by any signed-in user of that device. The app may also keep the Esri land-cover images used in property analysis in its offline map cache. Cached pages, viewed map tiles and those cached images are removed when you sign out. To remove what is kept for your account, use Clear offline data on the Privacy & data page (/app/data); Download this device's drafts saves a copy first. Removing the app or clearing site data also removes it. Drafts can contain access notes, names and locations, so protect access to your device.
B9. Retention and deletion
How long we keep information.
• Account and workspace content: While your account is active, then deleted within 30 days of a verified deletion request, except as described below
• Content you contributed to a shared workspace: Stays available to the workspace under its roles after you leave; on account deletion it is deleted or de-identified unless the workspace owner needs it and the law allows us to keep it
• LimitLine Assistant conversations: Until you delete them or your account. We do not delete them automatically. If a workspace is deleted, the conversations saved in it are deleted with it
• LimitLine Assistant usage counts and cost records (no message text): While your account exists; we may delete older records sooner. On account deletion, we delete them or remove your account identifier from them
• Assistant requests and answers at OpenAI: Up to 30 days in OpenAI's abuse-monitoring logs, or longer where the law requires (section B6)
• Billing, tax and transaction records: As long as tax and accounting law requires, generally up to 7 years
• Records of your acceptance of these documents, 18+ confirmation and subscription consent: For the life of the account and at least 3 years after it ends, to prove consent
• Security, fraud and abuse records: Up to 2 years, or longer if needed for an open investigation or legal hold
• Server logs at our hosting providers: According to provider settings, generally 30 days or less
• Backups: Deleted data leaves backups within 90 days
• Parcel owner details: Not stored, whichever source provides them. Shown on the parcel card only; not saved to your records, our database or offline storage
• Requests to hide owner details and protected-address notices: The request messages, for as long as the hide applies and as long as the law requires us to show we complied. The hide list itself holds a one-way code made from the source and parcel ID, not a name or address
Deleting your account. Sign in and open Account deletion (/account-deletion), or email support@limitline.app from your account email. We verify your identity, cancel any active subscription, and delete or de-identify your personal information within 30 days, except information we must keep for the reasons in the table above. If you are the last owner of a shared workspace, we will ask you to transfer or close it first.
Export. Workspace owners and members can download a structured export of workspace records. Your account data export also includes your own saved LimitLine Assistant conversations from every workspace, never anyone else's. Exports can contain precise and sensitive information; store them carefully.
B10. Who we share information with
We do not sell your personal information and we do not share it for cross-context behavioral or targeted advertising. We share it only as follows.
Service providers that process information for us under contract to provide their services to us. Except as noted for Cloudflare below, they use it only for that purpose:
• Vercel: Website hosting and server code. Information involved: Requests, IP address, logs, data passing through the app.
• Supabase: Sign-in, database, file storage, server functions. Information involved: Account, content, photos, location, logs.
• Stripe: Payments, subscriptions, billing portal, fraud prevention. Information involved: Email, payment card (entered directly with Stripe), billing address, plan and payment history.
• Resend: Sends account and billing email. Information involved: Email address, email content.
• Namecheap Email Forwarding and Microsoft 365: Receives and stores support email. Information involved: Messages you send to support.
• Cloudflare (Turnstile): Bot checks on sign-up, sign-in and password reset. Information involved: IP address, browser and device signals.
• OpenAI: The LimitLine Assistant's AI model (paid plans and free trials started with a payment card), processing requests on our behalf under OpenAI's business terms. Information involved: Your assistant messages and the earlier messages of the conversation, planning goals, the screen and planning information listed in section B6, and a one-way code made from your account ID.
Cloudflare Turnstile's two roles. Cloudflare processes Turnstile data on our instructions to protect LimitLine from bots. Under Cloudflare's Turnstile Privacy Addendum, Cloudflare also uses that data as an independent controller for its own purpose of improving its bot-detection services, and its own privacy policy applies to that use. See section 4 of the Turnstile Privacy Addendum.
Services you use through LimitLine. These receive information directly from your browser or our server to return data, and handle it under their own terms:
• Google and Apple for sign-in.
• OpenStreetMap tile servers (default street map) and USGS The National Map (aerial imagery): your IP address, the map area viewed, and ordinary browser information.
• Apple MapKit (CarPlay map, search and directions).
• Official county and state parcel services (the source is named on the map): tapped points and visible map areas.
• A licensed parcel-data provider, when we use one (for example Regrid, operated by Loveland Technologies): tapped points and visible map areas.
• US government data services, including the National Weather Service and NOAA (forecasts and radar), the US Census Bureau Geocoder (address search), USGS, FEMA, PAD-US, state natural-resource agencies and wildfire services (map overlays), some of them hosted on Esri ArcGIS infrastructure: selected coordinates, map areas or addresses you search, with our server's network information.
• Scout property analysis: when you run a Scout analysis, our server sends the selected map area (the coordinates of the analysis bounds, with no name, email or account identifier) to these public US government data services to fetch land-cover, crop, forest, canopy and wetland data for that area: the USDA National Agricultural Statistics Service Cropland Data Layer (its CropScape online service is hosted by George Mason University), the USGS and Multi-Resolution Land Characteristics Consortium (MRLC) Annual National Land Cover Database, the USDA Forest Service and MRLC NLCD Tree Canopy Cover, LANDFIRE Existing Vegetation Type (a partnership of the USDA Forest Service and the US Department of the Interior), and the US Fish and Wildlife Service National Wetlands Inventory. These government services receive our server's network information, not yours. We do not store their responses beyond the analysis; an analysis result you choose to save is kept like your other content.
• Esri and Impact Observatory Sentinel-2 10 m land cover (property analysis, including Scout): whenever you run a property or Scout analysis, your browser requests land-cover imagery for the selected analysis area directly from Esri's ArcGIS service, so Esri receives your IP address, that map area and ordinary browser information.
• LocationIQ (address suggestions, if enabled): the text you type and an approximate map area.
We do not add your account identifier to these map, parcel, weather, address or analysis requests.
Other sharing:
• People you choose: workspace members according to roles, Field Check-in contacts and guardians who accept, and anyone you send an export to.
• Legal and safety: when we believe in good faith it is required by law or legal process, or needed to protect someone's safety, prevent fraud or abuse, or protect our rights.
• Business transfer: if LimitLine is merged, sold or reorganized, information may transfer to the new owner, which must honor this Policy for information collected under it or give you notice and choices.
• With your consent for any other purpose.
We do not share information with advertisers, data brokers, social networks or marketing partners.
Provider references
B11. Your privacy rights
We honor the following requests from all US users, whether or not your state law requires it. Residents of California, Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Iowa, Delaware, New Hampshire, New Jersey, Tennessee, Minnesota, Maryland, Indiana, Kentucky, Rhode Island, Nebraska and other states with privacy laws may have these rights by law:
• Know and access: what personal information we have about you, and a copy.
• Correct inaccurate information.
• Delete your personal information (section B9).
• Portability: a copy in a usable format.
• Opt out of sale, targeted advertising and significant profiling. We do none of these. We treat a Global Privacy Control browser signal as a valid opt-out request.
• Limit use of sensitive information and withdraw consent for it (section B4).
• Appeal a decision we make on your request.
• Non-discrimination: we will not deny service, charge a different price or give a lower quality of service because you used a privacy right.
How to make a request. The steps depend on the kind of request.
• Opt-outs and limits (no account or verification needed). Requests to opt out of sale, sharing or targeted advertising, Global Privacy Control signals, and requests to limit the use of sensitive information or withdraw consent for it do not require a LimitLine account and do not require you to verify your identity. Email support@limitline.app with "Opt out" or "Limit" in the subject, or write to the address in section B1; a Global Privacy Control signal from your browser counts on its own. We may ask only for the information we need to apply the request to the right records. We honor these requests as soon as feasibly possible and, where the California Consumer Privacy Act applies, no later than 15 business days after we receive them (or a shorter period another law requires).
• Access, portability, correction and deletion (verification needed). Email support@limitline.app from your account email, or write to the address in section B1. We verify your identity by confirming control of your account email and, for sensitive requests, may ask for more information. We will confirm receipt within 10 business days and answer within 45 days. If we need more time, we will tell you why and may take up to 45 more days where the law allows.
An authorized agent may make a request for you with your signed permission. For an access, correction or deletion request, we may ask you to confirm your identity directly; we do not require that for an opt-out or limit request.
Appeals. If we deny your request, you may appeal by replying to our decision or emailing support@limitline.app with "Privacy appeal" in the subject. We will respond in writing within 60 days (or the shorter period your state requires) and explain our reasons. If you are not satisfied, you may contact your state attorney general.
California notice at collection. In the last 12 months we collected these categories of personal information: identifiers (name, email, account and device identifiers, IP address); customer records and commercial information (plan, subscription and payment history; card details are held by Stripe); internet or network activity (logs and feature use); precise geolocation; audio or visual information (photos you upload); and sensitive personal information (account sign-in credentials and precise geolocation). We collect them from you, your device, and the sources in section B2, for the purposes in section B3, and disclose them to the service providers and recipients in section B10. We do not sell or share personal information as California law defines those terms, and we have no actual knowledge of selling or sharing information of anyone under 16. We use sensitive personal information only for purposes California allows without offering a right to limit. Retention is described in section B9. California residents may also ask us once a year about disclosures to third parties for their direct marketing; we make none. Owner names and addresses shown on parcel cards come from government public records, directly or through a licensed parcel-data provider; we display them but do not keep them (section B7).
B12. Children
LimitLine is only for adults 18 and older. We do not knowingly collect personal information from anyone under 18. If we learn that an account holder is under 18, we will close the account and delete the information, except what we must keep for safety, security or legal reasons. If you believe a child is using LimitLine, email support@limitline.app.
B13. Security
We use access controls based on workspace roles, encrypted connections, restricted private storage with short-lived links, server-only privileged operations, and limited data collection. No system is perfectly secure. Protect your sign-in and device. Report suspected security problems to support@limitline.app. If a breach affects your personal information, we will notify you and regulators as the law requires.
B14. Where information is processed
LimitLine is operated in the United States for users in the United States. Our service providers may process or store information in other countries as part of providing their services. For example, Cloudflare's privacy policy (section 7) describes storing data in the United States and the European Economic Area and transferring or accessing it globally; see the Cloudflare Privacy Policy.
Provider references
B15. Changes to this Policy
We may update this Policy. The page shows the version and effective date. For a material change, we will notify you by email or in the Service before it takes effect and, where the law requires, ask for your consent. We will update this Policy before we start using a new category of personal information, a new purpose, or a new kind of provider (for example analytics or advertising).