SeringueiroSeringueiro

Kebijakan Privasi

v6 • DEFAULT

Note: This is the default version of our Privacy Policy. It applies when no localized version for your region is available. If a localized version exists, it may supplement or prevail over this default version to the extent required by applicable law.

Privacy Policy

Metadata

  • Version: 6
  • Updated on: 2026-04-10

1. Overview

Subject to applicable law, PEGUIM TECNOLOGIA LTDA, a private legal entity registered under CNPJ/MF No. 54.316.599/0001-04, with registered address at Rua São Paulo, No. 193, Poloni, São Paulo, Brazil ("Controller," "Company," "we," "us," or "our"), issues this Privacy Policy (the "Policy") to explain how personal data is processed in connection with the Seringueiro platform and related digital services.

2. Data We Collect

2.1. Geolocation and trip tracking

To support operational management and logistics auditing, we collect precise location data from your device.

  • What we collect: Latitude, longitude, speed, GPS signal accuracy, and timestamps.
  • When we collect it: Collection occurs continuously from the moment you start a tracked trip or activity until you end it.
  • Background collection and visibility: To preserve the integrity of route records, collection may continue while the app is minimized or the device screen is locked.
    • Android: We use a foreground service with a persistent notification.
    • iOS: We may use Live Activities on the lock screen and Dynamic Island, when available, to show trip status in real time.
  • Local storage and diagnostics: Trip identifiers, such as company, route, and trip IDs, may be stored locally on your device so tracking can resume after an app restart. Technical data about tracking-service failures may be sent to our diagnostic logs, including Crashlytics, for bug fixing and service stability.
  • Purpose: To calculate route efficiency, audit compliance with planned routes, and support operational safety.
  • Legal basis: Performance of a contract and, where permitted, legitimate interests.

2.2. Operational identifiers

We collect operation-related identifiers, such as Company ID, Route ID, Trip ID, and Driver ID, to associate location data with the correct operational context.

2.3. Property management and environmental data

To enable registration and monitoring of production units, we collect certain property-related data.

  • Property data: We collect the geographic location (GPS coordinates) of the property headquarters or center to provide localized weather forecasts and organize your production portfolio.
  • Rural Environmental Registry (CAR): We may collect a CAR receipt number to support autofill of property data, such as property name, city, state, and polygons, using public data sources.
  • Files and documents: If autofill is unavailable, we may allow manual upload of files, including PDF, ZIP, and JSON files, containing property data. You should not upload files containing sensitive personal data of third parties without authorization.
  • Purpose: Property registration, existence validation, and provision of climate intelligence services (AgroClima).

2.4. Production collection and evidence (Harvest Collection)

To support traceability and verify agricultural production information, we collect detailed data during harvest records.

  • Photographic evidence: The app uses your device camera to capture photos of packaging and production sites. These images help audit declared quantities and product quality. Gallery access is not used for this purpose; only photos captured in real time are accepted.
  • Collection geolocation: At the time a photo is captured or a record is created, we collect exact GPS coordinates to validate that production occurred within the declared property.
  • Production data: We collect information such as packaging type, quantity, collection date and time, and the identifiers of the production plots involved.
  • Offline processing: To support use in rural areas with limited connectivity, data and photos may be stored temporarily on your device and synchronized automatically with our secure servers once connectivity is available.
  • Hub visibility (optional): If you expressly choose to "Publish on Hub," collection data, including photos and descriptions, may become visible to other platform users.
  • Purpose: Operational management, inventory auditing, fraud prevention, and, where chosen by you, promotion of production.
  • Legal basis: Performance of a contract and, where permitted, legitimate interests.

2.5. Identity and authentication

To create and maintain your account securely, we collect identification data.

  • Data collected: Full name, email address, optional profile photo, and unique user identifiers (UID). If you use social login, such as Google, we collect the data provided by that provider in accordance with your authorization.
  • Session security: We collect technical connection data, such as IP address and device identifiers, and monitor session validity in real time to prevent unauthorized access and detect suspicious behavior.
  • Purpose: Identity management, secure authentication, account recovery, personalization, and fraud prevention.
  • Legal basis: Performance of a contract and, where applicable, consent.

2.6. Technical evaluation and quality control

To support standardized operational excellence, we collect technical data during field evaluations performed by agronomists and other technicians.

  • Technical evidence: We collect evaluation scores, textual observations, and detailed sample photos to audit production quality.
  • Sample geolocation: Each collected sample records exact latitude and longitude to confirm that the evaluation occurred at the proper location.
  • Evaluator data: We record identifiers and related information about the responsible technician and the evaluated producer for traceability and technical accountability.
  • Offline storage and synchronization: To support work in remote areas, data, including high-resolution photos, may be stored temporarily on the device as drafts and synchronized automatically once connectivity is restored. After synchronization, local data may be removed to free device storage.
  • Purpose: Quality control, technical auditing, and generation of agronomic reports.
  • Legal basis: Performance of a contract and, where permitted, legitimate interests.

