Privacy Policy for Sagify US
ezApps Software Inc.
Effective Date: October 18, 2026
ezApps Software Inc. ("ezApps," "we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard information when you use Sagify US (the "Service").
This Policy applies solely to the B2B use of Sagify US and should be read in conjunction with our Terms of Service.
1. Scope of This Policy
Sagify US is a business automation service for merchants that transfers invoice, order and inventory data between Shopify and Sage 50 US, and that can read documents you choose to give it (customer purchase orders, invoices and card statements) and enter them into Sage 50 for you.
Important:
Sagify does not store, retain, cache, or persist any customer, order, invoice, product, vendor or bank statement data on ezApps servers. Commercial transaction data is transferred in real time only, and the documents you ask Sagify to read are processed in memory and discarded.
2. Information We Collect
We collect only minimal operational telemetry data required for:
- Billing
- Security
- Service reliability
Telemetry Data Collected:
- Unique user account ID
- Authentication token (securely stored in hashed form)
- Transaction counts (e.g., invoice and order volume, and the number of vendor payments entered from card statements)
- Timestamps of system actions
We Do Not Collect:
- Customer names
- Customer addresses
- Email addresses of customers
- Payment card numbers
- Shopping cart contents
- Product descriptions
- Tax IDs
- Order values
- Invoice documents
- Bank or card statement contents: balances, transactions, vendor names or amounts
3. How We Use Information
We use telemetry data strictly to:
- Measure usage for billing
- Monitor system performance
- Detect security abuse
- Improve product stability
We never sell, trade, rent, or monetize telemetry data.
Configuration Data (Settings Backup)
Separately from the telemetry described above, Sagify can store a copy of your Sagify configuration so that you can restore it on another computer. This is a different category of information, used for different purposes, so we describe it separately.
A configuration backup contains the settings you have chosen, such as:
- Which Sage 50 general ledger accounts you map orders, taxes, shipping and fees to
- Your tax handling preferences and default tax codes
- The Sage 50 account codes you route different order types to
- Feature toggles and formatting preferences
A configuration backup does not contain any of the items in the "We Do Not Collect" list above, and it does not contain your Sage 50 or Shopify credentials, which never leave your computer. The card accounts you set up for the Banking feature are kept on your computer and are not part of the backup.
We use configuration backups only to:
- Let you restore your setup on a new or additional computer
- Reproduce your configuration when you contact us for support
- Test changes to Sagify against real configurations before we release them, so that an update cannot silently change how your orders are posted
Your configuration is sent to us when you save your settings, and when you choose to upload from this computer after we show you that the settings on another computer differ. Nothing is uploaded before then. We keep a limited number of recent versions per store so that you can roll back, and older versions are discarded. You may ask us to delete your stored configurations at any time using the contact details below.
Documents You Ask Sagify to Read
Some Sagify features read a document for you: a customer purchase order received as a file (Wholesale Orders), an invoice or financial document you want entered, or a credit card statement (Banking). When you give Sagify such a file, it is sent over an encrypted connection to our document-reading service, which passes it to OpenAI's API to extract the fields (dates, amounts, descriptions, account numbers as printed) and returns them to your computer for you to review before anything is entered into Sage 50.
- The file and the extracted contents are processed in memory and are not stored by ezApps. Our service's logs record the request (method, path, account ID and IP address), how long it took and how many lines were read, never the document or anything read from it.
- OpenAI states that data submitted through its API is not used to train its models and may be retained for a limited period (currently up to 30 days) for abuse and misuse monitoring, as described in OpenAI's API data usage policies.
- Nothing is read unless you choose to give Sagify the file. The OpenAI API key is held on our servers and never on your computer.
Banking Feature
The Banking feature turns a card statement into vendor payments in Sage 50. Everything it keeps, the statement's lines, the payments created, the card accounts you set up and the history and trends it shows you, is stored only on the computer where you use it: in Sagify's local database, and, for each statement, a copy of what was read from it, kept for up to 180 days so it can be opened again without being read twice, and removed when you remove the statement from the Banking tab. It is never sent to ezApps and is not shared with your other computers or with other users of your company account; the only thing we receive is the number of payments entered, for billing. Because this data lives on your computer, it is protected by your Windows login and your own backups.
Team Member Accounts
The company account can invite other people in the company to use Sagify with their own login and their own permissions (for example, orders but not banking). For each member we store the email address you invite, the name they give, a hashed password, their permissions, and when they were invited, joined or removed. We send the invitation email through our email provider. A member's activity counts against the company account for billing. When you remove a member, their access ends immediately; their record is kept with the company account so that the address can be invited again, and their own login remains until they ask us to delete it.
4. Data Storage & Retention
- Telemetry data is stored securely on protected servers in the United States.
- Telemetry records are retained no longer than necessary for:
- Billing verification
- Regulatory defense
- Dispute resolution
- Configuration backups are retained as a limited number of recent versions per store; older versions are discarded automatically.
- Documents you ask Sagify to read are not retained by ezApps; see the OpenAI retention described above.
- Banking data is retained only on your own computer, under your control.
- Upon account termination, telemetry data, configuration backups, team member records and processing records are deleted.
5. Data Security
We implement commercially reasonable security measures including:
- Token hashing and password hashing
- Encrypted connections (HTTPS / TLS)
- Role-restricted internal access
- Infrastructure-level firewall protections
- Credentials on your computer protected with Windows Data Protection (DPAPI)
However, no system can be guaranteed 100% secure, and you acknowledge and accept this risk.
6. Third-Party Platforms
Sagify operates by connecting to:
- Shopify APIs
- Sage 50 SDK & APIs
- OpenAI's API, only for the documents you ask Sagify to read
- Our email provider, for account and invitation emails
- Our payment processor, for subscription billing
Your customer, order, invoice, vendor and banking data remains entirely within:
- Shopify
- Sage
- Your own local systems
ezApps does not control, store, or access third-party systems beyond real-time transfer authorization.
7. Legal Basis for Processing
We process telemetry and account data under the following legal bases:
- Performance of a contract (providing the Service)
- Legitimate business interests (billing, system integrity)
Sagify is a commercial B2B system and is not intended for consumer personal use.
We do not sell or share personal information, and we do not use it for targeted advertising. California residents may exercise the rights described in Section 8 through the contact details below; we will not discriminate against anyone for doing so.
8. Your Rights
As a Sagify customer, you have the right to:
- Request access to your telemetry data
- Request correction of account-related records
- Request deletion of your account, your team member records and telemetry data upon termination
Requests may be submitted to: support@ezapps.io
9. Children's Privacy
Sagify is not intended for individuals under the age of 18. We do not knowingly collect personal information from children.
10. International Data Transfers
Your telemetry and account data is processed in the United States, and may be processed in other jurisdictions where our infrastructure providers operate. All data is protected using commercially reasonable safeguards.
11. Data Breach Procedures
In the event of a confirmed security breach affecting telemetry or account data:
- We will investigate immediately
- We will notify affected customers without unreasonable delay
- We will take immediate steps to mitigate further exposure
Because Sagify does not store customer, invoice, order or banking data, breach exposure is strictly limited to telemetry, configuration backups and account records.
12. Policy Updates
We may update this Privacy Policy from time to time.
- Material changes will be communicated via email or on our website
- Continued use of the Service after the effective date constitutes acceptance
13. Contact Information
For all privacy-related questions or requests:
ezApps Software Inc.
support@ezapps.io