Memahami kepatuhan

Pengungkapan regulasi

1. 1BankSync accesses Australian CDR data as a CDR Representative of Fiskil Pty Ltd (CDR Registration ADRBNK000246) under CDR Rule 1.10AA. BankSync holds no CDR accreditation of its own; Fiskil acts as our CDR Principal and collects and discloses CDR data on our behalf under Fiskil's CDR Policy, which BankSync adopts.
2. 2Fiskil Pty Ltd is listed on the ACCC's public CDR Register as an Accredited Data Recipient (ADRBNK000246). CDR Representatives are disclosed under their Principal's accreditation rather than holding a separate register entry.
3. 3Consent is collected through Fiskil's hosted consent screen. Maximum consent duration is 12 months (CDR Rule 4.14). You receive advance notice before expiry.
4. 4CDR data is used to provide the service you request. Within the BankSync Boundary, BankSync does not sell CDR data, use it for advertising or data brokerage, disclose identifiable CDR data for another party's independent commercial exploitation, or use customer CDR data to train AI or machine-learning models.
5. 5Financial data obtained under CDR is pass-through by default. It is stored only where you enable a BankSync-managed feature that requires storage, such as future BankSync Tables, or where needed for support, security, compliance, backups, or legal requirements.
6. 6Upon account deletion or consent revocation, all active CDR consents are immediately withdrawn and connection data is queued for deletion.
7. 7CDR complaints can be directed to Fiskil Pty Ltd or to the Australian Financial Complaints Authority (AFCA) and the Office of the Australian Information Commissioner (OAIC). Applicable laws include the Privacy Act 1988 (Cth), Competition and Consumer Act 2010 (Cth), and the Consumer Data Right Rules.

Pengungkapan regulasi

1. 1BankSync does not hold its own FCA authorisation or registration. UK Open Banking access is provided through Salt Edge Limited, a Registered Account Information Service Provider (RAISP) authorised by the Financial Conduct Authority (FCA FRN 822499, Companies House 11178811, 71–75 Shelton Street, London WC2H 9JQ).
2. 2BankSync accesses UK bank data under a data-sharing arrangement with Salt Edge Limited. Salt Edge Limited bears regulatory responsibility to the FCA for UK Open Banking data access.
3. 3Data accessed via Salt Edge is used to provide the service you request. Within the BankSync Boundary, BankSync does not sell your banking data, use it for advertising or data brokerage, disclose identifiable banking data for another party's independent commercial exploitation, or use customer banking data to train AI or machine-learning models.
4. 4Financial data obtained via UK Open Banking is pass-through by default. It is stored only where you enable a BankSync-managed feature that requires storage, such as future BankSync Tables, or where needed for support, security, compliance, backups, or legal requirements.
5. 5Salt Edge Limited and BankSync act as joint data controllers at the point of data sharing under UK GDPR. BankSync becomes the sole data controller once data has been received and forwarded to your connected destination.
6. 6You may revoke Open Banking consent at any time through your bank's consent dashboard or by contacting BankSync support.

Pengungkapan regulasi

1. 1US and Canadian bank connections are facilitated through Plaid Technologies, Inc., a CFPB-registered financial data aggregator operating under CFPB Section 1033 rules and bilateral data-sharing agreements with financial institutions.
2. 2BankSync does not store banking credentials. Authentication is handled directly between Plaid and your financial institution using tokenised connections.
3. 3Data accessed via Plaid is used to provide the service you request. Within the BankSync Boundary, BankSync does not sell your banking data, use it for advertising or data brokerage, disclose identifiable banking data for another party's independent commercial exploitation, or use customer banking data to train AI or machine-learning models.
4. 4Financial data obtained via Plaid is pass-through by default. It is stored only where you enable a BankSync-managed feature that requires storage, such as future BankSync Tables, or where needed for support, security, compliance, backups, or legal requirements.
5. 5You may revoke Plaid access at any time via the Plaid Portal (my.plaid.com) or by disconnecting the bank from within BankSync.

Pengungkapan regulasi

1. 1US bank connections through this provider are facilitated by Quiltt, Inc., a financial data platform, with MX Technologies, Inc. connecting to your financial institution under CFPB Section 1033 rules and its own data-access agreements with financial institutions.
2. 2BankSync does not store banking credentials. Authentication is handled between MX, Quiltt and your financial institution using tokenised connections.
3. 3Data accessed via Quiltt is used to provide the service you request. Within the BankSync Boundary, BankSync does not sell your banking data, use it for advertising or data brokerage, disclose identifiable banking data for another party's independent commercial exploitation, or use customer banking data to train AI or machine-learning models. Quiltt, MX and other independent providers may have their own terms and legal obligations.
4. 4Financial data obtained via Quiltt is pass-through by default. It is stored only where you enable a BankSync-managed feature that requires storage, such as BankSync Tables, or where needed for support, security, compliance, backups, or legal requirements.
5. 5BankSync makes its server-side calls to Quiltt from BankSync infrastructure in the United States (Google Cloud, us-central1). Quiltt requires this for CFPB Section 1033 data residency, and our production deployment refuses to start Quiltt without it.
6. 6You may revoke access at any time by disconnecting the bank from within BankSync.

Pengungkapan regulasi

1. 1US bank connections through this provider are facilitated by Quiltt, Inc., a financial data platform, with Finicity Corporation (a Mastercard company) connecting to your financial institution under CFPB Section 1033 rules and its own data-access agreements with financial institutions.
2. 2BankSync does not store banking credentials. Authentication is handled between Finicity, Quiltt and your financial institution using tokenised connections.
3. 3Data accessed via Quiltt is used to provide the service you request. Within the BankSync Boundary, BankSync does not sell your banking data, use it for advertising or data brokerage, disclose identifiable banking data for another party's independent commercial exploitation, or use customer banking data to train AI or machine-learning models. Quiltt, Finicity and other independent providers may have their own terms and legal obligations.
4. 4Financial data obtained via Quiltt is pass-through by default. It is stored only where you enable a BankSync-managed feature that requires storage, such as BankSync Tables, or where needed for support, security, compliance, backups, or legal requirements.
5. 5BankSync makes its server-side calls to Quiltt from BankSync infrastructure in the United States (Google Cloud, us-central1). Quiltt requires this for CFPB Section 1033 data residency, and our production deployment refuses to start Quiltt without it.
6. 6You may revoke access at any time by disconnecting the bank from within BankSync.

Pengungkapan regulasi

1. 1Investment portfolio and brokerage data is provided via SnapTrade, a financial data aggregator with direct API partnerships with US and Canadian brokerage providers.
2. 2BankSync does not store brokerage credentials. Authentication is handled directly by SnapTrade and your brokerage.
3. 3Investment data accessed via SnapTrade is used to provide the service you request. Within the BankSync Boundary, BankSync does not sell your investment data, use it for advertising or data brokerage, disclose identifiable investment data for another party's independent commercial exploitation, or use customer investment data to train AI or machine-learning models.
4. 4Investment data is pass-through by default. It is stored only where you enable a BankSync-managed feature that requires storage, such as future BankSync Tables, or where needed for support, security, compliance, backups, or legal requirements.