Privacy Policy

This Privacy Policy applies to Jangolo Business mobile applications, Jangolo account pages, Jangolo websites that link to this policy, and the related cloud services, support channels, and administrative tools. It describes how Jangolo handles information about visitors, account holders, organization administrators, employees, customers, suppliers, and other individuals whose information is entered into the service.

Some organizations may provide their own privacy notice for information they enter into Jangolo. In that situation, the organization decides why and how that business information is used, while Jangolo processes it to provide the service.

Jangolo is designed for day-to-day business operations, not advertising surveillance. We aim to request only information that supports account security, business features, service reliability, support, billing, and legal obligations.

• We do not sell personal information or organization records.
• We do not display third-party behavioral advertising inside Jangolo Business.
• We do not use customer sales, stock, payroll, supplier, or financial records to create advertising profiles.
• Access to organization data is restricted by account membership, roles, permissions, and technical controls.

Account information. When you create or use an account, we may process your name, email address, telephone number, authentication identifiers, preferred language, time zone, profile information, and account-security settings.

Organization information. Administrators may provide a business name, logo, addresses, contact details, tax or registration information, currencies, sites, stock locations, teams, roles, and operating preferences.

Support and communications. We process the content of support requests, feedback, demonstrations, forms, emails, and other communications you send to us, together with the contact information needed to respond.

Billing information. If paid services are used, we may process plan, subscription, invoice, transaction-status, and billing-contact information. Payment credentials may be handled directly by payment providers and are subject to their privacy practices.

Users and organizations may enter or upload operational records such as articles, categories, stock quantities, serial or IMEI codes, warehouses, sites, inventory counts, transfers, adjustments, customers, suppliers, purchases, sales, invoices, quotes, credit notes, payments, expenses, receipts, deliveries, documents, notes, and reports.

Organizations that enable team, payroll, or human-resources functions may also enter employee contact details, roles, work assignments, attendance information, salary terms, commissions, advances, payroll records, and related financial information.

The organization is responsible for deciding what business information is entered, ensuring that it has an appropriate legal basis, configuring user access, and responding to requests from individuals whose information it controls.

Jangolo may process product images, organization logos, receipts, attachments, signatures, documents, barcodes, QR codes, serial numbers, and other files that a user chooses to capture, upload, generate, or share. The app does not activate the camera unless a user invokes a feature that requires it.

Files shared from Jangolo through email, messaging, storage, printing, or another application become subject to the privacy practices of the destination selected by the user.

When you access the service, we may receive technical information needed to operate, secure, and troubleshoot it. This can include IP address, device and operating-system information, browser type, app version, language, time zone, network state, session identifiers, timestamps, requested pages or functions, crash details, diagnostic logs, and security events.

We use this information to maintain sessions, detect abuse, investigate failures, understand service performance, enforce rate limits, protect accounts, and improve reliability. We seek to avoid collecting diagnostic content that is not needed for these purposes.

In the Android app, the Privacy & Security options let users separately allow or disable technical session statistics and crash reports. When allowed, Sentry may receive the technical stack, app version and build, environment, operating system, device class, and a pseudonymous installation identifier needed for crash-free session measurement. The code excludes names, emails, phone numbers, business data, error messages, requests, screenshots, and view hierarchies.

If you sign in with Google or another supported identity provider, we receive the identifiers and profile information authorized through that provider, such as your email address and name. We do not receive the password you use with that provider.

We may also receive organization invitations, membership details, transaction confirmations from payment providers, delivery or communication status from integrated services, and information that another authorized user submits about you. Third-party services remain governed by their own terms and privacy policies.

Camera. Used when you choose to scan a barcode, QR code, or serial number, or capture an image or attachment.

Bluetooth. Used when you choose to connect a compatible scanner. On older Android versions, device discovery may require a location-related permission even though Jangolo does not use it to build a location history.

Biometric authentication. Used locally, when enabled, to unlock the app. Jangolo does not receive or store your fingerprint, face template, or other biometric template.

Files, photos, and notifications. Requested only where required to select or save a file, attach an image, export a document, or deliver notifications you have enabled. Permissions can be changed in device settings, although disabling one may prevent the related feature from working.

Jangolo websites and account pages may use cookies, local storage, and similar technologies to keep you signed in, remember preferences, secure forms, prevent fraud, maintain sessions, and understand essential service performance. Where required, optional technologies are used only after an appropriate choice.

