Privacy Policy for ZentraSnap
Introduction
ZentraSnap (“we”, “us”, “our”) operates the ZentraSnap application, a document extraction, file-storage and client-communication service for professionals, businesses and their clients, including accounting, bookkeeping, tax and other authorised financial-document work.
ZentraSnap processes financial documents using different technical pipelines depending on the type of document submitted. Bank statements are processed using ZentraSnap's own document-extraction technology running on cloud computing infrastructure, while invoices and receipts submitted for extraction are processed using the Google Gemini API. Clients and paid Professional accounts can also upload and organise their own documents in Files. Paid Professional accounts can retain completed extraction results in Recent extractions.
Because these documents may contain personal and confidential financial information, we seek to minimise the amount of data retained, restrict access to processing infrastructure and use service providers that provide appropriate security and data-protection safeguards.
Client Portal: accounts, sharing and communications
Account types and access. Professional accounts support accounting, bookkeeping, tax, lending, financial advice and other authorised document work. Professional is an account label, not a certification of identity, qualifications or regulatory status. Professional accounts may use bank-statement, legacy reconciliation and invoice/receipt extraction with available credits without a paid subscription. An active paid Professional subscription is required for Client Portal features and new Professional file storage. Each Professional account can have up to 20 clients, including pending access requests. Cancelled, declined, expired, revoked, blocked or removed connections do not use a client slot. Client accounts are free, have a separate 1 GB (1,000,000,000-byte) total allowance and do not include extraction tools. Pending uploads and items in Trash count towards the allowance.
Access requests. A paid Professional can request access to an existing Client account using its email address. ZentraSnap does not provide a public client directory. The client is shown the requesting professional’s name, contact email and practice name where available. Access requires acceptance while signed in to the intended Client account; receiving or opening an email alone grants no access. Requests expire after seven days and may be cancelled or declined. Clients can block further requests and later unblock the professional. Unblocking does not itself restore access.
What approval shares. Approval covers all existing and future files in the client workspace, rather than only an individual folder. Multiple named professionals may be approved separately. Approved professionals with active paid access can browse folders, search, preview, download files and folder ZIPs, and extract supported documents. They cannot upload into, rename, move or delete the client’s originals. They can see available client profile information: name, email address, profile picture, selected country, contact phone number and last sign-in date. Profile information is supplied by the account or authentication provider and may be incomplete. Clients should approve only intended recipients; professionals must use shared information only for authorised purposes and protect copies they obtain.
Working copies and revocation. Extracting a client document uses the professional’s credits. Working copies and results are held in the professional’s workspace under its storage and retention rules and are not automatically shared back with the client. Clients can revoke access; this blocks subsequent authorised retrieval through ZentraSnap. Subscription expiry also suspends the professional’s shared-client access and ability to send new requests. Neither action can recall information already loaded in a browser, downloaded, emailed or copied into a professional’s workspace. Removing a client from a professional’s list ends that connection and clears that professional’s notes; it does not delete the client’s account or originals. These service-access rules do not transfer ownership of documents or determine either party’s data-protection role.
Professional notes. Professionals can save up to 500 characters of notes in a client profile. Notes are stored in the service and are not shown to the client or other professionals through the ordinary interface. They may contain personal data and remain subject to applicable access, correction and deletion rights. The professional should include only information necessary for the authorised work. Revoking access does not itself erase the notes; removing the client from that professional’s list or deleting either participating account clears those notes from active records. Applicable recovery-history rules still apply.
Email requests. An approved paid Professional can send a general or document request from the client profile, with a required title and message and an optional due date. The subject identifies the professional by name or email and includes the request title; the message and any due date are included in the email body. Replies are directed to the professional’s contact email and are handled by the parties’ email providers, not stored as new conversations in ZentraSnap. The form does not attach original documents. A queued request is not proof of delivery or that the client has read it. The sender is responsible for the recipient, message contents and lawful use of the email facility. Service emails must not be used for unsolicited marketing or harassment.
Notifications and delivery providers. Access requests and other supported account events may generate in-app notices and service emails. Opening the notification panel marks the listed notices as read; this does not establish that the underlying request has been completed. Resend (Plus Five Five, Inc.) delivers these emails and processes sender and recipient addresses, sender identity, subject, message body, optional due date, invitation or service links and delivery information as needed. Personal or financial information entered into a request is included in the email sent to Resend and the recipient’s mail provider. See Resend’s data-processing terms. EU document storage does not mean that authentication or email processing takes place exclusively in the EU.
Portal records and retention. ZentraSnap processes account type, country, contact details, email-verification status, access requests and decisions, notes, request-delivery records, notifications and limited security events. In-app notifications are scheduled for deletion after 90 days, email-queue and delivery records after 30 days, and portal audit events after one year. Cleanup is asynchronous. Queued email contents are encrypted server-side and cleared following successful delivery or cancellation of the queued request; an undelivered payload can remain until queue cleanup. Invitation tokens are stored as hashes. Access-relationship and blocking records remain as needed to operate the relationship and honour access decisions, subject to account deletion and valid deletion requests.
Deletion and retained copies. Account deletion revokes relationships, clears the deleted account’s profile and relevant notes from active portal records, and initiates file cleanup. Historical in-app communications, if present from earlier versions, remain subject to their existing access and deletion rules; account deletion removes the deleted user’s authored reply text and attachment references. Other participants may retain their own records. Emails already delivered and downloaded or independently retained working copies cannot be recalled through account deletion. The separate retention rules for Files, Recent extractions, infrastructure recovery history, legal records and email providers continue to apply.
Data-protection responsibilities. Account types do not determine the parties’ legal roles. ZentraSnap acts as controller for account administration, security and service-operation information as described in the Privacy Policy. Providing the requested account and sharing functions relies on performance of the relevant service contract where applicable; proportionate security and abuse prevention rely on legitimate interests, and mandatory records on legal obligations. Where ZentraSnap processes documents, professional notes or request contents on a customer’s behalf, the DPA applies. A client’s approval is an access instruction, not a substitute for the lawful basis, authority or privacy notices needed for the parties’ processing. Professionals remain responsible for their subsequent use of shared information.
1. Who We Are
ZentraSnap is operated by Cristin Griu, trading as ZentraSnap, operating in Celbridge, Co. Kildare, Ireland.
For questions concerning this Privacy Policy, data protection or our security practices, contact:
2. Data Protection Roles and Customer Responsibilities
ZentraSnap acts as a Data Controller in relation to personal information used to create and administer your ZentraSnap account, manage subscriptions, provide customer support, secure the service and operate our business.
Where you submit bank statements, invoices, receipts, spreadsheets, text files or other supported business documents relating to your clients or other third parties, you or the organisation on whose behalf you use ZentraSnap normally determines why that data is being processed.
In those circumstances, ZentraSnap acts as a Data Processor, or where appropriate a sub-processor, and processes the document contents and associated identifying metadata only for the purpose of providing the ZentraSnap service and in accordance with the customer's instructions and our Data Processing Agreement.
You are responsible for ensuring that you have an appropriate lawful basis, authority and any required notices or permissions to process and submit personal data to ZentraSnap. This does not necessarily require consent; the appropriate legal basis depends on the circumstances and is the responsibility of the relevant Data Controller.
You are responsible for maintaining appropriate security for the computer, browser, network and working environment from which you access ZentraSnap.
3. Document Extraction and File Storage
3.1 Bank Statements
- ●When a bank statement is submitted for extraction, a processing copy is temporarily uploaded to private object storage provided by Cloudflare R2.
- ●Where a user uploads a JPG, JPEG, PNG or WebP image of a bank statement, ZentraSnap may first convert the image into PDF format locally within the user's browser before uploading it for processing.
- ●Bank statements are then processed using cloud computing infrastructure provided by Modal Labs. Processing may include native PDF text extraction and ZentraSnap's trained document-extraction models.
- ●Where a bank statement is image-based, scanned, does not contain usable native text, or where the initial extraction does not identify transaction data, ZentraSnap may use Microsoft Azure AI Document Intelligence as an OCR service. In these circumstances, the relevant document or page is transmitted to Microsoft Azure for text recognition and document-coordinate extraction before the recognised text is processed by ZentraSnap's document-extraction model.
- ●Microsoft Azure Document Intelligence temporarily stores submitted input data and analysis results in Azure Storage in the same Azure region as the request. Microsoft currently states that this information is automatically deleted after 24 hours. ZentraSnap may also request deletion of analysis results earlier where supported by the service.
- ●The processing system extracts structured transaction information such as transaction dates, descriptions, debit amounts, credit amounts and balances. Document-coordinate information may also be generated to enable features such as locating an extracted transaction within the source document.
- ●Temporary job-status information and extracted results may be stored in Cloudflare R2 while the extraction is being processed and delivered to the user.
- ●The bank-statement processing copy is normally deleted from temporary R2 storage after processing completes or fails. Automated storage-lifecycle controls provide a secondary cleanup mechanism. This does not delete copies retained in Files or Recent extractions, which follow section 9.
- ●Modal may retain limited technical information associated with function execution in accordance with Modal's own published retention policies.
- ●ZentraSnap does not use customer documents or saved extraction data to train its own machine-learning models without separate express agreement.
3.2 Invoices and Receipts
- ●When you use ZentraSnap's invoice or receipt extraction functionality, the document or image submitted for extraction is transmitted to Google's paid Gemini API.
- ●Google processes the document to return structured information such as supplier details, invoice numbers, dates, totals, tax information and line items.
- ●ZentraSnap uses the paid tier of the Gemini API. Under Google's applicable terms for paid Gemini API services, customer prompts and responses are not used to improve Google's products by default.
- ●Where Gemini API project logging is enabled, request and response logs may be retained within the relevant Google AI Studio project. Google currently allows project logging retention periods of 7, 14, 28 or 55 days, with a default maximum retention period of 55 days. Google may separately process limited information for security, abuse-prevention and legal-compliance purposes in accordance with its applicable terms and policies.
- ●ZentraSnap does not intentionally contribute customer financial documents, API logs or datasets to Google for model training or product improvement.
3.3 Files and Recent extractions
Files lets Clients and customers with paid Professional storage access upload supported documents, create nested folders, rename, move, pin, preview, download and delete items. Recent extractions can retain completed results and their source documents so they can be reopened in the matching review tool, subject to storage limits and successful saving.
Cloudflare R2 stores document contents and extracted-data files. A separate Cloudflare D1 database stores account ownership, file and folder names, parent-folder relationships, sizes, file types, timestamps, deletion and expiry information, extraction references and pinned-folder preferences. Names and folder structures may themselves contain personal data. The existing files database also stores portal account details, access relationships and decisions, professional notes, notification records, encrypted email-queue payloads and audit events.
Uploading a document to Files does not initiate AI extraction, send it to Gemini, Modal or Azure for extraction, or consume extraction credits. Previews retrieve the document for display in the browser; supported spreadsheet and text previews are processed in the browser without sending the document to an external office-preview service. Loading files or a folder into an extraction tool prepares the documents locally; extraction begins when the professional starts processing. That operation invokes the relevant processing route described above.
4. Information We Process
ZentraSnap may process account information such as your first and last name, email addresses and verification status, profile picture, available contact phone number, user identifier, selected account type and country, optional business or practice name, authentication information, last sign-in date, subscription status and account preferences. Where applicable, we also process billing and transaction information necessary to manage subscriptions. Payment-card information is processed by the relevant payment provider and is not stored directly by ZentraSnap.
ZentraSnap also processes and stores limited service-usage and credit-accounting information associated with your account. This may include your Clerk user identifier, subscription status, billing-cycle identifiers and dates, current credit balance, credits used, document and page counts, OCR page counts, invoice and receipt counts, extracted transaction counts, usage-event or job identifiers, processing status and relevant timestamps.
This service-usage information is used to administer the ZentraSnap service, apply usage allowances, prevent abuse, investigate billing or technical issues, maintain account statistics and produce aggregate service-usage statistics.
ZentraSnap's usage-accounting database is not intended to store the contents of customer financial documents. In particular, it does not store transaction descriptions, bank balances, transaction amounts, bank-account numbers, uploaded document filenames, invoice contents or receipt contents as part of credit and usage accounting. File contents are stored separately in R2, and identifying filenames, folder information and other file metadata are stored in the files database described in section 3.3.
When you use document extraction or store documents, the information processed may include:
- Bank statements, invoices, receipts and other supported documents
- Document images
- Account-holder or customer names
- Account identifiers & IBANs
- Transaction dates and descriptions
- Debit and credit amounts, and balances
- Supplier details and invoice numbers
- Addresses, tax information, and line items
- Client profile and access-permission information
- Professional notes and request messages, titles and due dates
- Notification, email-delivery and portal audit records
Documents may incidentally contain additional personal or sensitive information. ZentraSnap processes such information as part of providing the requested document, storage, sharing and communication services. We may also process limited technical information such as application requests, security events, rate-limiting identifiers, browser/device information and service diagnostics where necessary to operate and secure the service. If you contact us for support, we process the information that you provide as part of that communication.
If you create or access an account using a third-party identity provider such as Google, the authentication provider may provide ZentraSnap or our authentication provider with basic account information such as your name, email address and profile image for the purpose of creating, authenticating and managing your account.
5. How We Use Personal Data
We use Account Data and Service Usage Data to provide and administer ZentraSnap, authenticate users, manage subscriptions and billing, administer credit and storage allowances, record service usage, enforce applicable usage limits, provide customer support, maintain security, prevent fraud and abuse, diagnose technical problems, maintain account and aggregate usage statistics and improve the operation and reliability of the service.
Client Financial Data is processed on the customer’s instructions to provide extraction, authorised client sharing, request communications and file-storage functionality: receiving and storing documents, organising folders, saving and reopening results, generating previews, enabling downloads, restoring or deleting items, and maintaining access controls. Text extraction, OCR and AI analysis are performed when the customer uses the relevant extraction tool. Document contents and identifying file metadata are not used for advertising profiles.
ZentraSnap does not sell Client Financial Data.
ZentraSnap does not use advertising cookies or tracking pixels to track users across unrelated websites. Strictly necessary cookies and similar technologies may be used for authentication, security, subscription management and other functionality required to provide the service. Dashboard preferences may be kept in browser storage, and file metadata and previews may be temporarily cached in browser memory to reduce repeated loading. Such caching is not a permanent archive and does not grant access to another account. These may be provided by services such as Clerk.
ZentraSnap uses Vercel Web Analytics to understand aggregate website usage and improve the performance and reliability of the service. We do not use Google Analytics for behavioural advertising or cross-site advertising tracking.
6. Legal Bases for Processing
Our legal bases may include performance of a contract where processing is required to provide the ZentraSnap service, legitimate interests in operating, securing, supporting and improving the service, and compliance with legal obligations where applicable.
ZentraSnap does not independently determine the customer's lawful basis for processing that data. Instead, we process the data on the customer's documented instructions and subject to our Data Processing Agreement. The customer or relevant Data Controller is responsible for establishing the appropriate lawful basis under applicable data-protection law.
7. Third-Party Service Providers and Subprocessors
ZentraSnap uses a limited number of third-party service providers to operate the service. These providers are permitted to process personal data only as necessary to provide their relevant services, subject to their applicable contracts, data-processing terms and legal obligations:
Provides authentication, user-account management and subscription functionality.
Processes payments used through Clerk Billing. Clerk currently uses Stripe for payment processing. ZentraSnap does not directly store full payment-card numbers.
Provides hosting, server-side application infrastructure and website analytics. Authenticated file-management requests and document downloads may pass through its application routes.
Cloudflare R2 provides private object storage for saved documents, retained extraction results and temporary processing copies. Cloudflare Workers provide the storage API, upload/download handling and scheduled cleanup. A separate Cloudflare D1 files database stores ownership and file-management metadata. The existing D1 usage-accounting database continues to store limited credit, subscription and service-usage records, separately from stored document contents.
Provides cloud computing and GPU infrastructure used to process bank statements using ZentraSnap's document-extraction and OCR systems. Modal publishes a Data Processing Addendum and security safeguards for processing customer personal data.
Used to process invoices and receipts and, where enabled, provide API project logging and operational monitoring.
Provides Document Intelligence OCR when needed for bank-statement extraction, processing submitted pages and returning recognised text and document coordinates.
Delivers transactional notices and professional-to-client request emails. This includes recipient and sender contact details, subject, message contents, optional due date, invitation or service links and delivery information. Request emails are not limited to generic alerts: information typed into the message is sent to the provider and recipient. See Resend’s data-processing terms.
Used for API rate limiting and abuse prevention and may process limited technical identifiers required for that purpose. Upstash publishes a Data Processing Addendum covering processing of customer personal data.
8. Storage Location and International Data Transfers
Files and Recent extractions use private Cloudflare R2 buckets configured for the European Union jurisdiction and a separate EU-jurisdiction Cloudflare D1 database for file metadata. These storage settings do not mean that every application operation, support activity or extraction provider is confined to the EU. Processing copies and other providers follow their own applicable locations and transfer safeguards.
Some of ZentraSnap's service providers operate infrastructure or personnel outside Ireland or the European Economic Area. Where personal data is transferred internationally, ZentraSnap relies on appropriate safeguards required by applicable data-protection law, which may include European Commission adequacy decisions, the EU-U.S. Data Privacy Framework where applicable, Standard Contractual Clauses or other legally recognised transfer mechanisms.
Resend’s data-processing terms provide for applicable international-transfer safeguards for email processing. Copies in recipients’ mailboxes are also subject to their email providers’ terms and retention. Cloudflare's current DPA expressly covers situations in which it acts as a processor or sub-processor and contains provisions governing transfers from the EEA. Modal also provides a GDPR Data Processing Addendum addressing international transfers and subprocessors.
9. Data Retention
| Data | Retention |
|---|---|
| Files | Saved documents, folder information and saved extraction data remain available until deleted by the customer, account deletion, or return/deletion at the end of the processing relationship. Subscription expiry alone does not currently start an automatic deletion countdown. |
| Recent extractions | For paid accounts, completed extractions can be retained with their original documents and extracted data within a separate 250 MB allowance. Access expires 48 hours after the temporary entry is created. Editing or reopening it does not extend that period. Saving it to Files before expiry moves it under the saved-file retention rules. |
| Trash | Deleted saved files and folders move to Trash for up to 30 days. They can be restored during that period by a Client account or an account with paid Professional storage access, or permanently deleted earlier. A folder deletion includes its contents. Items in Trash continue to count towards the storage allowance until removed. |
| Deleted recent extractions | Temporary extractions bypass Trash. Deleting one removes access and requests removal of its retained originals and results. |
| Account deletion | Account deletion revokes access and triggers deletion of saved files, retained extractions and associated file metadata. Export anything you need before deleting the account. A minimal revoked-account identifier may remain to prevent stale requests from restoring access. |
| Client accounts | Clients have a free 1 GB (1,000,000,000-byte) allowance for saved files, including pending uploads and items in Trash. Client originals follow the saved-file and Trash rules. Client accounts have no retained extraction history. |
| Free Professional accounts | Free Professional accounts can extract documents using available credits without a paid subscription, but have no allowance for new saved files or retained extraction history. Results can be exported from the current browser session. Temporary copies needed to process documents and deliver results, and processing-provider retention, still apply. Former subscribers may retrieve or delete existing saved items as explained below. |
When paid access ends. For Professionals, new uploads and changes to stored data require paid storage access. Clients retain their separate free allowance; an expired professional subscription suspends that professional’s access to client data. An account without a current paid entitlement can still download or delete its existing saved items, subject to account security restrictions. Contact cristingriu25@gmail.com to arrange return or deletion of remaining data when ending the processing relationship. Subscription cancellation is separate from account deletion.
Deletion timing. Expiry and deletion first remove access through the service. Scheduled cleanup then removes the underlying objects and associated file metadata. Physical removal is asynchronous and can take longer during retries or service disruption. Temporary storage lifecycle rules provide an additional cleanup safeguard. Abandoned uploads and superseded extraction-result copies are also scheduled for cleanup; saved extraction revisions are not a customer-accessible version archive.
Recovery history. Deleted file metadata may remain in Cloudflare D1 recovery history until it ages out of the applicable recovery window, currently up to 30 days. This is separate from document contents in R2 and does not provide a customer file-recovery guarantee. Recovery history is restricted to authorised recovery operations, not ordinary account access. If used for recovery, applicable deletion instructions must be reapplied before restored data is made available. See Cloudflare’s recovery documentation.
These rules apply to Files and Recent extractions. Extraction-processing copies, provider security logs and account, billing and legal records have the separate retention rules described in the Privacy Policy and DPA. Retention required by law is limited to the relevant data and purpose.
Account information is retained while your ZentraSnap account remains active and for such additional periods as may be reasonably required for security, fraud prevention, dispute resolution, accounting, taxation or compliance with legal obligations. Where an account is deleted, account information will be deleted or anonymised from active systems where appropriate, subject to legitimate legal, security, backup and service-provider retention requirements.
Limited usage and credit-accounting records may be retained while your ZentraSnap account remains active and for such additional periods as are reasonably necessary to administer the service, investigate billing or usage disputes, prevent fraud or abuse, maintain security, satisfy accounting or taxation requirements and comply with legal obligations.
These records may include usage totals, credit balances, billing-cycle information, document and page counts, transaction counts, usage-event status and timestamps. Aggregate or anonymised statistics that no longer identify an individual may be retained for longer periods for business, operational and statistical purposes.
Temporary processing copies of original bank-statement documents uploaded to Cloudflare R2 are deleted by ZentraSnap's processing system after the extraction job completes or fails.
As an additional safeguard, temporary bank-statement files, extraction results, job-status information and related processing data stored in Cloudflare R2 are subject to an automated lifecycle rule configured to expire those objects after one day. This lifecycle rule acts as a secondary deletion mechanism in case processing copies are not removed earlier by the normal workflow. It does not apply to saved Files or replace the separate Recent extractions window.
Documents submitted for invoice or receipt extraction are processed using the paid Gemini API. If Gemini API project logging is enabled, request and response logs may be retained according to the retention setting configured for the project. Google's current available project-log retention settings are 7, 14, 28 or 55 days. Separate security and abuse-prevention information may be retained by Google in accordance with its applicable policies.
Support correspondence and business or billing records may be retained for as long as reasonably necessary to respond to requests, resolve disputes and comply with legal, accounting or taxation obligations.
10. Security
ZentraSnap uses technical and organisational measures intended to protect information processed through the service. Data transmitted between users and ZentraSnap's service providers is protected using encrypted HTTPS/TLS connections where supported.
Saved files, retained extractions and bank-statement processing copies are stored in private Cloudflare R2 storage. Storage buckets are not public document repositories. Cloudflare R2 automatically encrypts stored objects using AES-256 encryption. Modal states that user data processed through its infrastructure is encrypted in transit and at rest.
Access to account-specific usage and credit information is linked to the authenticated ZentraSnap account. Communication between ZentraSnap's server-side application and the private usage-accounting service is protected using server-side credentials that are not intentionally exposed to browser code.
File operations use authenticated account ownership checks, including checks on both folders when moving items. Upload permissions and folder-download authorisations are scoped and time-limited; ordinary previews and file downloads use authenticated routes. A person who obtains a valid temporary download URL may use it until it expires, so such URLs should be kept confidential. The service does not provide public sharing of stored folders.
ZentraSnap relies on Clerk for authentication and does not store user passwords directly. Payment-card details are processed by Stripe through Clerk Billing and are not stored directly by ZentraSnap.
No internet-based service can guarantee absolute security, but we take reasonable measures intended to minimise unauthorised access, disclosure, alteration or loss.
11. Your Data Protection Rights
Under the General Data Protection Regulation and other applicable data-protection laws, individuals may have rights including access, rectification, erasure, restriction of processing, objection and data portability, depending on the circumstances.
For requests concerning your ZentraSnap account or information for which ZentraSnap acts as Data Controller, contact us at cristingriu25@gmail.com.
Where a request concerns Client Financial Data processed by ZentraSnap on behalf of an accountant, bookkeeping firm or other customer, the relevant customer will normally be the Data Controller. Individuals should normally direct such requests to that organisation. ZentraSnap will provide reasonable assistance to our customers in responding to valid data-subject requests as required under our Data Processing Agreement and applicable law. This can include professional notes and request contents while held, even when they are not visible in the client interface. For independently held professional working copies or delivered emails, the relevant professional or recipient may also need to act on the request. This includes stored documents and associated identifying metadata where they remain available. Customers can use file downloads, folder ZIP downloads and deletion controls, or contact us for help with return, correction, restriction or deletion.
You also have the right to lodge a complaint with the Data Protection Commission in Ireland if you believe that your personal data has been processed unlawfully.
12. Data Processing Agreement
Our Data Processing Agreement governs ZentraSnap's processing of Client Financial Data on behalf of customers and forms part of the contractual terms for use of the service.
View DPA13. Changes to This Privacy Policy
We may update this Privacy Policy to reflect changes to our service, processing activities, service providers, legal requirements or security practices. Where a material change is made, we will update the effective date of this Privacy Policy and take any additional notification steps required by applicable law.
14. Contact
For questions concerning this Privacy Policy or ZentraSnap's data-protection practices, contact: