Insights / Data, Privacy & Security · · 12 min read

Shared infrastructure, separate data

How a group of companies can share technology without building a cross-product user graph. The data boundaries Oryvelon sets for each company, why marketing consent is not product consent, and what every product plans for from day one.

Whenever one organisation runs several products, an uncomfortable question follows close behind: does it combine what it knows about people? For many groups the honest answer is "yes, eventually", because combined data is tempting and the tools to combine it are easy to use.

At Oryvelon the default answer is no. We share infrastructure across our companies. We do not share the people who use them.

This note explains what that means in practice: where the boundaries sit, how they differ between companies, why consent is handled the way it is, and what each product has to plan for before it goes live.

Two very different kinds of sharing

It helps to separate two ideas that often get mixed up.

Sharing infrastructure means using the same standards, tools and practices to run several products: the same approach to deployment, monitoring, security headers, domain management, email authentication, AI model access and cost tracking. Nothing about a customer moves between products. What moves is know-how.

Sharing data means that information about a person collected by one product becomes available to another: a purchase history informing a different product's recommendations, an email address added to another brand's newsletter, a profile enriched with behaviour from elsewhere.

The first makes every company stronger. The second quietly changes the promise each company made to its customers. We do a lot of the first and none of the second by default.

Our default: no cross-product user graph

A "user graph" is the web of connections an organisation builds between accounts, devices, emails and behaviour. Large platforms build enormous ones. For a group like ours, a cross-product graph would mean linking a person's activity in MerchNivo, ZodiVela, KeşifAtlası and so on into a single profile.

We do not build one. Each company keeps its own users in its own database. If the same person signs up for two products, they have two accounts, and nothing in our systems joins them.

Could there be a future case where two specific products benefit from a connection — for example, a merchant who explicitly wants to link their MerchNivo workspace with a store run by our services company? Possibly. If so, it would be designed as an explicit, consented link between two independent systems, visible to the user and reversible. It would not be a background join that nobody asked for.

Boundaries by company

Not every product needs the same boundary. The sensitivity of the data decides how strict the rules are. Here is how it looks today.

Company Data kept separate Special rule
MerchNivo Shopify stores, orders, products, store customers Store-by-store tenant isolation
CastLyra Talent profiles, business briefs, messages Explicit consent and business access rules
EduRelia Student, parent, teacher and school data School tenants, row-level security, child-data minimisation
ZodiVela User profiles, readings, uploads No cross-product profiling
KeşifAtlası Assessments, income bands, family and application details Minimised sensitive data, versioned rules
Noveniq Commerce and order data Independent production business
Sinem Keser Beauty Academy Appointments, students, purchases Independent brand and customer relationship

A few of these deserve more explanation.

MerchNivo: store-by-store isolation

MerchNivo reads data from Shopify stores. That data belongs to each merchant, and it includes information about the merchant's own customers. Every store is a separate tenant: one merchant can never see another's data, and store data is never used for any other Oryvelon product. Even Noveniq, which the group owns and which serves as a real testing environment for MerchNivo, is treated as just another tenant with its own boundary. See Using a real store as a product test-bed.

EduRelia: the strictest standard in the group

EduRelia handles information about children. That puts it at the top of our sensitivity scale. Schools are separate tenants, access is enforced with row-level security in the database rather than only in application code, and the product collects the minimum information needed to support learning. Student data is never used in any consumer product or for marketing. We describe the approach in Child-data minimisation in education technology.

On a talent marketplace, visibility is the product — but it has to be controlled by the talent. CastLyra's rules decide which businesses can see which details, and consent is explicit and recorded. Talent data is never merged with any other Oryvelon product. See Verification as the foundation of a talent marketplace.

KeşifAtlası: minimise what is sensitive

People researching visas and relocation may share income bands, family circumstances and plans. KeşifAtlası collects only what the eligibility rules genuinely need, and assessment data does not flow automatically into marketing profiles of any product.

This is the part of data handling where good intentions most often slip.

When someone signs up to use a product, they agree to that product processing their data to provide the service. That is product consent (or, depending on the legal basis, a contractual necessity). It is specific to the product.

When someone agrees to receive marketing, that is marketing consent. It is a separate decision, and it is also specific: agreeing to hear from ZodiVela about new reading formats is not agreeing to hear from KeşifAtlası about visa reports.

