Catalog · Security
You never hand us a credential. Microsoft shows you who is asking.
The moment that decides most evaluations is a Global Administrator being asked to let a third party into their tenant. Here is what happens at that moment, what we can do afterwards, and what we cannot tell you yet.
How access is granted
On Microsoft’s page, not on ours.
Access to your tenant is granted through Microsoft’s own admin consent page, using a registered application. Your Global Administrator sees the exact permissions being requested and approves them there.
On that screen Microsoft shows the application’s verified publisher status. Microsoft checks it against its own records, and we do not assert it. That is the point: the reassurance comes from Microsoft’s interface, at the moment you are deciding.
No password is ever requested or held No service account to create No secret to email No form on our site grants anything Consent is recorded, and the connection is only live once Microsoft confirms it
Least privilege
Six permissions. Five of them read-only.
This is Catalog’s full request. The setup screen shows each one with a plain sentence saying why, before you are sent to Microsoft.
Read devices
So a request can be targeted at one of your own managed machines.
Read Intune apps
So your team can publish applications that already exist in Intune.
Read Intune managed devices
So a requester sees only the devices that are actually theirs.
Read all users’ profiles
So an approval step can resolve to the requester’s manager when that step comes up.
Sign in and read the user’s own profile
So people sign in with their Microsoft work account rather than a second password.
Read and write group memberships
This is the one that grants approved access. It adds the person or device to the install group.
What Catalog cannot do, at all
Deploy, alter or remove software Change your device policies or compliance rules Create, disable or delete accounts Read anyone’s mail, files or calendar Change directory roles or grant administrator rights
Payment
Card details never reach our servers.
Entered on Stripe, not on Avyna
Payment is taken on Stripe’s own hosted checkout. There is no page in the product where a card number is typed. No card number, expiry or security code reaches our servers or our database.
Stripe is the financial record
Subscriptions, invoices, retries, refunds, credit notes and tax all run on Stripe. What the product shows you is what Stripe holds, not a figure it calculated on its own.
What we actually store
A reference to your Stripe customer record and payment method: identifiers, nothing more. A breach of our systems exposes no payment data, because we hold none.
Not answered yet
Things we would rather tell you straight.
A security page that answers everything perfectly is usually one that is making things up. These are the questions we get, and where we honestly are on each.
Certifications
We do not hold ISO 27001 or SOC 2 today, and the Data Processing Agreement says so in writing. If your procurement process requires one, tell us early so nobody wastes a month.
Support commitments
Catalog publishes no support hours, response times or uptime figure, and we are not going to imply one. Help requests go through the form in the product and continue by email.
Access is added, never removed
Catalog adds group memberships when a request is approved, and never removes them. Time-limited access and revoking access already granted are not part of the product.
Legal
Legal documents
Avyna Catalog's terms, privacy policy and data processing agreement, published here as they stand today.
Diligence welcome
Send us the questionnaire.
We would rather answer forty questions now than find the blocker in week three.