Guardian
Trust & transparency

Privacy notice

How Guardian handles identity, provider connections and the business data your organization authorizes.

Version 1.1 · Effective 22 November 2026

1. Who is responsible

Guardian connects organizations to banking, accounting and document providers through a unified API and Model Context Protocol (MCP) gateway.

Guardian is operated by Crossing the line ehf.

Crossing the line ehf
Registration number: 5205161230
Suðurlandsbraut 10
Reykjavík, Iceland

Privacy and support enquiries: support@smartfiscal.ai

The Guardian operator is responsible for its account administration, service security and business communications. For records connected by an organization, that organization determines the business purpose and permitted users; Guardian processes those records on its instructions, subject to the applicable service and data-processing agreement. A bank or other provider may have its own responsibilities and privacy notice.

2. Information we handle

CategoryExamples and source
Identity and organizationSign-in identifiers and profile information from your identity provider; company name, country, registration identifier and membership role supplied by you or a company registry.
Connection and consentProvider, selected company or bank, environment, resource scopes, consent status and expiry, and credentials or tokens entered through secure connection flows.
Connected business recordsThe selected accounts, transactions, customers, suppliers, invoices or documents returned by your provider. These can include personal data about counterparties.
Pilot enquiriesWork email, company name, country, requested access and any use-case details provided in the form. Guardian stores these with a reference and review status so authorized Sales staff can follow up.
Operation and securityAccess-grant metadata, audit events, synchronization status, alerts, exports, timestamps and technical request information needed to operate and protect the service.

We obtain connected records from the provider you authorize, not directly from every individual mentioned in those records. Your organization is responsible for providing any notices required for its use of those records.

3. Purposes and legal bases

We use identity and account information to supply and administer the service, based on the applicable contract where you are a party, or our legitimate interests in serving your organization. Security monitoring, access control and fraud prevention support our legitimate interests in keeping the service secure. Legal obligations may require particular records to be retained or disclosed.

For connected business records, your organization must establish the appropriate legal basis and instruct Guardian on permitted processing. Provider authorization or bank consent permits the connection; it is not a blanket legal basis for every later use of personal data. Where processing relies on consent, consent may be withdrawn without changing the lawfulness of earlier processing.

4. Stored and pass-through data

Connection settings determine how supported resources are read. In synchronized mode, selected normalized records are stored in Guardian and refreshed according to the connection policy. In pass-through mode, Guardian retrieves and normalizes provider responses for the request without retaining those responses as synchronized business records. Connection metadata, credentials, consent and security/audit records are still needed in either mode.

When an authorized client explicitly requests a supported ledger snapshot, Guardian temporarily stores an encrypted immutable copy of the requested ledger result for consistent pagination, including on pass-through connections. These snapshots expire after 15 minutes; cleanup runs in bounded batches, so physical deletion may follow later. Backup retention still applies. A snapshot does not itself certify ledger completeness or authorize account totals.

Provider secrets are kept in the configured secure credential store, using Azure Key Vault in the hosted environment; the application database holds references rather than raw provider credentials. API/MCP clients receive authorized data, not the provider credentials.

Sandbox and Live connections have separate credentials and data. Guardian fixtures use synthetic records. Provider-hosted sandboxes are separate services and should not be supplied with real data unless their rules and your organization expressly permit it.

5. Providers and authorized applications

Microsoft Azure supplies hosting, database and secure key/secret infrastructure for the current deployment. Your configured identity provider handles sign-in. Connected ERP, banking and document providers process requests needed for the integration. For Enable Banking connections, Enable Banking facilitates the bank authorization and account-information flow under its own terms and privacy notice; the selected bank may also provide a notice.

Your organization can authorize downstream applications and MCP clients, including AI clients, for selected connections and resources. Guardian shares data within those grants. Review each recipient's privacy and retention terms before authorizing it. Revoking a Guardian grant stops subsequent Guardian access; it does not erase copies a recipient already obtained.

We may also disclose information to professional advisers or authorities where necessary for legal obligations, security or legal claims. We do not sell connected business records. This notice does not authorize advertising use of financial records.

6. Location and international transfers

The current hosted Guardian environment runs in Microsoft Azure Sweden Central in the EU. An external provider, identity service or downstream application may process data in other locations. EU hosting alone does not determine where every recipient processes data.

Where we arrange a transfer of personal data outside the EEA, we use an applicable adequacy decision or appropriate safeguards, such as standard contractual clauses, where required by law. Contact us for information about the safeguards applicable to your service. A downstream application selected by your organization is responsible for its own processing; review its locations and safeguards before granting access.

7. Retention and deletion

Stored provider records follow the retention policy selected for the connection. The current default is 90 days since a record's last successful observation; successfully refreshed records can therefore remain available longer than 90 days from their first import. Retention is separate from refresh frequency and maximum acceptable data age.

Identity, membership, consent, audit and security records are retained for as long as needed to administer access, investigate incidents, meet legal obligations or handle claims. Expired or revoked access does not by itself delete every associated record. Backups and copies held by providers or authorized applications have separate lifecycles.

Background alert-history export downloads expire 24 hours after the export request is created; expired exports are removed by background cleanup. Files you download are under your control. The hosted database currently has a seven-day rolling backup window, so a deleted record may remain in a protected backup until that backup expires. Backups are retained for recovery, not ordinary application access.

Account, consent and audit metadata do not expire under the connection-record retention rule. When you request account closure or deletion, we assess which records are still necessary for service administration, security, legal obligations or claims, and delete or anonymize information no longer needed. A legal hold can require particular records to be retained until the matter is resolved. Contact us for your organization’s retention or deletion request; the connection’s 90-day setting is not a promise to delete every category within 90 days.

8. Cookies and browser storage

The Console uses essential sign-in/session cookies and temporary security cookies for authentication and request protection. The current Console session expires after 30 minutes. Your identity provider controls its own sign-in session. User preferences and notification dismissals may be saved against your user account.

The hosted service also uses Azure App Service’s essential ARRAffinity and ARRAffinitySameSite routing cookies to keep requests on the appropriate service instance. These may be set when you view public pages; they are used for service routing, not advertising or analytics.

These public legal pages work without JavaScript and load no advertising tags, analytics scripts or external fonts. Additional non-essential tracking must be disclosed and, where required, obtain consent before it is introduced.

9. Your choices and rights

Depending on applicable law, you may request access, correction, deletion, restriction or portability of personal data, and object to processing based on legitimate interests. These rights can be subject to legal exceptions and proportionate identity verification. We respond within the time required by applicable law and explain any permitted extension or refusal. You can also complain to your competent data-protection authority. In Iceland, this is Persónuvernd; see its complaint guidance. You do not need to contact us first to exercise that right.

For records controlled by your organization, contact its administrator first; Guardian will assist with requests within its role. Use Guardian's connection and Developer access controls to manage authorized access, and the bank/provider's controls where appropriate to withdraw its consent. Do not include passwords, API keys, tokens or financial documents in an initial privacy request.

10. Contact and notice changes

Send privacy questions and requests to support@smartfiscal.ai, or write to Crossing the line ehf at the address above. Please identify the organization and service concerned without sending credentials or unnecessary sensitive records.

Guardian does not itself make automated credit, employment or similar decisions with legal or comparably significant effects about you. Applications authorized by your organization may have different functions and notices.

The effective date and version appear above. Material changes to purposes, recipients or data handling will be explained through an appropriate service notice. A change to this document does not itself expand any connection permission or consent.