Privacy and delivery standards
How we handle your information and your project.
Plain-language commitments for this website and for the software projects we deliver. Website analytics is described on its own, separate from project delivery. Specific terms for each project are agreed in writing before work starts.
01
Website information
- This website does not use accounts or logins.
- This website has no contact form. You can contact us by email.
- Information you send by email is used to review and respond to your inquiry.
02
Website analytics
- We use Google Analytics 4 to understand how this website is used, including which pages people visit, so we can improve the site.
- Google Analytics records visits to pages on this website. It uses cookies or similar technologies to recognize a browser from one page to the next.
- We do not intentionally send names, email addresses, or account IDs to Google Analytics.
- Google describes how its products use information from sites that use Google services: How Google uses information from sites or apps that use our services.
- Questions about privacy on this website can be sent to bryan@bnsapps.com.
03
Access to your systems
- We request appropriate access permissions for each task, and we confirm them with you before connecting to any platform.
- Credentials and API keys are kept out of source code and shared through agreed, secure channels.
- Access can be removed at the end of a project or at any time you request it.
04
Client data
- Your business data is used only for the agreed project work.
- Testing arrangements and the use of client data are agreed for each project.
- Integration feasibility depends on each platform's API, terms, and the access you can provide.
05
Scope and delivery
- Development starts after a written scope with deliverables, priorities, and acceptance criteria.
- Pricing and how scope changes are handled are agreed in advance. Changes are agreed before additional work begins.
- Recurring costs such as hosting and third-party subscriptions are identified separately, including who is responsible for each.
06
Communication
- You communicate directly with the team building your software.
- Collaboration hours are agreed around your time zone at the start of a project.
- Decisions and progress are written down so nothing depends on memory.
07
Ownership and handover
- Code ownership, licensing, account responsibilities, and handover are defined in the project agreement.
- Included support is clearly distinguished from optional ongoing services such as maintenance and monitoring.
- Handover includes the information needed to run and extend what was built.
Questions about these standards? See the FAQ or get in touch.
Build something useful
Tell us what you want to build.
Share your current process, the tools you use, and what you want to improve.
Discuss your project