What we collect, why we hold it, and what stays yours.
Four policies. One covers you as a visitor. One covers how you may use the platform. One covers your team's data and the AI that drafts your work. One covers what runs in your browser.
Privacy policy
Version 1.1. Last updated . This version adds LinkedIn's Insight Tag, which runs only if you accept cookies.
This policy covers you as a visitor to this site and as someone who contacts us. It sets out what we collect, why we hold it, how long we keep it, and what you can ask us to do about it.
Data your team puts into the platform is a different question. That is covered under Data privacy.
Who this policy covers
It applies to this website at technocenter.io, to the sign-in page at platform.technocenter.io, and to any enquiry you send us by email, phone or WhatsApp.
It does not cover what happens inside the platform once your organisation is a customer.
It does not cover other companies' sites you reach from links here. Once you leave, their policies apply.
What you give us
When you request a demo, we ask for three things and offer two more:
Your full name.
Your work email.
Your company.
Your team size, chosen from a short list. Optional.
A note telling us what you would like to see. Optional.
That is the whole form. We do not ask for a phone number, a job title or a budget.
The note is a free-text box. Keep confidential project detail out of it, and do not paste in other people's personal information. Tell us what you want to see and we will ask the rest on the call.
If you email, phone or message us on WhatsApp instead, we hold whatever you chose to send, plus the address or number you sent it from.
What your browser tells us
We count visits with Plausible, which runs on every page of this site.
It records the page you viewed, the site or search that sent you, your country, and your device and browser type.
It sets no cookie. It does not follow you to other websites. It does not build a profile that identifies you.
We use the counts to see which pages are useful and which are not. There is nothing else in it.
LinkedIn, if you accept cookies
We advertise on LinkedIn. To see whether those ads work, we use LinkedIn's Insight Tag. It runs only if you press Accept on the cookie banner.
When it runs, it tells LinkedIn the page you are on, the page that sent you, your IP address, your device and browser type and the time of the visit.
If you have a LinkedIn account, LinkedIn can match the visit to it.
What we get back are totals. How many people reached us from an ad. The job functions, industries and company sizes of visitors as a group. LinkedIn does not tell us who you are.
We can also ask LinkedIn to show our ads to people who have visited this site. We see how big that audience is, never who is in it.
We do not send LinkedIn your email address, your demo request or anything else you type here.
LinkedIn's privacy policy covers what LinkedIn does with the data.
The spam trap
The demo form carries a hidden field that a person never sees and never fills in. Automated spam tools fill it in anyway.
If that field comes back with anything in it, we drop the submission without reading it. Nothing is stored and nobody is notified.
Why we use it
Six reasons, and no others:
To answer your enquiry and arrange the demo you asked for.
To keep a record of the conversation, so the next person to pick it up has the context.
To count visits so we can improve the pages.
If you accepted cookies, to measure our LinkedIn ads and show them to people who have visited.
To protect the site from abuse and spam.
To meet an obligation the law puts on us.
We do not sell your personal information. We do not share anything you send us for advertising. The LinkedIn tag is the only advertising tool on this site, and it waits for your Accept. We do not add you to a marketing list off the back of a demo request, and we do not pass your details to anyone else to sell to you.
Where a demo request goes
Worth knowing how the form works today. It is not wired to a customer-relationship system.
When you submit it, the request reaches us as an ordinary email to support@technoempower.com and sits in that mailbox with the rest of our support mail. The people who can see it are the people who staff that mailbox.
If we connect the form to a form service or a CRM, we will name that service here before we switch it on.
Who else your browser talks to
Some things on this site are fetched from other companies' servers. Any request your browser makes carries your IP address, because that is how a reply finds its way back. These are the ones:
plausible.io, on every page, for the visit counting described above.
snap.licdn.com, px.ads.linkedin.com and www.linkedin.com, on every page but only after you accept cookies, for the LinkedIn ad measurement described above.
cdn.simpleicons.org, svgl.app, cdn.jsdelivr.net and upload.wikimedia.org, on a few pages, for the small product logos shown next to names such as Jira and OpenAI.
Those logo requests carry a no-referrer instruction, so the server sending the image is not told which page asked for it.
Fonts are different. They are served from this site, not from a font network, so no third party sees you loading them.
Two links hand you over entirely. The WhatsApp button opens a chat with us through Meta, under Meta's terms. Signing in opens platform.technocenter.io, which is a separate application with its own notice.
How long we keep it
An enquiry stays with us while the conversation is live, and for a reasonable period afterwards so we can pick the thread up if you come back.
Visit counts are aggregate. There is nothing in them to link back to you.
If you accepted cookies, LinkedIn removes anything that directly identifies you within seven days of a visit and deletes the rest within 180 days.
Where the law sets a period, we follow it.
If you want your enquiry deleted sooner than that, ask and we will.
Your rights
Subject to the law that applies to you, including POPIA in South Africa and the GDPR where relevant, you can ask us to:
tell you what we hold about you,
give you a copy of it,
correct anything that is wrong,
delete it,
stop using it for a particular purpose,
withdraw a consent you gave us.
Ask, and we will act within the time the law allows. We will not charge you for a reasonable request.
If we cannot do what you asked, we will tell you why rather than go quiet.
If you are not satisfied with how we handled it, you can take it up with the data-protection regulator that applies to you.
How to reach us
One mailbox handles all of this: support@technoempower.com. Put one of these in the subject line so it reaches the right person quickly:
Privacy request — a question about this policy.
Data request — access, correction, deletion, or a copy of what we hold.
Cookies — anything about what your browser stores.
You can also call 0861 787 777 or message us on WhatsApp at +27 79 498 0243. Both are fine for a question.
Send anything you want us to act on in writing to the mailbox, so there is a record of what you asked and when.
Changes to this policy
The version number and date at the top tell you what you are reading.
When we change something that affects you, we say so here rather than change it quietly.
We do not reserve a right to rewrite this without telling you.
Terms of use
Version 1.0. Last updated .
These terms cover the TechnoCenter website and platform. By using either, you accept them.
If your organisation has signed a separate agreement with us, that agreement governs your use of the platform. Where the two differ, the signed agreement wins.
What these terms cover
They apply to this website, to the platform at platform.technocenter.io, and to any trial or evaluation access we give you.
They sit alongside the Privacy policy and the Data privacy policy on this page. Read the three as one set.
Pricing, plan limits and what each resource pack includes are on the pricing page. We have not repeated the numbers here, because that page is where they are kept current.
Who can agree to them
TechnoCenter is built for organisations, not for personal use.
If you accept these terms for a company, you are confirming you have authority to bind it. If you do not have that authority, do not accept them.
Your account
You decide who in your organisation gets access, and you are responsible for what they do with it.
Keep sign-in details private. Do not share a login between people.
The platform gives you fine-grained access controls over both users and Lumina agents, so you can scope what each one can reach. Premium resource packs add single sign-on and SAML, so access follows your own identity provider.
If you think an account has been used without permission, tell us straight away with Security in the subject line.
Plans, fees and AI tokens
What you pay and what you get is set out on the pricing page or in your agreement.
Every interaction with a Lumina agent uses AI tokens, and your allowance comes from your resource pack. When the allowance runs out, agent work stops until it is topped up.
We may apply rate limits where one account's usage puts the service at risk for everyone else. We will talk to you before we do that, unless the problem is urgent.
Acceptable use
Use the platform for lawful delivery work. Do not:
break the law, or help someone else break it,
upload content you do not have the right to use,
upload malware, or try to get past the virus scanning on uploads,
try to reach another customer's data, or another user's account,
probe, scan or load-test the platform without our written permission,
run a denial-of-service test against it,
reverse-engineer the platform, or copy it to build something that competes with it,
resell, sublicense or rent access to it,
share credentials, or put more people on it than you have paid seats for,
use it to produce unlawful, harassing or discriminatory content,
put personal data into it that you have no lawful basis to process,
automate access to the API beyond what your agreement allows. The API is private, not open for public use.
One of those deserves more than a bullet. Lumina generates test data on request, which makes it tempting to paste real production records in as a starting point. Do not. Test data should be synthetic or properly de-identified, and special-category personal data does not belong in a test environment at all. That call is yours to make, and yours to answer for.
Acceptable use of Lumina
AI output carries its own rules.
Review before you use it. Lumina drafts. Your team accepts, edits or rejects. Nothing is published and nothing syncs to your other tools until a person approves it.
Do not present Lumina output as professional judgment. It is a draft written from the inputs you gave it.
Do not use it to reproduce someone else's protected work.
Lumina is not a replacement for QA expertise. It handles the drafting. Your team handles the judgment, and the accountability stays there.
If you break these rules
We may suspend or restrict access where use breaks these terms or puts the service at risk.
Where we can, we tell you first and give you a chance to put it right.
Serious or repeated breach ends access.
We do not delete your data as a punishment. If access ends, you get the chance to export it. See How long data stays.
Your content stays yours
You keep ownership of everything you bring into the platform. Your requirements, your test assets, your data, your files.
You give us the permissions we need to host and process that content in order to run the service for you, and nothing beyond that.
Work Lumina drafts from your inputs is yours too, as between you and us. What a model provider's own terms say about output is a separate matter, covered under Which model your content reaches.
What stays ours
The platform, the site, the software behind them, and the TechnoCenter and Lumina names are ours.
You get the right to use the platform under your plan. You do not get ownership of it.
Other companies' names and logos shown on this site belong to those companies. Showing them says these tools connect. It does not say those companies endorse us.
Tools you connect
Connecting a tool such as Jira is you instructing us to move data between it and TechnoCenter.
Jira is a two-way sync. You resolve conflicts. TechnoCenter-only data is never overwritten.
You are responsible for the credentials you give us and the permissions attached to them. Grant the least access that does the job.
What happens to data once it is back inside the other tool is governed by that tool's terms, not ours.
Availability and changes
We work to keep the platform available and to keep it secure.
We do not promise uninterrupted service, and we do not publish an availability figure here. Where you need a service commitment, it belongs in your agreement.
We do maintenance, and we ship changes. Where a change materially affects how you use the platform, we give reasonable notice.
We may update these terms. The version and date at the top show what you are reading, and material changes are called out.
Liability
The platform is provided as it is. We do not warrant that it will be free of errors.
Lumina drafts work. A person on your side approves it. That approval is the point at which responsibility for the output passes to you, and that is deliberate.
To the extent the law allows, we are not liable for indirect or consequential loss, including lost profit, lost data or business interruption.
Any limit or cap on our liability is set out in your agreement with us.
Nothing here limits liability that the law does not allow us to limit.
Ending access
You can stop using the platform whenever you like.
Notice periods, cancellation and refunds are set out in your plan or agreement.
Before you go, ask for an export. Put Data request in the subject line.
Governing law
These terms are governed by the law of the Republic of South Africa. The courts of South Africa have jurisdiction over any dispute about them.
This policy covers the data your team works with inside TechnoCenter and Lumina. Who decides what happens to it, where it runs, how it is kept apart from other customers' data, what Lumina does with it, and how we protect it.
Data we collect about you as a website visitor is covered under Privacy policy.
Who decides what
Your organisation decides what data goes into the platform and why. We process it on your instructions in order to run the service.
In data-protection language, you are the controller and we are the processor. In plain terms: it is your data and your decision, and our job is to do what you asked with it and nothing else.
We align our handling of personal data with the law that applies to you, including POPIA in South Africa and the GDPR where relevant.
What lives in the platform
The delivery work itself. Product strategy, epics and user stories. Test plans and test cases, including negative cases. Test data. Automation scripts. Requirements, defects and test results.
Alongside it, the account and activity records that make the platform work. Who your users are, what they did, and when.
Then whatever else your team uploads or types. Files, attachments and free-text fields.
That last category is the one to watch. A free-text field will hold anything, including personal data nobody planned to put there. Setting the standard for what your team writes into one is your call, and it is worth making explicitly.
Where it runs
The standard deployment is a hosted private cloud. That is a VPC in AWS, which we run for you.
Premium resource packs add two other options: your own private cloud, or on-premise. Both run in containers on Docker or Kubernetes, on Windows or Linux, across AWS EKS, Azure AKS, Google GKE, Red Hat OpenShift and STACKIT.
If you self-host, you run the infrastructure. The controls described under How we protect it are ones we operate in the hosted deployment. In your own environment, most of them become yours.
We have not named a region here, because the answer depends on your deployment. Ask us where your instance will run before you sign, and we will tell you.
Your data is kept apart
Customer data is ring-fenced. Every resource pack includes a dedicated knowledge base, and that is where your content and your training data sit.
Access controls apply per user and per Lumina agent, so separation holds inside your organisation as well as between organisations.
How Lumina works with your data
Lumina drafts from the inputs and the scope you give it. It works step by step and shows its reasoning, so a person can read it and correct it.
Every item it produces comes with three choices: accept, edit or reject.
Nothing is published, and nothing syncs to your other tools, until a person approves it.
It never acts on its own. It waits for your inputs, does the work you assigned, and hands it back.
It does not test your software by itself, and it has no authority to publish anything without approval.
Which model your content reaches
This is the part of the AI story people most need in writing, so here it is plainly.
Each Lumina agent is assigned a large language model. Which models you can choose depends on your resource pack:
Basic runs on OpenAI, with GPT-4o-mini as the default.
Standard and Premium let you choose across models from OpenAI, Anthropic, Google and Meta.
Premium can bring its own model, in which case requests go to the endpoint you configured.
When a Lumina agent works an item, the content of that item is sent to the model provider you selected, so that the model can do the work. That provider's own terms govern what happens to the request at their end.
If you bring your own model, that traffic goes where you pointed it, and your arrangement with that provider applies.
Choosing the model is therefore also choosing whose terms apply to your content. Ask us which models are available on your pack before you assign an agent to real work.
Training your agents
Training data is what you give a Lumina agent so it learns your goals, standards, team and organisation. It is how an agent produces something that reads like your team wrote it.
Your training data lives in your dedicated knowledge base.
You decide what goes into it, and you keep it current as your standards change. Train mode is available on Standard and Premium packs.
All training data and AI interactions are auditable. You can see what an agent was given and what it produced from it.
What we do not do with your content
We do not sell it.
We do not use it to advertise to you.
We do not give another customer access to it.
We do not use it for any purpose other than running the service for you and meeting an obligation the law puts on us.
What a model provider does with a request sent to it is governed by that provider's terms, not by this policy. See Which model your content reaches. If that matters to your risk assessment, and for a bank or an insurer it should, ask us for the current terms of the model you plan to use before you assign an agent to real work.
How we protect it
The controls that apply in the hosted deployment:
Fine-grained access controls over users and over Lumina agents.
Files and uploaded content are scanned for viruses before they are stored.
A data-governance programme keeps user and agent activity monitored and auditable.
Customer data is ring-fenced in dedicated knowledge bases.
Integration keys and access tokens are vaulted and encrypted.
The API is private. It is not open for public use.
Daily monitoring and automated threat detection.
Single sign-on and SAML on Premium resource packs, so access follows your identity provider.
Traffic between your browser and the platform is encrypted with TLS. TLS protects data while it moves. It does not protect data at rest, and we would rather say that than blur the two.
For encryption of stored data, the answer depends on your deployment and the storage behind it. Ask us and we will tell you what applies to yours.
What we do not claim
We do not hold ISO 27001, SOC 2 or any other security certification today, and we do not claim one.
If your own compliance requirement needs a certified provider, say so early and we will tell you honestly whether we meet it.
Reporting a security problem
If you find a vulnerability, tell us. Email support@technoempower.com with Security in the subject line.
Send us what you found, how to reproduce it, and what you think the impact is. A short, clear write-up is worth more than a scanner dump.
We will acknowledge your report and look at it. We would rather not put a clock on that than put one up and miss it.
What we ask of you:
Give us a reasonable chance to fix it before you publish anything.
Do not access, change or delete anyone else's data while you are testing.
No load testing and no denial-of-service testing.
Stay within your own account and your own data.
If you report in good faith and stay within those lines, we will not pursue you for it.
We do not run a paid bounty programme. If we did, this is where it would say so.
If something goes wrong
If a security incident affects your data, we tell you.
We tell the relevant regulator where the law requires it.
We tell you what we know, what we do not yet know, and what we are doing about it. An incomplete update early beats a tidy one late.
How long data stays
Your data stays while your subscription runs.
When it ends, you can ask for an export, and we remove the data in line with your agreement.
Where the law requires us to keep something, we keep only that, and only for as long as it requires.
If you need a defined retention period written down, it belongs in your agreement. Ask us and we will put it there.
Requests from your team, and from your customers
If someone asks you to access, correct or delete personal data that sits inside TechnoCenter, that request is yours to answer. You know the context and you hold the relationship.
We will help you find it, export it or remove it. Email support@technoempower.com with Data request in the subject line.
If a request comes to us directly about data inside your platform, we point the person back to you rather than act on it ourselves.
Other services in the path
Running the platform involves other companies. Which ones depends on your deployment and your choices:
The cloud your instance runs on.
The model provider you selected for each Lumina agent.
Any tool you chose to connect, such as Jira.
We have not published a fixed list here. It would be out of date the week after it went up, and a stale list is worse than none. Ask us for the current one before you sign and we will give it to you in writing.
Questions about your data
Email support@technoempower.com. Use Data request for access, correction, deletion or export. Use Privacy request for a question about this policy. Use Security for a vulnerability report.
Cookie notice
Version 1.1. Last updated . This version adds LinkedIn's Insight Tag, which runs only if you accept.
Short version first, then the detail.
Our visit counting uses no cookies. One thing on this site does: LinkedIn's Insight Tag, which measures our LinkedIn ads. It runs only if you press Accept. If you reject, the only thing stored is your answer.
What is actually stored
Your answer, whichever way you answer. It is not a cookie.
When you accept or reject on the banner, we save an entry called tc_cookie_consent_v2 in your browser's local storage. It holds two things: which you chose, and when you chose it.
It stays until you clear site data for this site.
It lives in that browser on that device. A choice made on your laptop does not carry across to your phone, so the banner appears again there.
If you answered before 15 October 2026, the banner asks again. That answer was given before the LinkedIn tag was here, so an old Accept does not count as a yes. An old Reject still stands.
We use Plausible to count visits. It runs on every page of this site.
It records the page viewed, the site or search that sent you, your country, and your device and browser type.
It sets no cookie. It does not follow you across other websites. It does not build a profile that identifies you.
Like any request your browser makes to another server, the request reaches plausible.io carrying your IP address. That is how the internet delivers a reply. What comes back to us is aggregate counts.
LinkedIn's cookies, if you accept
We advertise on LinkedIn. LinkedIn's Insight Tag tells us whether those ads work. It stores identifiers on your device, so it waits for your Accept.
Until you accept, the tag does not load and this site does not contact LinkedIn.
Once you accept, it runs on every page here. It sends LinkedIn the page you are on, the page that sent you, your IP address, your device and browser type and the time.
It can store these on technocenter.io:
li_adsId, an identifier LinkedIn uses to count conversions. It sits in local storage until you clear site data. Where local storage is blocked it is a cookie instead, for 180 days.
li_fat_id, a cookie set when you arrive from a LinkedIn ad, so LinkedIn can connect the visit to the click. 30 days.
li_giant, a cookie LinkedIn uses to count conversions by groups of members. 7 days.
LinkedIn also sets cookies on its own domain, linkedin.com, such as bcookie, lidc and li_sugr. If you are signed in to LinkedIn, they let it match the visit to your account. Those are LinkedIn's cookies. Its cookie policy covers them, and its cookie table lists every one.
We get back totals, never names. LinkedIn removes anything that directly identifies you within seven days and deletes the rest within 180 days.
What the banner does
Worth being straight about this one.
The banner controls one thing: LinkedIn's Insight Tag.
Accept, and the tag loads on this page and every page after it.
Reject, and it never loads. The record of your answer is the only thing stored.
Until you answer, it stays off. Ignoring the banner is not a yes.
Visit counting carries on either way, because it stores nothing on your device.
What needs your consent
The rule most cookie law turns on is whether something is stored on or read from your device. That is the trigger, not the word "cookie".
Storage that is strictly necessary to deliver a page you asked for does not need consent. Your banner answer is in that category, because it exists only to record the answer itself.
Anything beyond that does need consent, and we ask for it properly rather than assume it. That includes advertising or retargeting tags, a chat widget that drops an identifier, embedded video that sets a cookie and any analytics that identifies you rather than counting you.
One of those runs here today: LinkedIn's Insight Tag, an advertising tag. That is why the banner asks.
Other content that loads in your browser
A few pages show small product logos next to names such as Jira, OpenAI and Anthropic. Those images are fetched from cdn.simpleicons.org, svgl.app, cdn.jsdelivr.net and upload.wikimedia.org.
Each of those requests carries your IP address, because that is how the image gets back to you. They are sent with a no-referrer instruction, so the server is not told which page asked for the image. None of them set a cookie for this site.
The WhatsApp button in the corner opens a chat through Meta. Tapping it hands you to Meta under Meta's own terms.
Fonts and assets
Fonts are served from this site, not from a font network. Loading a page here does not tell Google or anyone else which pages you read.
The platform is separate
platform.technocenter.io is a different application. It has to remember that you are signed in, so what it stores in your browser is not the same as what this site stores. Its own notice covers that.
Changing your mind
Two ways.
Use the Change your cookie choice button at the bottom of this page. It clears the saved entry and brings the banner back.
Or clear site data for technocenter.io in your browser settings, which does the same thing along with everything else stored for this site.
If you switch from Accept to Reject, the LinkedIn tag stops loading from the next page you open, and we delete what it stored on technocenter.io.
Cookies on linkedin.com are LinkedIn's to clear, and your browser settings can remove them. If you have a LinkedIn account, your LinkedIn ad settings control whether visits like this one shape the ads you see.
Do Not Track and Global Privacy Control
Some browsers send a Do Not Track or Global Privacy Control signal.
We treat either one as a Reject. If your browser sends one, the LinkedIn tag does not load, whatever you chose on the banner.
We do not sell personal information.
Changes to this notice
The version number and date at the top tell you what you are reading.
If we add anything that stores or reads data on your device, this notice is updated before it goes live, and the banner starts asking about it.
We do not change what runs on the site first and describe it afterwards.
We count visits without cookies. If you accept, LinkedIn also sets cookies so we can measure our LinkedIn ads and show them to past visitors.
Reject and nothing loads from LinkedIn. See our Cookie notice.
