Skip to content
LocalOnly

Contact

LocalOnly is run by a small team, and email reaches a person rather than a ticket queue. Here is where to send each kind of message, and what to include so we can act on it.

Who you are contacting

LocalOnly is operated by SprintOak and maintained by RavikiranReddy Balemla, a Senior Software Engineer based in Hyderabad, India. Messages reach him directly rather than a support desk, which is worth knowing in both directions: a well-described bug tends to get fixed quickly, and a one-line “it doesn't work” tends to sit unanswered because there is nothing to act on.

There is no phone line and no office to visit, so email is the only real channel. Replies come from hello@sprintoak.com - a @sprintoak.com address, because SprintOak is the operating company behind the LocalOnly domain. You can confirm the identity behind that address on LinkedIn.

General questions and feedback

For anything that does not fit the categories below, write to hello@sprintoak.com. We read every message. Before writing, it is worth checking the FAQ and the documentation, which cover keyboard shortcuts, offline installation and the most common questions about how the tools handle your data.

Requesting a tool or a change

Most of what exists here started as somebody's complaint, so requests are genuinely welcome. Send them to hello@sprintoak.com with the subject “Tool request”.

The most useful requests describe the taskrather than the feature. Telling us “I need to strip the null fields out of an API response before diffing it against a fixture” leads to a better result than “add a filter button”, because it tells us what the output has to be correct for. Anything already planned is listed on the Roadmap.

Reporting a bug

Send bug reports to hello@sprintoak.com. Because everything runs client-side, we have no server logs to check - we can only see what you tell us, so details matter more than usual:

  • The tool and its URL.
  • Your browser and version, and your operating system.
  • What you did, what happened, and what you expected instead.
  • Any error shown in the browser console (open developer tools with F12, then the Console tab).
  • A minimal input that reproduces it - with any real credentials, tokens or personal data replaced by dummy values. Please never email us a payload you would not want stored in an inbox.

Privacy, data protection and legal

For questions about the Privacy Policy, cookies, or to exercise a data-protection right under GDPR, CCPA or similar legislation, write to hello@sprintoak.com. Note that we hold no account records and no copy of anything you have processed, so most access or deletion requests concern data held by Google as our analytics and advertising provider, and we will point you to the right controls. Legal and licensing enquiries go to hello@sprintoak.com.

Advertising and business enquiries

For partnerships, sponsorship or advertising, email hello@sprintoak.com with your proposal. We do not publish sponsored posts, paid links or “guest articles” on this site, so those enquiries will be declined.

Security disclosure

If you believe you have found a vulnerability, please report it privately to hello@sprintoak.com and give us a reasonable opportunity to fix it before disclosing it publicly. Include the affected URL, the steps to reproduce, and the impact you believe it has. Our scope, expectations and disclosure process are set out on the Security page.

Response times

LocalOnly is maintained alongside other work, so a reply typically takes a few business days. Security reports are prioritised ahead of everything else. If a week passes with no response, it is worth resending - occasionally a message is filtered, particularly one carrying an attachment or a code sample.

Elsewhere

You can also reach the maintainer on LinkedIn, though email is monitored more reliably.

Command Palette

Search for a tool or command