Legal

This page sets out the baseline legal terms for using rmnbb.com and for working with P/E Roman Babakin, an individual entrepreneur registered in Georgia and operating through this website and client portal.

This website and the related services are intended for business customers. By using the website, contacting through it, creating an account, or purchasing services, you agree to these terms unless separate project-specific terms are agreed through the client portal or in writing.

1. Provider

Services on this website are provided by:

P/E Roman Babakin
Individual Entrepreneur registered in Georgia
Website: rmnbb.com
Legal and support contact: contact@rmnbb.com

2. Services

I provide custom software development and ongoing support for small and medium-sized businesses, including internal systems, client portals, automations, integrations, and AI-enabled products.

My standard delivery model is Software with a Service (SwaS):

a paid implementation stage for discovery, design, development, and launch;
followed by an optional recurring support subscription for the live production system.

The subscription is designed to keep the solution operational, supported, and evolving in a controlled way. It covers operation of the live system, monitoring, incident handling, technical support, and a limited amount of small improvements. Major enhancements, new modules, new integrations, substantial workflow changes, and architectural rework are handled as separate paid stages.

3. Project Terms and Official Records

Each client project is managed through the rmnbb.com client portal.

The portal is the primary place where project scope, stage terms, payment status, releases, incidents, approvals, support history, and other project records are maintained. These records form the official project history and are the primary reference point for delivery and support matters.

Clients can export project records and related documents from the portal in signed PDF format. A signed export reflects the recorded state of the project at the time of export and provides an independent record of that version.

If a project includes specific commercial terms, scope documents, an NDA, support terms, or other written project conditions, those project-specific terms take precedence over this public page for that project.

4. Official Communication Channels

Unless a project states otherwise, the official communication channels are:

the rmnbb.com client portal, for project communication, approvals, incidents, and delivery history;
contact@rmnbb.com, for initial contact and as a fallback if the portal is unavailable.

Other channels can be used for convenience, but they are not treated as official unless expressly confirmed for a specific project.

5. Payments

Implementation pricing, support pricing, billing structure, and payment timing are defined for each project.

Unless otherwise agreed:

implementation work starts after the relevant stage is approved and the agreed payment conditions are met;
support subscriptions are billed in advance for the applicable service period;
support, access, and active service depend on an active paid period;
if payment is not continued, the service period ends at the end of the paid term.

Payment of an invoice confirms acceptance of the relevant paid stage or subscription period under the project terms recorded at the time of invoicing.

6. Intellectual Property

Unless otherwise agreed in writing:

the client owns its business data;
I retain ownership of my codebase, frameworks, methods, templates, tools, internal components, know-how, and delivery processes;
the client receives the agreed access to and use of the delivered solution as part of the service model.

Source code and underlying implementation are not transferred by default. If a project includes a source code transfer, buyout, or broader IP assignment, that must be expressly agreed in the relevant project terms.

7. Client Data and Export

Client business data remains the client's data.

For supported projects, I provide a reasonable technical ability to export client business data in a machine-readable format, typically CSV and/or JSON, as defined for the project. Project records and selected project documents can also be exported from the portal in signed PDF format.

Unless separately agreed, the service includes data export capability, but not a full migration to another provider, platform, or custom environment.

8. Confidentiality

Confidential information shared during discussions, discovery, delivery, and support is handled with appropriate care and used only as needed to evaluate, deliver, operate, or support the services.

Where needed, a separate NDA can be signed before deeper discovery or data sharing begins. If an NDA is in place, that NDA governs confidentiality for the relevant project.

9. AI-Assisted Work

I may use AI tools and external automation services to assist with analysis, planning, development, testing, support, and internal operations.

AI is used as a supporting tool under my direction and control. Final responsibility for architecture, security-sensitive decisions, infrastructure, and delivered results remains with me.

When external AI services are used, I apply a data minimization approach:

only the data needed for the specific task is shared;
anonymized, reduced, synthetic, or test data is preferred where practical;
sensitive data, secrets, and full production exports are not sent to external AI services unless that use is necessary and appropriate for the project.

If a project involves regulated, highly sensitive, or specially restricted data, any additional handling requirements must be defined in the project terms.

10. Support and Service Levels

If a project includes ongoing support, the detailed support model is defined at project level, including support windows, response targets, incident priorities, maintenance expectations, and any service credit rules.

Unless expressly agreed otherwise:

support is provided on a professional business-use basis, not as an unlimited development retainer;
incidents must be reported through an official channel;
planned maintenance, third-party outages, force majeure events, and client-caused issues are outside normal uptime calculations.