More information about website technologies and controls is available in our Cookie Policy. Browser settings may block some storage, but essential account or security functions may then be unavailable.

• To create, authenticate, secure, recover, and administer accounts.
• To provide inventory, purchasing, sales, finance, reporting, document, team, and other features selected by an organization.
• To synchronize authorized devices and keep business records consistent.
• To apply organization membership, warehouse access, roles, and permissions.
• To generate invoices, receipts, reports, exports, and other documents requested by users.
• To process subscriptions, verify payment status, and maintain billing records.
• To answer support requests, investigate incidents, and communicate service notices.
• To prevent fraud, misuse, unauthorized access, and threats to users or the service.
• To comply with applicable law, lawful requests, accounting duties, and dispute-resolution needs.
• To improve accessibility, performance, stability, and product design using information appropriate for that purpose.

Depending on the context and applicable law, Jangolo processes personal information because it is necessary to provide a requested contract or service, because an organization has instructed us to process its data, because we have a legitimate interest in securing and improving the service, because we must comply with a legal obligation, or because consent has been provided for a particular optional activity.

Where processing relies on consent, that consent may be withdrawn for future processing. Withdrawal does not affect processing that was lawful before it was withdrawn and may make an optional feature unavailable.

An organization administrator can invite or remove members, assign roles and stock locations, configure permissions, review organization records, and control many aspects of the workspace. Information entered under an organization may therefore be accessible to its authorized administrators and members according to their permissions.

If you use an account provided by an employer or another organization, that organization may control the workspace and related records. Questions about its internal use of your information should first be directed to that organization.

We use carefully selected providers to operate parts of Jangolo, such as cloud hosting, databases, storage, authentication, email, payment processing, security, error diagnosis, and customer support. These providers receive only the information reasonably needed to perform their services and are expected to protect it under contractual and legal obligations.

Sentry acts as a diagnostic provider when this collection is enabled. Technical information is used only to understand failures, measure stability, and improve reliability; it is not used for advertising or commercial profiling.

Current technology may include services supplied by Supabase and Google for infrastructure or identity functions. The exact provider may change as the service evolves, but Jangolo remains responsible for selecting providers appropriate to the function and applicable requirements.

We may disclose information to authorized members of the relevant organization; to service providers acting for us; when a user deliberately shares or exports information; to protect the security, rights, or safety of Jangolo, users, or others; to investigate fraud or abuse; or when required by applicable law, court order, or another valid legal process.

If Jangolo is involved in a merger, financing, acquisition, reorganization, or sale of assets, information may be reviewed or transferred as part of that transaction, subject to appropriate confidentiality and notice where required. We do not disclose customer business records to data brokers for advertising.

Jangolo and its providers may process information in countries other than the country where a user or organization is located. Privacy and data-protection laws differ between countries. Where required, we use contractual, organizational, or other recognized safeguards for cross-border processing.

Organizations remain responsible for evaluating any location-specific requirements that apply to the business information they choose to place in the service.

Jangolo uses measures appropriate to the nature of the service, including encrypted network connections, authentication controls, organization separation, role permissions, database row-level restrictions, protected secrets, backups where appropriate, logging, and procedures for responding to suspected incidents.

Users also play an important role: use a strong and unique password, protect recovery methods, enable available device security, limit administrator access, review team permissions, keep devices updated, and notify us promptly if an account or device may be compromised. No internet or storage system can be guaranteed completely secure.

We retain information for as long as needed to provide the service, maintain account and organization continuity, meet security and accounting needs, resolve disputes, enforce agreements, and comply with legal obligations. Retention periods vary according to the type of record, the organization’s instructions, and applicable requirements.

Deleted information may remain for a limited period in protected backups, logs, fraud-prevention records, or records that must be retained by law. During that period it is restricted from ordinary use and removed or anonymized according to the relevant lifecycle.

You may request account deletion through the app or the account deletion page. We may need to verify identity, authority, and organization ownership before completing a request.

Deleting one member does not necessarily delete records owned by an organization or needed by other authorized members. Before an organization account is deleted, ownership may need to be transferred, records exported, outstanding obligations resolved, and legally required information retained. We will explain material limitations that apply to a verified request.

Depending on applicable law and our role in relation to the information, you may have rights to request access, correction, deletion, restriction, portability, or objection; withdraw consent; or complain to a data-protection authority. We may ask for information needed to verify identity and protect accounts from fraudulent requests.

For information controlled by an organization using Jangolo, requests should generally be sent first to that organization. We will support verified organizations in responding to requests where required. Some rights are subject to lawful exceptions, including security, accounting, legal claims, and the rights of others.

Jangolo Business is intended for organizations and authorized business users, not for children acting on their own. Children should not create accounts unless the use is lawful, appropriately supervised, and authorized by the relevant parent, guardian, employer, school, or organization.

An organization that enters information about minors is responsible for complying with applicable child-privacy and employment laws and for limiting collection and access appropriately.

Privacy law often distinguishes between an organization that decides why and how personal information is used and a provider that processes information on that organization’s instructions. Jangolo generally determines the purposes of processing for account registration, website operation, subscription administration, fraud prevention, service security, support management, and direct communications about Jangolo. For those activities, Jangolo acts as the organization responsible for the processing, subject to applicable law.

For sales, customers, suppliers, employees, inventory movements, payroll, invoices, attachments, and other records entered into a workspace, the subscribing organization generally decides the purpose, content, access rules, and retention needs. Jangolo processes those records to provide the selected features. The organization must inform the affected people, identify a lawful basis, respect their rights, avoid entering excessive or unlawful information, and configure access appropriately.

If Jangolo receives a request concerning information controlled by a customer organization, we may direct the requester to that organization. We may also notify the organization and provide reasonable technical assistance. This division of responsibilities does not reduce Jangolo’s duty to protect the service data entrusted to us or to follow valid instructions within the limits of the law and the service agreement.

Creating an account requires information that allows us to identify the account holder, establish a secure session, associate the person with an organization, and communicate essential notices. Authentication records may include a password hash, identity-provider identifier, login timestamps, failed-attempt information, recovery status, device or session identifiers, and security events. Passwords are intended to be protected through one-way security techniques rather than stored as readable text.

When Google or another supported provider is used, the provider authenticates the person and sends Jangolo the authorized identity attributes. The provider may independently record the authentication request. Removing Jangolo from a provider account does not automatically delete the Jangolo account, and deleting the Jangolo account does not necessarily delete records retained by the identity provider.

Recovery procedures may require additional verification to prevent an attacker from taking over an account. We may temporarily delay or refuse a recovery or sensitive account change when signals indicate abuse, when ownership cannot be reasonably established, or when an organization administrator must approve the change. Security logs related to attempted access may be retained after a session ends when needed to investigate misuse and protect other users.

A workspace can contain owners, administrators, managers, sellers, stock personnel, delivery personnel, accountants, read-only users, or other roles created by the organization. The information visible to each person depends on product configuration, assigned permissions, sites, warehouses, and the actions of administrators. A person with broad administrative rights may be able to view, export, correct, or delete substantial portions of the organization’s data.

Invitations may include the invited email address, inviting organization, proposed role, invitation status, expiration information, and audit events. Administrators should verify addresses before sending invitations and promptly revoke access when a person changes responsibility or leaves the organization. Shared credentials should not be used because they make it harder to protect records and determine who performed an action.

Jangolo may record important administrative activity such as invitations, role changes, exports, deletions, authentication events, or security-sensitive configuration changes. These records support accountability, troubleshooting, fraud prevention, and dispute resolution. Availability and detail can vary by plan and feature, and an audit record should not be treated as a complete employee-monitoring system.

Business functions necessarily connect information across records. Creating a sale may use customer details, article descriptions, quantities, prices, taxes, discounts, payment status, salesperson identity, site, stock availability, and document numbering. Purchasing may use supplier contacts, costs, expected deliveries, received quantities, payment information, and attachments. Inventory calculations may use every validated movement affecting an article at a site or warehouse.

Reports, dashboards, profit estimates, and forecasts are generated from records entered or synchronized by authorized users. Their accuracy depends on the completeness and correctness of those records. Jangolo may calculate totals, margins, balances, aging, stock levels, performance indicators, and other derived values to display requested features, but these calculations do not change who controls the underlying business information.

