Cookie Policy

This Cookie Policy describes how the Callout website handles cookies and similar storage technologies. It covers this website only. The Callout Android app is covered separately by the App Privacy Policy and the EULA and Terms of Use.

1. Who this policy is from

This website is operated by Bartlett Software LLC, the publisher of the Callout Android app. In this policy, we and us mean Bartlett Software LLC, and this site means the pages served from this domain: the company page at the root that lists our apps, the contact page beside it, and everything about Callout under /callout/ — its home page and every document listed on the Legal page. It does not mean lonestarbids.com, which the root page links to and which is a separate site under its own policies.

2. The short version

This website sets no cookies of any kind. Not strictly necessary cookies, not functional or preference cookies, not analytics or performance cookies, not advertising or targeting cookies, not first-party cookies, and not third-party cookies. There is no cookie to accept, reject, or configure, because none is written in the first place.

The site is a set of static HTML files with one stylesheet, one small JavaScript file, and a few images, all served from this same site. Nothing on these pages profiles you, follows you from page to page, or recognises you when you come back.

3. What a cookie is

A cookie is a small text file that a website asks your browser to save, and that your browser then sends back with every later request to that site. Because the file survives from one page view to the next, cookies are how sites remember a signed-in session, a language preference, or the contents of a shopping basket, and, in the advertising industry, how they remember which pages a particular browser has visited over time.

Cookies are not the only way to do that. Similar technologies include local storage, session storage, IndexedDB, tracking pixels and web beacons, and browser fingerprinting. This policy uses the word cookie broadly enough to cover all of them, and the answer is the same for every one: this site does not use them.

4. What this site does not load

Most cookies on the web arrive with third-party code rather than being written by the site you are actually visiting. This site loads no third-party code at all. Every stylesheet, script, font reference, and image on these pages comes from this site itself, so your browser makes no request to any other company while you read them.

4.1 The one script on the site

A single small JavaScript file runs on these pages. It does two cosmetic things: it highlights the navigation link for the page you are on, and it marks the Google Play button as not yet active while the app is unpublished. It reads nothing about you, writes nothing to your device, and makes no network requests. Every page here is built to work identically with JavaScript disabled or blocked.

5. Local storage and session storage

This site writes nothing to local storage, session storage, or IndexedDB. It stores no identifier for you, no visit counter, and no saved preference. Your browser may still keep the HTML, CSS, image, and script files it has already downloaded in its ordinary cache so that pages load faster next time. That cache is under your control, holds no information about you, and cannot be read by us.

6. Why there is no cookie banner

Article 5(3) of the EU ePrivacy Directive, and Regulation 6 of the UK Privacy and Electronic Communications Regulations (PECR), require consent before a website stores information on, or gains access to information stored on, a visitor's device, unless that storage is strictly necessary to provide a service the visitor asked for. Satisfying that rule is what cookie banners exist to do.

This site neither stores information on your device nor reads information stored there, so no consent is required, and a banner asking for it would be theatre rather than a legal obligation. For the same reason, because no cookie or similar identifier is set, this site builds no profile of you and processes no personal data for analytics, advertising, or any other purpose that would need a lawful basis under the EU General Data Protection Regulation or the UK GDPR.

If any of that ever changes, this policy changes with it, and any consent the law requires would be asked for before anything was stored. See section 10.

7. Server logs, the one caveat

One thing does happen that is worth stating plainly, because a cookie policy claiming that absolutely nothing is recorded anywhere would be misleading.

This site is served by a third-party hosting provider, and a content delivery network may sit in front of it. To deliver a page to you at all, those providers necessarily receive, and may record in their server logs, standard connection data: typically your IP address, your browser's user agent string, the URL you requested, the referring URL if your browser sent one, and a timestamp. This is a technical necessity of how the web works, since a server cannot send a page back without knowing where to send it.

Note what this is and is not. It is not a cookie. Nothing is written to your device, and no identifier follows you from one page to the next. We do not use these logs to track, profile, or measure visitors, we run no analytics over them, and we do not combine them with anything else. The Website Privacy Notice covers this in more detail, including the role of the hosting provider.

8. The Callout app

The Callout Android app uses no cookies. It has no browser component and no embedded web view, and it contains no advertising, no analytics, no crash-reporting or telemetry code, and no account system. Its release build does not even request the Android internet permission. Everything you create in the app, including routines, alarm settings, callout text, and voice recordings, stays in the app's private storage on your own device.

Separately from the app itself, Google Play gives the developer limited, anonymized sales and crash statistics for the store listing. That happens on Google's side, involves no code in the app and no cookie, and identifies no individual to us; it is described in section 4.1 of the App Privacy Policy.

The app's full data practices, including the one caveat about the third-party text-to-speech engine that speaks your callouts, are set out in the App Privacy Policy. The copies of the Privacy Policy and the EULA bundled inside the app are the authoritative versions you agree to when you use it.

9. Links to Google Play and other sites

Pages on this site carry a Google Play button for Callout. The app is not published yet, so that listing is not live at the time of writing, and the button is presented as coming soon rather than as a live download. Google Play is operated by Google, not by Bartlett Software LLC, so if you do follow that link once it leads somewhere, you are on a site we do not control, and Google's own cookie, storage, and privacy practices apply there from that point on, instead of this policy. The same is true of any other external destination reached from this site, including a mail application opened by an email link.

Following a link away from this site is the point at which the guarantees in this policy stop applying. Nothing on these pages loads Google content in the background, so simply reading this site sends nothing to Google.

10. Changes to this policy

This policy will be updated if the way the site works ever changes, and the Last updated date at the top of the page will change with it. There is no mailing list and no notification mechanism, precisely because this site collects no contact details, so that date is how to tell whether anything has changed since you last read it.

Adding cookies, analytics, or third-party embeds is not planned. If it ever happened, this page would say so specifically, naming what was set and why, and any consent required by law would be obtained before anything was stored on your device.

---

11. Contact

Questions about this policy, or about anything on this site, are welcome by email. The address is on the contact page.

Bartlett Software LLC
bartlettsoftwarellc.com/contact

Related documents: the Website Privacy Notice, the Website Terms of Use, the App Privacy Policy, and the EULA and Terms of Use. All of them are listed on the Legal page.