Security and data handling
Liscaragh Save is a Microsoft 365 add-in, not a hosted service that your email passes through. Your email and files move directly between Outlook and your own SharePoint or OneDrive, using your own sign-in. This page sets out exactly what that means, and the one place Liscaragh's own infrastructure genuinely is involved: your subscription.
This page is written to be handed to a security reviewer or attached to a procurement questionnaire. If you need anything here confirmed in a specific format, get in touch.
Where your email and files go
Liscaragh Save runs as JavaScript inside Outlook itself (New Outlook, Outlook on the web, or classic Outlook for Windows) and inside your browser. When you save an email or attachment, the add-in calls Microsoft Graph directly, using a token issued to you by Microsoft when you sign in. The content of your email or attachment is never uploaded to a Liscaragh server. It goes straight from Microsoft's own infrastructure, Outlook and Microsoft Graph, into the SharePoint or OneDrive location you chose.
Liscaragh Software does operate one small backend service for this product (hosted on Microsoft Azure, at app.liscaragh.com). It handles exactly one thing: checking your tenant's subscription or trial status, and starting or managing billing through Stripe. It is never in the path of a save itself.
What Liscaragh's backend does and does not hold
Holds: your tenant ID and subscription status
To know whether your organisation has an active trial or subscription, Liscaragh's backend stores your Microsoft 365 tenant ID alongside a subscription status and a reference to the matching Stripe customer and subscription. That is what a "licence check" looks up on every launch of the add-in.
Never holds: your email content or files
No email body, attachment, filename or SharePoint content passes through, or is stored by, Liscaragh's infrastructure at any point. There is no path in the code for it to do so.
Never holds: your activity log, by default
Every save and undo is logged, but by default that log is written only to your own device (your browser profile's local storage), never transmitted anywhere. See "The activity log" below for the one optional exception, which still keeps the data inside your own tenant, not Liscaragh's.
Never sees your Microsoft 365 password
Sign-in uses Microsoft's own identity platform (the same sign-in flow as any other Microsoft add-in). Liscaragh Save receives a token proving who you are and what you're allowed to do; your credentials themselves are never visible to the add-in or to Liscaragh.
Permissions requested, and why
A tenant admin consents to these permissions once, for the whole organisation. Every one of them is a Microsoft Graph delegated permission, meaning the add-in can only ever act as the signed-in user, within whatever that user is already allowed to do, never with standing access of its own.
- User.Read
- Confirms who is signed in. Used to identify the user for the save flow and settings; nothing more.
- Mail.Read
- Reads the currently open email so it can be saved as a file. The add-in only ever reads the message you have open; it does not scan your mailbox.
- Mail.Read.Shared
- The same read access, extended to shared and delegated mailboxes you already have access to in Outlook, so the add-in works from those mailboxes too.
- Files.ReadWrite.All
- Writes the saved email or attachment into the SharePoint library or OneDrive folder you choose. This is the highest-privilege permission the add-in asks for, which is exactly why a tenant admin has to consent to it once before anyone can use the add-in; see installing Liscaragh Save.
- Sites.Read.All
- Lets the destination picker search for a SharePoint site by name. Without it, the add-in could still save to a site it already knows the address of, but the "search for a site" step in the picker would not work.
The activity log
Every save and undo is logged: who did it, what kind of item, the subject and sender, the filename, the source mailbox, the destination, when, and whether it succeeded. Deliberately, none of that lives on Liscaragh's own infrastructure by default.
- Default: local to the device. The log is written to this browser profile's local storage on your own device. It never leaves the device, and Liscaragh has no access to it. The trade-off is that it is per device and per browser profile: the same person on two machines has two separate histories that do not merge.
- Optional: also written inside your own tenant. In Settings, you can point the log at a SharePoint site and library in your own tenant. Once set, every save and undo is also appended to a daily file there, using the same
Files.ReadWrite.Allpermission already consented to, no new permission and no new consent prompt. This is genuinely inside your own tenant and data residency boundary, not Liscaragh's.
Either way, the CSV export in Settings reads from whichever of the above you have enabled, so you can see and share your own tenant's activity without needing anything from us.
What we can and cannot see
Because the actual save never routes through Liscaragh's infrastructure, we cannot see your email content, your files, or your SharePoint structure. What we can see is limited to your tenant ID, your subscription status, and (only if you choose to email us) whatever you tell us directly when contacting support.
Removing it
Removal is a single step for a tenant admin: Microsoft 365 admin centre, Integrated apps, select Liscaragh Save, Remove. This is reversible and does not touch mail flow. Any locally stored activity log data on individual devices is unaffected either way, since it was never Liscaragh's to remove.