2.7. Subscription management and limits

To administer platform usage and enforce contracted limits, including slot-based limits, we process data about the scale of your operation.

  • Usage data: We count active production modules, linked users, and storage usage to verify compliance with the limits of your current plan.
  • Subscription history: We keep records of plan changes, subscription status, and transactions for auditing and support.
  • Purpose: Enforcement of business rules, abuse prevention, and customer lifecycle management.
  • Legal basis: Performance of a contract.

2.8. Deliveries and commercialization

To manage production sales and financial allocation, we collect detailed commercial and tax-related data.

  • Financial and tax-related data: We collect sale price, total amount, discounts, buyer data, and tax indicators, including declaratory options used in internal calculations.
  • Participants and allocation: We record beneficiaries of the delivery, such as partners or co-producers, their participation percentages, and related amounts. When you enter third-party data, you represent that you have the necessary authorization to do so in the context of the relevant commercial relationship.
  • Automatic calculations: The system uses this data to calculate net amounts, weight deductions, and payment allocations, and stores the history of those operations.
  • Integrity and traceability: When production collections are linked to a delivery, we generate an audit record containing a snapshot of the relevant operational data. This record may be retained as needed for operational security and fraud prevention, even if source data is later deleted, to the extent permitted by applicable law.
  • Document export (PDF): The platform allows generation of PDF documents containing delivery summaries, financial data, weighing lists, photos, and traceability maps. These documents consolidate personal and operational data for external sharing by the user.
  • Purpose: Financial management, commercial history, transparency among partners, calculation support, and generation of records.
  • Legal basis: Performance of a contract and, where permitted, legitimate interests, including fraud prevention.

2.9. Agronomic monitoring and field activities

To support operational management of agricultural activities, such as tapping, stimulation, treatment, and replacement, we collect field execution data.

  • Activity tracking: During a field activity, we may continuously collect geolocation data, including latitude, longitude, and timestamps, to map routes and covered areas.
  • Background operation: To reduce interruptions in recordkeeping, the app may use continuous execution services.
    • Android: A foreground service with a persistent notification may be used.
    • iOS: Live Activities may be used to display activity status and duration in real time.
  • Context data: We associate the activity with the responsible user, the property, and the production module where the work is performed.
  • Offline operation: Data may be stored locally on the device and synchronized automatically once internet connectivity is available.
  • Purpose: Productivity control, coverage auditing, and field team management.
  • Legal basis: Performance of a contract and, where permitted, legitimate interests.

2.10. Public professional profile (networking)

To help connect professionals in the sector, such as producers, technicians, and rubber tappers, we offer an optional public-profile feature.

  • Optional nature (opt-in): Your profile is private by default. Public visibility is activated only if you expressly choose it in the app settings.
  • Data exposed: When public profile is enabled, the following data may become visible to other authenticated platform users: full name, profile photo, city/state, declared professions, CREA number if any, and contact data such as email and phone number.
  • Performance card generation and sharing: The platform may allow generation of an image summarizing performance metrics for external sharing. That file is generated locally on your device, and any external sharing is your responsibility.
  • Purpose: Professional networking, credential visibility, and hiring opportunities.
  • Legal basis: Consent.

2.11. Community and forum

To promote knowledge sharing and technical support, the platform offers community and forum spaces where users may publish topics and comments.

  • User-generated content: When you create a topic or comment, we collect and store the text, uploaded images, and publication metadata.
  • Attribution and visibility: Your content may be published to authenticated platform users together with your name and profile photo, if available, to preserve authorship and accountability.
  • Interaction data: We record interactions with content, such as likes, topic views, and watched topics, to personalize your feed and notify authors about relevant engagement.
  • Media storage: Uploaded images may be compressed and stored on secure servers, including Firebase Storage. When a topic or comment is deleted, related images may also be permanently removed.
  • Purpose: Community engagement, technical support, and dissemination of good agricultural practices.
  • Legal basis: Consent for publication and, where permitted, legitimate interests for community administration.

2.12. Calculation and export tools

The platform provides auxiliary tools, such as the DRC Calculator, to simulate financial values and generate reports.

  • Local processing: Data entered in these tools may be processed exclusively on your device and is not sent to our servers unless you expressly synchronize it as part of another feature.
  • Temporary files: When you use export functions, such as PDF or image export, temporary files may be generated in your device cache only for the time needed to complete sharing.
  • External sharing: The app may facilitate sending those files to third-party apps, such as messaging or email apps, but we do not control the destination or privacy of the data after it is shared.

2.13. Climate monitoring and operational intelligence