Organizations should avoid placing full payment-card numbers, authentication secrets, medical information, or unrelated sensitive data in free-text fields or attachments. Where a record must be preserved for accounting, tax, warranty, anti-fraud, or legal reasons, deletion requests may require restriction or anonymization instead of immediate removal. The organization is responsible for setting lawful document and accounting retention practices for its jurisdiction.

When an organization enables workforce functions, it may process names, contact information, job roles, work sites, attendance, schedules, salary components, commissions, advances, deductions, payment history, and notes. This information can be sensitive because it describes a person’s employment and financial circumstances. Access should be limited to people who genuinely require it for payroll, management, accounting, or legal compliance.

Jangolo provides tools selected by the organization and does not independently decide an employee’s compensation, discipline, schedule, tax treatment, or legal status. Calculations and generated documents depend on the rules and values supplied by authorized users. Organizations should verify outputs before relying on them for payment or official filings and should provide employees with any notice required by local labor and privacy law.

Employee requests concerning workplace records should normally be addressed to the employer or organization first. Jangolo may preserve limited technical and security evidence when an account is removed, while the organization may retain payroll or employment documents for mandatory periods. A former employee’s removal from the workspace does not automatically erase legitimate business records that identify actions performed during employment.

Authorized users may import information from spreadsheets, files, devices, or supported services. An import may create new records, update existing records, or associate information based on identifiers chosen by the user. Before importing, the organization should verify that it has authority to use the information, that the file does not contain unnecessary columns, and that recipients and permissions are correctly configured.

Exports, PDFs, receipts, invoices, reports, backups, print jobs, and shared files can contain personal or confidential business information. Once downloaded, printed, copied, emailed, or sent to another application, the copy may no longer be controlled by Jangolo. The person initiating the action and the organization are responsible for selecting an appropriate destination, protecting the file, and deleting obsolete copies.

Some devices and operating systems may cache previews, recent files, print queues, notification content, or downloaded documents. Jangolo cannot remove every copy created outside the service. Users should use device encryption, screen locks, trusted printers, secure communication channels, and appropriate recipient checks, particularly for payroll, customer, supplier, or financial documents.

An organization may choose to connect Jangolo with identity providers, payment services, messaging tools, storage providers, scanners, accounting systems, or other applications. A connection can allow information to move between services in accordance with the permissions presented during setup. Jangolo does not activate an optional integration merely because it is technically available.

The administrator enabling an integration should review the categories of information exchanged, the provider’s privacy terms, the people who can use it, and the method for disconnecting it. A third party may retain information previously received even after the connection is disabled. Disconnecting may stop future transfers but may not reverse transactions, messages, documents, or copies already created.

We may restrict or disable an integration that threatens service security, violates applicable requirements, changes in an incompatible way, or is no longer supported. Providers control their own systems and availability. When an integration acts on an organization’s instructions, the organization remains responsible for ensuring that the transfer and the third party’s intended use are appropriate.

We may send transactional communications needed to operate an account, including verification messages, password or security alerts, invitations, subscription notices, receipts, service-status information, policy updates, and responses to support requests. These communications are not promotional, and disabling marketing messages does not prevent us from sending information necessary to provide or secure the service.

Optional product announcements, educational material, surveys, and offers may be sent where permitted. Recipients can use the unsubscribe mechanism or contact us to change promotional preferences. We may retain a minimal suppression record so that an address that opted out is not accidentally added back to the same list.

Push notifications can reveal limited information on a locked screen depending on device settings. Users can change notification permissions and preview settings through the operating system. Delivery providers may process device tokens and technical delivery information. An organization may also generate customer or staff communications using Jangolo features; in that case, the organization is responsible for the recipients, content, timing, consent, and compliance of those messages.

When a person contacts support, we use the supplied account information, description, screenshots, files, device details, and relevant diagnostic records to understand and resolve the request. Support personnel may ask for additional context, but users should redact unrelated personal information and never send passwords, one-time codes, private signing keys, or complete payment-card credentials.

Access to customer records for support is limited to what is reasonably needed and may require authorization from an account holder or administrator. We may keep a history of the request, actions taken, and resolution so that we can provide consistent assistance, identify repeated defects, train authorized personnel, defend against abuse, and improve documentation or product reliability.

Ideas, feature requests, ratings, survey answers, and other feedback may be analyzed and combined with similar feedback. We will not publicly identify the author of a testimonial or case study without appropriate permission. If a support channel is operated through another provider, that provider may process the conversation under its service agreement with us.

