Security, access and data protection

Panel access: two-step verification

Signing in to Bulutegra is protected by two-step verification. A password alone is not enough; the session does not open until the second step is completed. A leaked password on its own does not give anyone access to your account.

You enable two-step verification per user, not per company. When someone leaves the team you disable that user; you are never forced to run the whole operation through one shared login.

User roles: everyone sees their own area

Bulutegra has six roles: Administrator, Content, Warehouse, Returns, Accounting and Reporting. The role decides what a user sees in the panel and what they are able to change.

Warehouse users work with orders and shipments; they do not see profitability or settlement pages. The content team works on product titles, descriptions, images and quality findings; they do not touch the price matrix. Accounting handles settlements, commissions and reconciliation. The administrator manages users, channels and permissions.

This is as much about clarity as it is about security: nobody can change something by accident on a screen that is not part of their job.

Ownership flags stop the wrong write

In a multichannel operation the most expensive mistake is two systems writing to the same product at the same time. One lowers the price, the other puts it back; stock lands on the wrong channel.

Bulutegra solves this with an ownership flag. For every product and channel pair, one question is answered: is Bulutegra managing this product on this channel, or is an external system? If ownership sits outside, Bulutegra reads and reports that field but never writes to it.

That is what lets you run your existing setup alongside Bulutegra during a migration and hand over channels one at a time.

Shadow mode: read first, write later

During the monitoring step of onboarding the system runs in shadow mode. For one to two weeks it reads from your channels, calculates what it would do and records it, but writes nothing anywhere.

At the end you have a concrete comparison: which stock level, which price and which order Bulutegra would have processed, and where that differs from your current setup. Mapping errors, missing barcodes and wrong categories surface before any live data is touched.

Shadow mode lets you measure the risk of a wrong write instead of guessing at it. Write access is opened only after you approve it, channel by channel.

Connection, passwords and sessions: the technical measures

Connection. Both bulutegra.com and the panel are served over HTTPS only. Browsers receive a one-year HSTS instruction including subdomains, so the address is never even tried unencrypted. Responses carry a content security policy (CSP) together with framing, content-type, referrer and browser-permission policies. The site's fonts are served from our own server; no page makes a request to a third-party server.

Passwords. Passwords are never stored in clear text and cannot be reversed: a random salt is generated per user and the password is hashed with PBKDF2-HMAC-SHA256 over 200,000 rounds. Brute-force attempts hit a lock: five failed attempts from one IP within 15 minutes close login for 15 minutes. Password reset links are signed and time-limited.

Sessions. The session cookie is closed to browser scripts (HttpOnly), sent over HTTPS only (Secure) and not carried on cross-site requests (SameSite). Two-step verification uses the TOTP standard; backup recovery codes are stored hashed rather than in clear, and each works once. The “remember this device” option is a signed, time-limited cookie: once it expires the second step is asked again.

The sections below set out the backup arrangement, how credentials are stored, where the servers run, how we notify security incidents and who our sub-processors are. Any detail not written there either is shared in writing before a contract; ask at destek@bulutegra.com.

Backups: every night, in two separate places

The databases are backed up automatically every night. A consistent copy of the database is taken, while file directories are copied incrementally, so the backup job does not slow the system down.

Backups are kept for fourteen days and are also copied to a second server. Losing one machine does not mean losing the data.

When you close your account, the copies held in backups fall out of the cycle on their own.

How channel and ERP credentials are stored

The credentials needed for your channel and ERP connections are held on the server in files that only the user the service runs as can read. File permissions are closed to any other user on the system, and in the panel only a user with the Administrator role can reveal them, one at a time, on the Settings screen.

Let us be plain here: those files are not protected by disk encryption. We have no separate measure against physical seizure of the disk; the protection rests on limited access to the server and on file permissions. We write this so that a measure we do not have is not implied.

Panel passwords, by contrast, are hashed irreversibly and backup recovery codes are not stored in clear either; the detail is in the technical measures section above.

Where the servers run