At Oryvelon the two are recorded and handled separately, per company. Using one company's customer list to promote another company is off the table unless the person has explicitly agreed to it. We cover the practicalities in Marketing consent is not product consent.

Shared AI without shared data

AI raises the stakes, because it is easy to accidentally send data to places it should not go.

Every AI feature in the group uses the same kind of gateway for model routing, budgets, logging and fallbacks. But each product has:

  • its own AI project and API keys;
  • its own prompts, owned and versioned by that product;
  • its own knowledge base for retrieval, if it uses one;
  • its own budget and cost reporting;
  • its own logs, filtered for personal information.

The gateway standardises how we call models. It never merges what products send to them. A store summary from MerchNivo and a reading from ZodiVela never share a prompt, a knowledge base or a log. See Retrieval without leakage: private knowledge bases per product and What an AI gateway does.

Analytics without a single identity

We still need to understand how people move between our companies — for example, how many visitors to oryvelon.com go on to visit a company site. We do that with consistent campaign parameters on links between sites, and by looking at aggregated, product-level numbers. We do not stitch individual users together across products. See Analytics without surveillance and UTM standards for measuring traffic between sister brands.

What every product plans for from day one

Boundaries are easiest to build at the start. Before any Oryvelon product goes live, its data plan answers five questions.

  1. Minimum collection. What is the smallest set of data that lets the product work? Everything else is left out until there is a clear reason.
  2. Role-based access. Which roles exist — customer, admin, teacher, parent, business, talent — and what can each one see? Access is defined by roles, not by individual exceptions.
  3. Auditability. Which actions are critical enough to log — changes to permissions, exports, deletions, sensitive views — and where is that log kept?
  4. Retention. How long is each kind of data kept, and what triggers its deletion?
  5. Export and deletion. How does a person get a copy of their data, and how do they have it deleted?

We explain the last two in more depth in Retention, export and deletion.

What this costs us — and why it is worth it

Separate data is not free. It means:

  • separate databases to operate, back up and monitor;
  • separate accounts for people who use more than one product;
  • separate analytics setups;
  • more careful engineering whenever a feature touches personal data;
  • saying no to some marketing ideas that would be easy with combined data.

We accept those costs because the alternative is worse. Combined data creates a single point of failure: one breach, one misconfigured query or one overreaching campaign affects every company at once. It creates regulatory complexity, because each product's legal basis for processing is different. It makes it much harder to ever separate a company from the group. And, most importantly, it changes the relationship each company has with its customers in a way they did not agree to.

How the boundaries are checked over time

Boundaries that are drawn once and never checked tend to erode. A convenient export here, an extra field there, a new vendor that receives more than it needs. So the boundaries are part of our regular operating rhythm rather than a one-off design exercise.

At design time, every new feature that touches personal data answers the five planning questions again: what it collects, who can see it, what is logged, how long it is kept and how it is removed.

At vendor selection, any new tool that will receive personal data is reviewed for what it actually needs. Analytics, email, support and AI providers are configured per company, with the minimum data required.

At access reviews, which happen every quarter, we check who can reach each company's data and remove access that is no longer needed. See Least-privilege access for small teams and contractors.

At incident review, if something goes wrong — a misrouted email, an over-broad export, a log that captured more than it should — the fix includes a change to the standard so the same mistake is harder to make in every company.

This rhythm is not glamorous, but it is what turns a principle into a habit.

Requests we decline, and what we do instead

Principles become clearer when you see the requests they rule out. Here are the kinds of ideas that come up in any multi-brand group, and how we handle them.

"Let's email all our customers about the new product." We do not send one company's customers marketing for another company. Instead, the new product is announced on oryvelon.com, on the founders' own channels and — where it genuinely fits — in the existing product's own communication about its own features. Anyone who has explicitly opted in to hear about the group can be told directly.

"Let's enrich profiles with data from our other apps so recommendations are better." Recommendations in each product use that product's data. If a product needs more information to be useful, it asks the user for it, explains why and lets them decline.

"Let's use one analytics property for everything so we can see the whole funnel." Each company has its own measurement. To understand movement between companies, we use campaign parameters on links and compare aggregated numbers. We do not track individuals across brands.

"Let's train one model on everything we know." Each product's knowledge base, prompts and evaluation data stay with that product. Techniques that work well are shared as documentation; data is not.