We may use limited technical and usage information to understand whether features load, synchronize, fail, or are difficult to use. Relevant events can include application version, screen or feature category, response time, crash type, device class, network state, and whether an operation completed. We aim to minimize event content and avoid using customer documents or transaction details when an aggregate or technical signal is sufficient.

Analysis may be performed at an aggregated, pseudonymized, or account level depending on the troubleshooting or improvement need. Aggregate statistics can help us prioritize performance work, capacity, accessibility, language coverage, and frequently requested workflows. Account-level review may be necessary when an authorized user reports a specific synchronization or data-consistency problem.

Analytics used for essential security and reliability may not be optional because the service cannot be safely operated without detecting failures and abuse. Where a separate technology is used for optional measurement, we will provide the choice required by applicable law. Product analytics are not used to sell a person’s behavior to advertising networks.

Jangolo may offer automation, recommendations, document recognition, anomaly detection, summaries, or other assisted features. When such a feature is available, it may process the records selected by the user or required for the requested result. We will seek to describe the feature’s purpose and any important choice before information is sent to a separate model or specialized provider.

Automated output can be incomplete or incorrect and should be reviewed by an authorized person, especially before changing stock, paying an employee or supplier, filing taxes, granting credit, contacting a customer, or making another consequential decision. Jangolo should not be used as the sole basis for decisions that produce legal or similarly significant effects on an individual unless the organization has established an appropriate lawful process.

Customer business records are not treated as public information merely because an automated feature processes them. If we intend to use identifiable service data to train a general-purpose model beyond providing the requested service, we will first establish an appropriate legal basis and provide any notice or choice required. We may use de-identified, aggregated, synthetic, or internally generated information to evaluate quality and safety.

We may transform information so that it no longer reasonably identifies a person or organization, or combine it with information from many accounts. Such information can be used to measure service availability, understand general product adoption, plan infrastructure, detect broad security patterns, produce non-identifying statistics, and improve features.

De-identification is assessed in light of the information reasonably available and the purpose of use. We do not attempt to re-identify information that we have designated as de-identified except to test whether protective techniques remain effective, investigate security, or comply with law. We also expect recipients of de-identified information to avoid re-identification where applicable.

Aggregated figures published externally should be presented at a level that does not reveal a customer’s confidential results or an individual’s activity. Information that can still be linked to an account through a code or separate key is pseudonymous rather than anonymous and remains protected as personal or customer information where applicable.

We monitor technical signals that can indicate credential attacks, unauthorized access, unusual traffic, malicious files, abuse of invitations, unexpected exports, or attempts to bypass organization boundaries. Monitoring may use IP addresses, session identifiers, request patterns, device details, timestamps, access results, and other security events. Access to this evidence is limited to authorized operational, security, legal, or support needs.

If we identify a suspected incident, we may preserve relevant logs, restrict sessions, require renewed authentication, disable a feature, contact administrators, reset credentials, or take other proportionate measures. Investigation may involve infrastructure providers or professional advisers bound by confidentiality. We aim to distinguish a security event from ordinary mistakes and to avoid disrupting legitimate business more than necessary.

Where applicable law or a contractual commitment requires notification of a personal-data breach, we will provide notice to the appropriate customer, authority, or affected person within the required framework. The content and timing may depend on the investigation, risk, law-enforcement restrictions, and the customer’s role. Users should report suspected compromise promptly and preserve relevant evidence without publicly disclosing sensitive details.

We may receive subpoenas, court orders, regulatory demands, preservation requests, or other government requests. We review requests for apparent validity, scope, authority, and jurisdiction. Where legally permitted and appropriate, we may challenge an overbroad request, seek clarification, limit disclosure to the information legally required, or direct the requester to the customer organization that controls the records.

We may notify the affected customer before disclosure unless prohibited by law, a court order, an emergency, or a reasonable concern that notice would create harm or defeat the lawful purpose of the request. A delayed notice may be provided when the restriction expires if permitted. Emergency disclosures are considered only where we reasonably believe they are necessary to prevent imminent risk of death or serious physical harm and the request contains sufficient information.

