Secure. Powerful. Easy to use.
Terabat Apps builds software for individuals and small businesses who need capable tools without unnecessary complexity.
We believe good software should do more than simply work. It should respect the people using it, protect the information entrusted to it, explain what it is doing, and make difficult tasks easier to accomplish.
These principles guide how we design our products today and how we intend to build them in the future.
Software Should Work for People
Powerful software does not have to be complicated software.
We design our products so that people can accomplish meaningful work without needing to understand the technical systems operating behind the scenes.
That means clear language, sensible workflows, helpful guidance, and interfaces designed around what the user is trying to accomplish—not around how the software happens to be built.
Our goal is professional-grade capability without unnecessary enterprise complexity.
Privacy by Design
Privacy should be part of the architecture of a product, not something added later as a policy statement.
Whenever practical, we design software to:
- collect only the information it actually needs;
- process sensitive information locally when appropriate;
- avoid unnecessary transmission of private data;
- minimize the amount of information stored;
- protect credentials, passwords, and other sensitive information;
- keep private user content out of diagnostics and logs; and
- clearly explain when information must leave the user’s device.
Simply having access to information does not mean an application should use it.
Local When Local Makes Sense
Some tasks do not need the cloud.
For our desktop and local applications, we prefer local processing when it provides the functionality the product needs while improving privacy, reliability, or user control.
Online services may still be necessary for features such as licensing, updates, compatibility information, account services, or support. When they are used, our goal is to keep those interactions focused on the information required for that specific purpose.
Private user content should not be uploaded simply because doing so would be convenient for us.
Responsible Cloud Software
Some products are designed to operate as hosted services. In those cases, information must be stored and processed online for the application to work.
Our SaaS products are designed around a different but equally important set of responsibilities.
We aim to:
- isolate customer and tenant information appropriately;
- limit access according to need;
- use appropriate security controls;
- protect credentials and secrets;
- minimize unnecessary collection and retention;
- clearly explain how customer information is used;
- provide understandable retention and deletion practices; and
- avoid using customer information for unrelated purposes.
Cloud software should earn the trust required to hold customer information.
Security Should Be Built In
Security should not require the user to become a security expert.
We believe secure defaults, careful credential handling, appropriate access controls, data protection, and responsible software-update practices should be built into the product itself.
Where security choices must be made by the user, we should explain those choices clearly enough for a normal person to make an informed decision.
Security should make software safer—not unnecessarily harder to use.
Respect the User’s Data
A user’s information belongs to the user.
Our products should avoid unnecessary destructive behavior and, whenever practical, preserve original information before creating modified, reduced, converted, or exported versions.
When software creates backups, exports, reports, documents, or other important files, we should design workflows that reduce the chance of accidental overwriting or data loss.
Data preservation is a product-design responsibility, not merely a user responsibility.
Safety Is Not a Premium Feature
Paid plans may provide additional capability, capacity, automation, convenience, or professional features.
Basic protections for user data should not be intentionally weakened or withheld simply to create another pricing tier.
Security, privacy, safe handling of information, and reasonable protection against accidental data loss should be part of the foundation of the product.
Honest Software
We believe software companies should describe their products based on what those products can actually do.
That means avoiding exaggerated claims, clearly communicating limitations, and distinguishing between what the software knows and what it may only infer.
If a product cannot reliably determine something, we should not present that information as a certainty.
Trust is more valuable than a marketing claim.
Powerful Without the Bloat
Small businesses and individual users often need many of the same capabilities found in larger enterprise systems—but they may not have dedicated IT departments, security teams, implementation consultants, or weeks to learn a new application.
That is an important part of why Terabat Apps exists.
We want to build tools that provide serious capability while remaining practical, understandable, and affordable for the people and organizations using them.
Secure. Powerful. Easy to use.
Designed to Improve
Our design ethos is not intended to be static.
As we build new products, learn from our customers, encounter new technologies, and improve our internal standards, these principles will continue to evolve.
Individual Terabat Apps products may also have additional design rules based on the type of information they handle and the people who depend on them.
What should remain consistent is the underlying goal: build useful software responsibly.
Built by Terabat Apps
When you see Built by Terabat Apps, we want it to mean something.
Software designed to respect your information.
Software that does not make simple things unnecessarily difficult.
Software that is honest about what it can do.
Software built with security and privacy in mind from the beginning.