Any uptime commitments, response targets, or service credits apply only during an active paid support period and only to the extent included in the relevant project terms.

11. End of Service and Retention

There is no mandatory minimum subscription term unless a project states otherwise. A client can end ongoing support by not renewing the next paid period.

Unless otherwise agreed for a specific project:

the system can be suspended or stopped after the paid period ends;
client business data is retained for up to 30 calendar days after service stop;
during that retention period, the client can export available business data and project records;
after that retention period, the data can be deleted as part of normal cleanup procedures.

If a project includes a different retention period, export scope, or deletion procedure, the project terms apply.

12. Acceptable Use

You may not use the website, portal, or services:

for unlawful, fraudulent, abusive, or infringing activity;
to interfere with the operation, reliability, or security of the website or services;
to attempt unauthorized access, distribute malicious code, or misuse infrastructure;
in violation of applicable sanctions, export controls, or other legal restrictions.

I can suspend or refuse access where reasonably necessary to protect the website, infrastructure, clients, or legal compliance.

13. Privacy Notice

This section explains how personal data is processed in connection with the website, client portal, inquiries, and business relationships.

14. Data Collected

Depending on how you interact with the website or services, I may process:

contact details such as name, email address, company name, role, and message content;
account and project information submitted through the portal;
billing and transaction information;
technical data such as IP address, browser type, device information, access logs, and usage events;
communication and support records.

15. How Data Is Used

Personal data is used to:

respond to inquiries and communicate with prospects or clients;
evaluate project fit and prepare proposals or project terms;
create and manage client accounts and project records;
deliver, secure, maintain, and improve the services;
process billing and maintain business records;
meet legal, tax, accounting, and compliance obligations;
prevent abuse, fraud, and security incidents.

16. Legal Basis

Where applicable, personal data is processed on one or more of the following grounds:

to take steps before entering into a contract;
to perform a contract;
for legitimate business interests, including operating, securing, and improving the services;
to comply with legal obligations;
based on consent where consent is required.

17. Data Sharing

I do not sell personal data.

Personal data is shared only as reasonably necessary with:

hosting, infrastructure, email, analytics, payment, monitoring, and support providers;
subcontractors or service providers involved in delivering the agreed services;
legal, regulatory, tax, or public authorities where required by law;
a successor or acquiring party in the event of a business transfer or reorganization.

Where third-party providers are used, they process data as part of the operating stack for the website or project delivery.

18. International Processing

Because the services are provided online and may rely on international infrastructure providers, personal data can be processed in countries other than your own. Where this happens, I use reputable providers and apply appropriate safeguards in line with the business context and the nature of the services.

19. Retention of Personal Data

Personal data is kept for as long as reasonably necessary for communication, project delivery, support, recordkeeping, compliance, security, and dispute resolution. Different categories of data can have different retention periods depending on their purpose.

20. Security

I use appropriate technical and organizational measures to protect data, including access controls, backups, and standard operational safeguards suited to the services provided and the type of data involved.

If I become aware of a security incident affecting client data, I will notify the affected client through an official channel without undue delay and, for supported production projects, typically within 24 hours of confirmed discovery.

21. Cookies and Technical Logs

The website may use essential cookies, server logs, and basic technical analytics required for security, functionality, performance, and service improvement.

If non-essential cookies or tracking tools are introduced, this page and any required consent mechanism will be updated accordingly.

22. Your Rights

Depending on the laws that apply to you, you may have rights to request access to, correction of, deletion of, restriction of, or export of certain personal data, or to object to certain processing.

Requests can be sent to contact@rmnbb.com. Reasonable verification may be required before a request is completed.

23. Website Information and Availability

I work to keep the website and services available, reliable, and professionally maintained. Temporary interruptions can occur from time to time due to third-party dependencies, or circumstances outside reasonable operational control.

Information published on this website is provided for general business information and does not create a binding delivery commitment unless confirmed in project-specific terms.

24. Liability

Total liability arising from a project or service relationship is limited to the amount paid by the client for the affected service during the 3 months preceding the event giving rise to the claim.

Nothing in this page excludes liability that cannot be excluded under applicable law.

25. Governing Law

Unless otherwise agreed for a specific project, this page and any non-project-specific dispute are governed by the laws of Georgia, without regard to conflict of law rules.

Before starting formal proceedings, both sides should first try to resolve the matter in good faith through the official communication channels.

26. Updates

I can update this page from time to time to reflect changes in the website, services, operating model, or legal requirements. The latest version published at rmnbb.com/legal applies from its effective date unless separate project terms provide otherwise.

27. Contact

For legal, privacy, or service-related questions, please use:

rmnbb.com
contact@rmnbb.com