We may also preserve or use information when reasonably necessary to establish, exercise, or defend legal claims; enforce agreements; investigate fraud; protect users; collect amounts owed; or respond to a dispute. This does not authorize unrestricted access to customer records, and internal access remains limited according to need and applicable safeguards.

If Jangolo considers or completes a financing, merger, acquisition, restructuring, insolvency process, or sale of some or all assets, relevant information may be disclosed under confidentiality to professional advisers, potential counterparties, investors, or a successor. We would seek to limit disclosure to what is reasonably required for evaluation, security, continuity, and completion of the transaction.

A successor that receives personal information would be expected to honor applicable privacy obligations and the commitments associated with the transferred service. If the transaction materially changes the responsible entity or the purposes for which personal information is used, we will provide notice and choices where required by law.

Changes within a customer organization—such as a new owner, administrator, employer, franchise manager, or legal entity—are controlled by that customer. Jangolo may require evidence of authority before transferring workspace ownership or releasing access, particularly where existing administrators dispute the change.

Privacy rights and terminology differ by country and region. Depending on the applicable law, a person may be entitled to know the categories and sources of personal information, the purposes of use, the categories of recipients, retention criteria, and whether information is sold or used for targeted advertising. As stated above, Jangolo does not sell personal information or customer business records and does not use them for third-party behavioral advertising.

Some laws provide rights to correct inaccurate information, obtain a portable copy, request deletion, restrict or object to processing, withdraw consent, opt out of certain transfers, or appeal a refusal. Rights may be limited when a request conflicts with another person’s rights, legal retention, security, confidential business information, freedom of expression, fraud prevention, or the establishment of legal claims.

Nothing in this policy is intended to reduce non-waivable rights. If a region-specific notice or contract applies to a particular customer, that document supplements this policy. Where the documents conflict, the more specific legally applicable term controls for the matter it addresses.

A request should clearly identify the account, organization, right being exercised, and information concerned. To protect users, we may verify control of the registered email or telephone number, require authentication, ask for appropriate evidence, or confirm authority when an agent submits the request. We will not request more verification information than reasonably needed.

We aim to respond within the period required by applicable law. Complex or numerous requests may require an extension where permitted, in which case we will explain the delay. We may ask the requester to clarify an overly broad request so that we can locate the relevant information. A response may be delivered through a secure account channel rather than ordinary email.

Requests are generally free, but applicable law may allow a reasonable fee or refusal for manifestly unfounded, excessive, repetitive, or abusive requests. If we deny or limit a request, we will explain the principal reason and any available appeal or complaint route where required. We may retain a limited record of the request to demonstrate compliance and prevent fraud.

Jangolo pages may link to documentation, app stores, social networks, payment pages, partner sites, or other resources that we do not operate. A link does not mean that the external service follows this policy. Before providing information, users should review the destination, its operator, permissions, security, and privacy terms.

If Jangolo later offers public profiles, shared catalogues, public documents, comments, forums, or community spaces, information deliberately published there may be indexed, copied, forwarded, or retained by other people and search services. Users should not publish confidential, sensitive, or third-party information without authority. Removing the original post may not remove copies outside our control.

Social-media interactions with Jangolo are also processed by the relevant platform. We may view information made available through that interaction and use it to respond, moderate abuse, or understand feedback, but the platform independently determines many of its own processing purposes.

Some browsers send “Do Not Track” or other preference signals. Because the meaning and legal effect of these signals can differ, Jangolo responds to recognized legally required signals where applicable and otherwise uses the cookie and privacy controls described on the relevant page. Essential storage needed for authentication, security, fraud prevention, or a requested function may continue to operate.

A device or browser preference may apply only to that device, browser, or profile. Clearing storage, using another device, signing out, or changing browser settings can affect the saved choice. Account-level preferences may continue across devices when the service is designed to store them with the account.

We design forms and workflows to collect information relevant to the function being used, but flexible business tools also allow organizations to create descriptions, notes, categories, attachments, and custom operational practices. An available field is not an instruction to enter every possible detail. Users should enter only information that is accurate, relevant, lawful, and reasonably necessary for the business purpose.

Account holders can correct many profile and business records directly, while some finalized accounting, inventory, security, or audit records may require a reversal, adjustment, annotation, or administrator action rather than silent replacement. This preserves traceability and does not prevent the correction of inaccurate personal information. Where a direct edit is unavailable, an authorized user can contact support or use an appropriate compensating workflow.