"Let's give the support team access to all products so they can help faster." Support access is granted per company and per role. A person helping CastLyra talent does not automatically see EduRelia records. Access is reviewed regularly and removed when it is no longer needed.

Each of these declines has a small cost in convenience. Together they are what makes the group trustworthy.

Five questions before combining any data

Occasionally there may be a genuine case for connecting data between two companies. When that happens, we ask five questions before anything is built.

  1. Did the person clearly ask for it? A connection the user requested and can see is very different from one done in the background.
  2. Is the purpose specific and explained? "Better experience" is not a purpose. "Show your store's sales in your agency report" is.
  3. Is it the minimum data needed? Connecting two systems does not mean copying everything from one to the other.
  4. Can the person undo it? Every connection should be reversible, with data removed when it is.
  5. Would we be comfortable describing it publicly? If we would hesitate to explain it on this website, we should not build it.

If any answer is uncomfortable, the connection is not built.

A note for partners and customers

If you are a business working with one of our companies, the practical implications are simple. Your data is held by that company, under that company's privacy notice, and used to provide the service you signed up for. It is not shared with other Oryvelon companies, and it is not used to market their products to you or your customers.

If you are an individual using one of our products, the same applies. You can ask that company for a copy of your data or for its deletion, and the request concerns that company alone.

A worked example: one person, three companies

Consider a hypothetical person — call her a small business owner — who uses three Oryvelon companies over a year.

She runs a Shopify store and connects it to MerchNivo. Later she books a course at Sinem Keser Beauty Academy. Later still she uses KeşifAtlası to check whether she could move abroad.

Inside the group, those are three customers. MerchNivo holds her store connection inside her store's tenant. The academy holds her booking and payment record. KeşifAtlası holds her assessment answers, including income band and family details, collected only because the eligibility rules need them. Nothing links the three records, and nobody in the group is supposed to know they belong to the same person.

Here is what that means in practice:

  • The KeşifAtlası assessment never informs what MerchNivo suggests, and her store's sales never affect how KeşifAtlası treats her.
  • Unsubscribing from the academy's newsletter changes nothing in the other two, because each consent was given separately.
  • If she asks KeşifAtlası to delete her data, that request is handled by KeşifAtlası. Her MerchNivo workspace is untouched, because it belongs to a different relationship.
  • If one of these companies were ever sold, her records would go with that company only.

That last point is the test we find most useful. If a company cannot be separated without first untangling its customers from everyone else's, the boundary was never real.

Common ways data leaks between products by accident

Few groups decide to merge customer data. Most drift into it through tooling. These are the leaks we design against.

  • One tracking pixel or tag container across brands. A shared advertising or analytics tag quietly builds the cross-brand profile a group said it would not build. Each company has its own tags and properties.
  • One email tool account with one audience list. If every brand's subscribers sit in one list with a "brand" field, one wrong filter sends the wrong people the wrong campaign. Audiences live in separate workspaces.
  • Production data copied into test environments. A realistic test database is tempting, and it is how real customer records end up on a laptop. Test data is synthetic or anonymised. See Local, preview, staging, production.
  • Logs that carry whole payloads. A debug log that stores full AI requests can hold personal information from one product in a place other people can read. Logs are filtered and stay per product.
  • Shared database users. Even with separate tables, a single database user with access to everything removes the boundary where it matters most. Isolation is enforced at the data layer, as described in Tenant isolation explained.

None of these requires bad intent. That is why the standards cover them explicitly.

Summary

Oryvelon exists to share foundations across companies. Data is deliberately not one of those foundations. Each company holds its own users, its own records and its own promises, and the group's job is to make sure those promises are kept — with tenant isolation where it is needed, the strictest standards where children are involved, explicit consent where visibility is the product, and separate handling of marketing permissions everywhere.

Share the plumbing, not the people. It is one of the simplest rules we have and one of the most important.

For how each company applies it, see the Companies page. For the wider operating model, see Build.

Questions and answers

Does Oryvelon combine customer data across its companies?

No. There is no cross-product user graph by default. Each company keeps its own users, database and privacy boundary.

What does Oryvelon share between companies?

Infrastructure and operating standards — deployment, security, monitoring, an AI gateway client and brand-neutral code. Not user data.

Is marketing consent the same as agreeing to use a product?

No. Agreeing to use one product does not mean agreeing to be marketed to by other companies in the group. Oryvelon records and handles the two separately.

NextHow we start a new company: our 10-step protocol →