The website and the panel run on servers in virtualisation infrastructure we manage ourselves: not on top of a ready-made application platform, but on machines we set up and patch ourselves. Site traffic passes through the Cloudflare network.

We do not publish the country the servers are in or the hosting provider on this page; we share both in writing before a contract. Writing to destek@bulutegra.com is enough to ask.

What we do if there is a security incident

If an incident affects the security of personal data, we notify the affected customers within 72 hours of becoming aware of it.

The notice states what happened, which categories of data were affected, when it was noticed, the measures we took and what needs doing on your side. If the picture is not yet complete we do not wait: we tell you what we know and update it afterwards.

Where the law requires it, notifications to the competent supervisory authorities are made as well. If you spot a security weakness, write to destek@bulutegra.com; we take such reports seriously and get back to you.

The third parties we use to run the service

Our sub-processor list is short and set out here in plain sight:

Cloudflare — site traffic passes through this network, so that the site is served and protected against attacks. Google (Google Analytics) — only if you consented on the cookie banner, and only for website measurement; the customer and order data processed in the panel sits entirely outside it. Our own mail server — form notifications and blog emails are sent from it, with no third-party email service involved.

Live chat is not on that list, because it runs on our own server. The common practice is to hand chat to a cloud provider; we do not, so the content of the conversation stays with us. The site also uses no third-party fonts, no external content delivery network and no CAPTCHA service.

We inform our customers before adding a new sub-processor.

Marketplace API keys

Channel connections stay tied to your own marketplace accounts. Keys are issued in your name and belong to your store. They stay hidden in the panel; only a user with the Administrator role can reveal one on the Settings screen, and the Content, Warehouse, Returns, Accounting and Reporting roles cannot see them.

On Etsy and eBay the connection is made through one-click authorisation. If you stop working with a channel, revoking the authorisation from your own marketplace account is enough: the connection ends at that moment.

AI Camera: footage stays on your premises

In the AI Camera module, processing happens on a local server inside your own facility. Camera footage does not leave the warehouse or the store and is not uploaded to a cloud service.

What leaves the building is the result of the processing, not the image itself: which product, which order, which action. You keep a record of the process without sending video recordings outside your business.

Form verification without a third-party CAPTCHA

The contact and demo forms on this site do not use a third-party CAPTCHA service. Verification runs on our own server.

In practice this means your name, email address and browser details are not handed to a verification provider when you fill in a form. The submission reaches us directly and is used only to reply to you.

Monitoring and transparency

A system health screen shows the state of every connection. Channels are checked continuously; if a channel stops sending data for longer than expected, it is flagged as gone quiet and an alert is raised. You do not find out about a broken connection from a customer complaint about a missing order.

We are equally open about what changes in the product. Release notes state what each update changed, so when a screen or a behaviour is different you can go back and read why.

What data we process and why

Bulutegra processes what the work requires and no more: order records (order number, line items, totals, shipping and payment details), product records (SKU, barcode, price, stock, content) and the customer contact details needed to ship an order (name, address, phone, email).

This data comes from the marketplaces and from your own systems. The purpose is single: to move the order from the channel into your ERP, keep stock and price accurate, and let you follow returns and settlements. It is not used for marketing and it is not sold.

Data is kept for as long as the service continues and applicable retention rules require. You can ask for correction, export or deletion by writing to destek@bulutegra.com, and we answer such requests in writing. The data controller is Markapia Global LLC.

Website analytics and cookies

Two measurement systems run on this website. The first is our own counter: it does not store visitor IP addresses, it produces a hash that changes daily, and the data never leaves our server. The second is Google Analytics, which sends measurements such as page views, referral source and the path taken through the site to Google, and writes a cookie to your browser to do so.

We use Google Analytics to see which content is working, not for advertising personalisation. The customer and order data we process in the panel sits outside this measurement and is never combined with website analytics.

Tracking protection in your browser or an ad blocker will switch this measurement off, and the site continues to work fully. When you press the live-chat button at the bottom right, the script of our support system (Chatwoot, running on our own server) is loaded and a chat cookie is written so your conversation can continue; unless you press the button, that script is never loaded.