Jangolo may identify obvious formatting errors, duplicate candidates, impossible quantities, incomplete required fields, or inconsistent references, but automated validation cannot guarantee that a record reflects reality. Organizations remain responsible for regular review, reconciliation, access checks, and correction at the source. If inaccurate data has been exported or sent to another recipient, the organization may also need to correct the external copy.

Retention is determined by the nature of the information and the reason it is held. Active account and workspace records are generally retained while the service is used. Billing, invoice, tax, and transaction evidence may be retained for statutory accounting periods. Security events may be retained long enough to detect repeated attacks and investigate incidents. Support records may be kept to resolve recurring problems and document commitments. Marketing preferences may be retained until changed, together with a limited suppression record after an opt-out.

When an organization deletes a record, closes a workspace, or ends a subscription, active copies may be removed, anonymized, or placed beyond ordinary use according to the applicable workflow. Technical queues, replicas, caches, and backups update on different schedules. A backup is maintained for resilience and is not intended as an archive that users can browse after deletion. If restoration is required following a failure, deletion instructions applicable at the time of backup are reapplied where technically and legally appropriate.

We may retain a limited subset longer when necessary for fraud prevention, security, legal claims, contractual enforcement, financial reconciliation, or mandatory law. When the reason ends, the information is deleted or de-identified according to the relevant process. Customers with specific statutory obligations should configure their own retention practices and export required records before closing the service.

Subscription administration may require the customer name, plan, billing period, currency, invoice details, tax information, payment method category, provider transaction identifier, status, renewal information, refunds, disputes, and communication history. A payment provider may collect additional identity, bank, mobile-money, or card information directly. Jangolo receives only the information the provider makes available for confirming and reconciling the transaction.

We and our providers may use transaction and technical signals to prevent duplicated charges, unauthorized payments, account takeovers, promotion abuse, chargebacks, and other fraud. A suspicious transaction may be delayed, refused, reversed, or referred for additional verification. These measures protect customers and the service but do not guarantee that every fraudulent or mistaken transaction will be detected.

Financial institutions, mobile operators, app stores, tax authorities, and payment networks may independently process payment information under their own legal obligations. Questions about their processing should be directed to them. Jangolo may retain billing evidence after account deletion when needed for tax, accounting, dispute, anti-fraud, or legal purposes, while restricting it from unrelated product use.

If you believe that Jangolo has handled personal information incorrectly, please contact us with enough detail to understand the issue. We will review the relevant account, our role, the applicable records, and the response already provided. A complaint does not affect access to ordinary support, and raising a good-faith privacy concern will not result in retaliation or a reduced level of service.

Where applicable law provides an internal appeal after a privacy request is denied, the appeal should identify the original request and explain why the decision should be reconsidered. It will be reviewed by an appropriate person who was not solely responsible for the initial outcome where reasonably possible. We will communicate the result and any further complaint options required by law.

You may also have the right to complain to a data-protection, consumer-protection, or other competent supervisory authority in the country or region where you live, work, or believe an infringement occurred. We encourage direct contact first because it can allow us to investigate and correct an issue quickly, but doing so does not remove a legally protected right to approach an authority.

This Privacy Policy explains information practices and should be read with the Jangolo Terms of Service, Cookie Policy, account notices, subscription terms, and any data-processing or enterprise agreement that applies. The Terms govern use of the service, while this policy focuses on personal information and customer service data. A product screen may provide a more specific notice at the moment a particular feature is enabled.

Examples in this policy illustrate common Jangolo functions and do not state that every feature, provider, permission, or category is used by every customer. “Including” and similar expressions introduce examples and are not exhaustive. References to law mean the law applicable to the relevant processing, which can vary according to the person, organization, service, and location.

If a translated version differs materially from the version designated as controlling in an applicable contract, the contract determines which text governs that customer. We nevertheless intend the French and English policies to communicate the same substantive commitments. Questions about an apparent difference may be sent to the privacy contact below.

We may update this Privacy Policy when Jangolo features, providers, security practices, or legal obligations change. The date shown above will be updated. If a change materially affects privacy rights or how personal information is used, we may also provide notice in the service, on an account page, or by email where appropriate.

Earlier versions may be retained for accountability. Continued use after an updated policy takes effect does not remove any rights that cannot lawfully be waived.