1. WHO WE ARE AND WHAT THIS COVERS
Developing Together Technologies LLC is a limited liability company organized under the laws of the Commonwealth of Virginia, at 610 Madison St PMB 626, Alexandria, Virginia 22314. “We”, “us” and “our” mean Developing Together Technologies LLC; “you” means the organization or person using our website or software.
This policy covers our website at devttech.com and the DevTTech Application that we license to customer organizations. Where a separately signed agreement sets different terms for your data, or for feedback, testimonials and correspondence you give us, the signed agreement controls.
2. OUR WEBSITE
We believe in privacy, and we built our website to respect it. Our website collects no information about traffic or users. We run no analytics and no marketing tools, and we set no cookies. It has no contact form: the addresses on it are ordinary mail links.
Our website is hosted by GitHub Pages, and GitHub is the only outside party a visit reaches. GitHub processes the network requests needed to serve a page, which includes your network address, under its GitHub privacy statement.
3. HOW THE SOFTWARE WORKS, AND WHY WE DON’T COLLECT YOUR DATA
DevTTech builds software that runs directly on your own computer. Our application collects published material from user-selected sources and reads the documents you choose. A language model runs on your computer so that all scoring, summaries, synthesis, and general model output never leave your machine.
- Your documents all stay on your computer. They are not uploaded to us, and we have no way to retrieve them.
- The language model runs locally. Nothing you ask the application, and no document it reads, reaches us or any external AI service.
- We do not read your email. The application only asks for permission to send mail on your behalf, and nothing else. It cannot open, search, or list your messages.
We designed this application to give you peace of mind: your data and your intellectual property remain yours. We run no server that holds your content, so we cannot produce it for you, in response to a subpoena, or after a breach on our side: we simply do not have it.
The application also fetches the public sources you configure. Journals, agency pages and news outlets are contacted directly. The briefing feed we publish is served from our website, as section 2 describes. Each request discloses your network address to the site it fetches, as any web request does. The requests do not carry your documents or reports. Where a source asks for a contact address (such as Crossref), the address is the one you enter in your settings, and it is sent only to that source.
4. CONNECTED EMAIL ACCOUNTS
The application emails finished reports to your recipients from an email account you connect, so they arrive as internal mail and the sent copy stays in your mailbox. To do that, the application asks your email provider for one permission: the ability to send mail. A narrower permission does not exist for sending, and routing the mail through our own servers would mean handing us the reports (what the local-only design avoids).
That permission allows one action: sending mail as the account that granted it. It gives no ability to read, open, search, list, label, download or delete messages, and no access to contacts, calendar, files or profile beyond the sending address. We request no other permission from any provider.
The token
When you connect an account, your provider issues a token to the application on your computer. It is saved in a file in the application’s folder, readable only by your user account, and never sent to us. We do not hold, see or back up your account credentials or tokens, and no account password is stored in the software.
What is sent
Only the report itself, to the recipients you configured, through your email provider, from your own account. Each provider’s handling of that mail is governed by that provider’s privacy policy.
Supported providers
Permission and revocation details for each provider:
| Provider | Permission requested | Revoke access at |
|---|---|---|
| Google (Gmail) | Send mail (gmail.send), classified by Google as “sensitive” | myaccount.google.com/connections |
Google accounts
Google issues the token when you complete Google’s consent screen. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We do not transfer or use Google user data for serving advertisements, do not sell it, do not use it to train generalized artificial intelligence or machine learning models, and do not allow humans to read it except with your explicit permission for a specific support request, where required by law, or where necessary for security purposes. Google’s handling of mail you send is governed by Google’s privacy policy.
Other providers
For any provider we add, we use the connected account only to send reports you request, and we follow that provider’s developer and privacy policies. Each one is listed in the table above with its permission and revocation page.
5. INFORMATION WE RECEIVE, AND HOW LONG WE KEEP IT
Three narrow categories, none of them automatic:
- Business contact information: the names, email addresses, phone numbers and organization details you give us when you inquire about, negotiate or hold a license. We keep it for as long as the relationship lasts, and afterward for as long as our legal, accounting and tax obligations require.
- Support material you choose to send: a log file, a screenshot, or a description of a problem. We ask for the least we need, use it only to diagnose the problem you reported, and delete it when the matter is closed. You decide what to send. The application has no telemetry, crash reporting, usage analytics or license check-in, and there is no address of ours in the software for it to report to. Our installer also switches off telemetry in the local model runtime it installs.
- Payment and billing records: kept as long as our tax and accounting obligations require.
Email account tokens are not on this list. They stay on your computer until you revoke or delete them, and they never reach us.
6. YOUR CHOICES, AND HOW TO REVOKE ACCESS
Revoking the email permission
You can revoke it at any time, in either of two places:
- At your email provider, using the revocation page for that provider in section 4; or
- In the application, disconnect the email account.
Revoking stops the application from sending mail. It does not delete mail already delivered, and the rest of the software keeps working as before. To remove the token from your computer, delete the application’s folder or the credential file within it.
Your contact information with us
You may ask what business contact information we hold about you, ask us to correct it, or ask us to delete it, by writing to reports@devttech.com. We will respond within a reasonable period.
7. SHARING AND DISCLOSURE
We do not sell your personal information. We do not share it for advertising, with one exception that requires your written permission: if you agree in a signed agreement, we may use feedback and correspondence you give us about the software, and your name, title and organization in connection with it, as a testimonial or case study in our marketing. We never use your documents, your reports, or Google user data for this purpose. We have no advertising business.
We disclose the information in section 5 only to service providers who help us run the business (and only what each needs), where the law requires it, or to protect our rights, our customers, or the security of our software. If the business is ever sold or reorganized, these records and this policy transfer with it.
8. SECURITY
The architecture is the main safeguard: data we never collect cannot be breached on our side. For what we do hold, we use ordinary, proportionate measures. On your computer, the application restricts the token file to your own user account. Protecting the computer itself, including its login, disk encryption and backups, is your organization’s responsibility under your license agreement.
9. INTERNATIONAL USERS
We operate from the United States. If you use our software or website from elsewhere, the limited information in section 5 goes to the United States, where privacy law may differ from your own.
10. CHILDREN
Our software and website are for organizations and professional use. They are not directed to children, and we do not knowingly collect personal information from anyone under 13.
11. CHANGES TO THIS POLICY
If we change this policy, we will post the new version here and update the effective date. If a change materially reduces the protection of information we already hold, we will tell affected customers directly rather than relying on the posted version. Earlier versions are available on request.
12. HOW TO CONTACT US
Developing Together Technologies LLC
610 Madison St PMB 626, Alexandria, Virginia 22314
reports@devttech.com
devttech.com
This policy describes our practices as of the effective date shown above. It is not a contract and does not replace the license agreement that accompanies the software.