To provide agronomic recommendations, such as tapping and stimulation windows, we collect and process weather-related data connected to your property.

  • Property geolocation: We use the geographic coordinates registered for the property to obtain hyperlocal weather forecasts. Unlike real-time device location, this data is fixed and tied to the rural property.
  • Sharing with weather providers: To generate forecasts, we share the property coordinates with specialized weather providers, such as OpenWeatherMap. We do not share user identity data, such as name or email, with those partners for this purpose.
  • Climate history: We may store daily climate variables, such as rainfall, temperature, and wind, for productivity analysis and production correlation.
  • Purpose: Operational decision support, loss prevention, activity planning, and agricultural intelligence.
  • Legal basis: Performance of a contract and, where permitted, legitimate interests.

2.14. News and market intelligence

To provide editorial content and market indicators, the platform integrates news and quotation services.

  • Search queries: When you use news-search tools, the searched terms may be sent to content servers to return relevant results. We do not persistently associate those searches with your user profile unless otherwise disclosed.
  • Technical connection data: Content delivery may occur through CDNs and partner servers. In that process, IP address and technical device data may be processed strictly to transmit the requested content.
  • Purpose: Provision of sector information, market quotations, and educational content.
  • Legal basis: Legitimate interests, where permitted, or another legal basis available under applicable law.

3. Data sharing

  • Contracting entity or organization: Your trip-location data may be shared with the organization to which your account is linked for fleet management, auditing, or similar operational purposes.
  • Weather-data providers: We share property coordinates with weather services, such as OpenWeatherMap, to process and return forecast data shown in the app.
  • Other platform users: If you enable public profile or choose to publish production information on the Hub, specific profile or production data may become visible to other users of the Seringueiro platform. You may revoke that visibility at any time through the settings available in the platform.
  • Map and geolocation providers: We use third-party services, such as Google Maps Platform, to convert coordinates into addresses and display interactive maps. Location data and search terms may be shared with those providers strictly to deliver the requested service.
  • Authentication and infrastructure providers: We use cloud-service providers, including Google Firebase, for login processing, secure storage, and hosting. Those providers operate under their own contractual and security standards.
  • User-directed exports and sharing: The platform offers tools that allow you to export data, such as PDFs and profile or performance images. If you share exported files outside the platform, you are responsible for that external disclosure.

We do not sell your data to third parties for advertising purposes.

4. Data retention

We retain personal data and operational records for the period strictly necessary to fulfill the purposes described in this Policy, comply with legal or regulatory obligations, and protect rights in administrative, arbitral, or judicial proceedings.

In general:

  • Account and identification data: retained while the account remains active and, after a deletion request, for the period reasonably necessary to complete the request and comply with retention obligations.
  • Operational and traceability records, including geolocation, evidence, and audit snapshots: may be retained for the period needed for contractual performance, operational security, fraud prevention, support, and recordkeeping, subject to applicable law.
  • Security and diagnostic logs: may be retained for a limited and reasonable period for incident investigation, abuse prevention, bug fixing, and service improvement.
  • Backups: for continuity and security reasons, certain data may remain in backup copies for technical retention windows, during which we take measures to restrict access and use.

When you request deletion, we may retain specific records where a valid legal basis exists, such as legal compliance, establishment or defense of legal claims, or fraud prevention, always to the extent strictly necessary.

5. Your rights

Depending on your location and applicable law, you may have rights regarding your personal data, which may include the right to request access, correction, deletion, portability, restriction, objection, withdrawal of consent where processing relies on consent, and information about data sharing.

You may also have the right to lodge a complaint with the competent supervisory authority in your jurisdiction.

5.1. How to exercise your rights

To exercise your rights, contact us through the channel indicated in this Policy and, when possible, inform: (i) your full name, (ii) the email linked to your account, (iii) the right you want to exercise, and (iv) information that helps us locate the relevant data.

To protect data subjects and prevent fraud, we may request additional information to verify identity and clarify the request.

6. Contact

If you have questions about this Policy or about the processing of your data, contact us at: contato@peguim.com.br

7. International transfers

The platform uses infrastructure, storage, and cloud-processing providers, so personal data may be processed or stored on servers located outside your country of residence, depending on supplier architecture and availability. Where required, we adopt reasonable measures and safeguards to support an adequate level of protection under applicable law.

8. Information security

We adopt technical and organizational measures designed to protect personal data against unauthorized access and accidental or unlawful destruction, loss, alteration, disclosure, or misuse. No system is absolutely secure, so we also recommend that you keep your device protected, keep your operating system updated, and avoid sharing credentials.

9. Changes to this Policy

We may update this Policy from time to time to reflect legal, regulatory, or operational changes. The current version will remain available in the platform. When changes are material, we may provide additional notice where required or appropriate.