Data Collection & Storage

Learn what account, poultry farm, financial, workforce, device, attachment, and support information HenBase may process, why it is used, where it is stored, and how users can manage or request deletion of their information.

Effective Date: July 15, 2026Last Updated: July 15, 2026

User-Controlled Farm Data

Most farm, flock, production, sales, expense, worker, payroll, customer, vendor, task, and note information is entered directly by HenBase users.

Secure Cloud Storage

HenBase uses authenticated cloud database and storage services to save and synchronize authorized records between supported app and web sessions.

No Sale of Farm Data

HenBase does not sell user information, poultry farm records, customer records, sales records, payroll data, or expense information to advertisers.

Account and Data Control

Users may update supported records, request correction, export important information where available, and submit an account deletion request.

1Data Categories

The table below describes the categories of data HenBase may collect, how it is used, where it is stored, and how it is managed. On mobile, the same information appears as stacked cards.

1. Account Profile Information

Examples

  • Full name
  • Email address
  • Phone number
  • Account profile details
  • Farm owner or organization details
  • Account preferences

How It Is Collected

Entered by the user during registration, account setup, profile editing, or support communication.

Why It Is Used

Create and manage accounts, identify the account owner, provide account access, communicate about support or service matters, and associate farm records with the correct user.

Where It Is Stored

Authenticated cloud database and account services.

Retention and Deletion

Retained while the account is active; removed through account deletion.

2. Authentication Information

Examples

  • Account ID
  • Authentication session
  • Email verification status
  • Password-reset status
  • Login timestamps where available
  • Security and authentication events

How It Is Collected

Created by the authentication provider when you register, sign in, verify email, or request a password reset.

Why It Is Used

Sign users in, protect accounts, verify identity, recover access, and prevent unauthorized access. Passwords and authentication secrets are handled by the authentication provider and are not displayed as readable text inside HenBase.

Where It Is Stored

Authentication provider services.

Retention and Deletion

Retained while the account is active.

3. Farm Information

Examples

  • Farm name
  • Farm location
  • Farm contact information
  • Farm description
  • Farm status
  • Farm settings

How It Is Collected

Entered by the user through HenBase farm forms.

Why It Is Used

Organize records by farm and display farm-level dashboards and reports.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

4. House and Pen Information

Examples

  • House or pen name
  • Farm association
  • Capacity
  • Location
  • Status
  • Notes

How It Is Collected

Entered by the user through HenBase house or pen forms.

Why It Is Used

Organize poultry records by physical house or pen.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

5. Flock Information

Examples

  • Flock name
  • Batch
  • Breed
  • Production purpose
  • Placement date
  • Initial bird count
  • Current bird count
  • Farm and house association
  • Status
  • Notes

How It Is Collected

Entered by the user through HenBase flock forms.

Why It Is Used

Track bird populations, production, mortality, feed, health, and reporting.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

6. Egg Production Records

Examples

  • Collection date
  • Total eggs
  • Good eggs
  • Broken eggs
  • Dirty eggs
  • Damaged eggs
  • Farm
  • House
  • Flock
  • Notes

How It Is Collected

Entered by the user through egg production records.

Why It Is Used

Calculate egg-production totals, trends, and reports.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

7. Feed Management Records

Examples

  • Feed item
  • Feed type
  • Purchase quantity
  • Usage quantity
  • Unit
  • Cost
  • Supplier or vendor
  • Farm
  • Flock
  • Record date
  • Notes

How It Is Collected

Entered by the user through feed purchase and usage forms.

Why It Is Used

Track feed purchases, feed usage, stock, cost, and reporting.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

8. Mortality Records

Examples

  • Number of birds lost
  • Date
  • Flock
  • Suspected reason
  • Notes
  • Disposal information where entered

How It Is Collected

Entered by the user through mortality records.

Why It Is Used

Track mortality totals, bird populations, alerts, and reports.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

9. Health and Vaccination Records

Examples

  • Health observations
  • Symptoms
  • Treatment notes
  • Vaccination type
  • Vaccine date
  • Next due date
  • Medication information
  • Veterinarian or provider notes where entered

How It Is Collected

Entered by the user through health and vaccination records.

Why It Is Used

Support health recordkeeping and reminders. HenBase does not diagnose disease or replace professional veterinary care.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

10. Inventory Records

Examples

  • Inventory item
  • Category
  • Quantity
  • Unit
  • Purchase information
  • Reorder level
  • Vendor
  • Notes

How It Is Collected

Entered by the user through inventory forms.

Why It Is Used

Track farm supplies and operational inventory.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

11. Sales Records

Examples

  • Sale date
  • Product type
  • Quantity
  • Unit price
  • Total amount
  • Amount paid
  • Balance due
  • Payment method
  • Payment status
  • Customer
  • Farm
  • Notes

How It Is Collected

Entered by the user through sales forms.

Why It Is Used

Track revenue, customer purchases, payments, balances, and financial reports.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

12. Customer Information

Examples

  • Customer name
  • Phone number
  • Location
  • Customer type
  • Purchase history
  • Payment status
  • Balance
  • Notes

How It Is Collected

Entered by the user through customer forms. Users must have lawful authority to enter customer information.

Why It Is Used

Manage customer relationships, purchases, balances, and sales records.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

13. Vendor Information

Examples

  • Vendor name
  • Contact person
  • Phone
  • Email
  • Address
  • Goods or services
  • Purchase history
  • Payment information
  • Notes

How It Is Collected

Entered by the user through vendor forms.

Why It Is Used

Manage suppliers, purchases, expenses, payments, and balances.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

14. Expense Records

Examples

  • Vendor
  • Category
  • Description
  • Quantity
  • Total amount
  • Amount paid
  • Balance due
  • Expense date
  • Payment method
  • Reference number
  • Notes

How It Is Collected

Entered by the user through expense forms.

Why It Is Used

Calculate expense totals, balances, and financial reports.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

15. Worker and Payroll Information

Examples

  • Worker name
  • Role
  • Phone number
  • Start date
  • Attendance
  • Work days
  • Salary or pay rate
  • Advances
  • Deductions
  • Payments
  • Payroll records
  • Notes

How It Is Collected

Entered by the user through worker, attendance, and payroll forms.

Why It Is Used

Support worker management, attendance, payroll calculations, deductions, payments, and reports. HenBase payroll tools are recordkeeping and calculation tools; users remain responsible for employment, payroll, tax, wage, overtime, and legal compliance.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

16. Tasks, Reminders, and Farm Notes

Examples

  • Task title
  • Description
  • Due date
  • Reminder date
  • Reminder time
  • Farm
  • Flock
  • Note type
  • To-do items
  • Completion status

How It Is Collected

Entered by the user through task and farm note forms.

Why It Is Used

Support operational planning, alerts, reminders, and farm recordkeeping.

Where It Is Stored

Authenticated cloud database (Supabase).

Retention and Deletion

Retained until deleted, archived, or removed through account deletion.

17. Reports and Calculated Information

Examples

  • Dashboard totals
  • Egg totals
  • Feed totals
  • Bird populations
  • Mortality totals
  • Revenue
  • Expenses
  • Payroll totals
  • Customer balances
  • Vendor balances
  • Production summaries

How It Is Collected

Generated by HenBase from user-entered records.

Why It Is Used

Derived from records entered by users. Incorrect, incomplete, duplicated, or outdated source records may affect reports.

Where It Is Stored

Generated from stored records; not stored as a separate permanent dataset unless saved by the user.

Retention and Deletion

Updated as source records change; removed with the related records on account deletion.

18. Attachments and Uploaded Files

Examples

  • Photos
  • Screenshots
  • Receipts
  • Farm documents
  • Support attachments
  • Other files intentionally uploaded by users

How It Is Collected

Intentionally uploaded by the user. Users should not upload passwords, complete payment-card numbers, government identification numbers, or unnecessary sensitive personal information.

Why It Is Used

Support records, documentation, issue investigation, and farm management.

Where It Is Stored

Secure cloud storage services when file-upload features are used.

Retention and Deletion

Deleted with the related record or through account deletion.

19. Device and Technical Information

Examples

  • Device type
  • Operating system
  • HenBase app version
  • Browser type
  • Error logs
  • Crash information
  • Diagnostic information
  • Session information
  • Synchronization errors

How It Is Collected

Generated automatically by the app, browser, or device when errors or crashes occur, where available.

Why It Is Used

Troubleshooting, security, performance improvement, compatibility, error investigation, and abuse prevention. HenBase does not collect GPS, precise location, contacts, camera, microphone, or advertising identifiers unless those features are actually enabled.

Where It Is Stored

Service provider systems, where enabled.

Retention and Deletion

Kept for a limited diagnostic period.

20. Support Communications

Examples

  • Name
  • Email
  • Phone
  • Ticket category
  • Priority
  • Subject
  • Message
  • Device information
  • Screenshot
  • Support responses
  • Ticket status

How It Is Collected

Submitted by the user through support forms or email.

Why It Is Used

Respond to account, technical, synchronization, billing, privacy, and deletion questions.

Where It Is Stored

Secure backend services.

Retention and Deletion

Retained while needed to resolve the issue and for limited security or operational records.

21. Account Deletion Requests

Examples

  • Full name
  • Account email
  • Phone
  • Reason
  • Confirmation statements
  • Request reference
  • Verification status
  • Processing status

How It Is Collected

Submitted by the user through the public Account Deletion page, in-app request, or support.

Why It Is Used

Verify, track, process, and document account deletion requests.

Where It Is Stored

Secure backend services.

Retention and Deletion

Retained to document completion and prevent fraud.


2How Information Is Collected

Information handled by HenBase may come from the following sources:

  • Information entered directly by users
  • Records created through HenBase forms
  • Calculations generated from user records
  • Authentication and security services
  • Support forms and email communications
  • Files intentionally uploaded by users
  • Device or diagnostic information generated when errors occur
  • App-store purchase status where paid subscriptions are enabled

HenBase does not purchase information from data brokers and does not engage in hidden data collection.


3Where Information Is Stored

HenBase uses a connected Supabase cloud database and authentication system for authorized account and farm records.

  • Some temporary information, interface preferences, cached data, or limited app settings may also be stored locally on a user's device.
  • Uploaded files may be stored through secure cloud-storage services when file-upload features are used.
  • Support and deletion requests are stored through secure backend services rather than only in browser or device memory.

Not all information is stored permanently, and not all information is stored only on the device.


4App and Web Synchronization

  • Authorized mobile and Base44 sessions may access the same Supabase records.
  • Users must sign in using the same HenBase account.
  • Records are associated with the authenticated user ID.
  • Synchronization may be delayed by internet access, authentication state, app version, service interruption, or database maintenance.
  • Users should refresh both platforms after important changes.
  • Users should verify critical records after synchronization.

5Account Access and Database Protection

HenBase uses authenticated access and row-level database security so users can access only records associated with their account, except where an authorized administrative role is permitted to perform support or system-management duties.

  • Users must protect login credentials.
  • Users should not share accounts with unauthorized people.
  • Users should log out of shared devices.
  • Administrative access is limited to authorized personnel.
  • Privileged database credentials are never included in public browser or mobile code.

HenBase does not publicly display technical secrets, keys, database policies, or service-role credentials.


6How HenBase Uses Information

HenBase uses information to provide and improve the platform, including:

  • Account registration and authentication
  • Managing farms, houses, flocks, and bird populations
  • Recording egg production
  • Managing feed
  • Tracking mortality
  • Managing health and vaccination records
  • Managing inventory
  • Recording sales and customer balances
  • Recording vendors and expenses
  • Managing workers and payroll
  • Managing tasks and farm notes
  • Generating reports and dashboards
  • Synchronizing authorized records
  • Providing reminders and alerts
  • Troubleshooting technical problems
  • Responding to support requests
  • Processing account deletion requests
  • Preventing fraud, abuse, and unauthorized access
  • Improving app reliability and compatibility

7Data Processing and Service Providers

HenBase does not sell user information or poultry farm records to advertisers. Information may be processed by service providers that are necessary for:

  • Authentication
  • Cloud database hosting
  • File storage
  • Website hosting
  • Email delivery
  • App distribution
  • Crash reporting
  • Analytics if enabled
  • Customer support
  • Payment processing if paid subscriptions are enabled

Providers are referenced only where actually used in the production application. HenBase does not share advertising data unless advertising is added to HenBase.

Information may also be disclosed where reasonably required for:

  • Legal compliance
  • Court orders
  • Fraud investigation
  • Security incidents
  • Abuse prevention
  • Protection of users or systems
  • Enforcement of legal terms

8Data Retention

  • Active account information is generally retained while the account remains active.
  • User-created operational records may remain until deleted, archived, or removed through account deletion.
  • Support tickets may be retained while needed to resolve the issue and for limited security or operational records.
  • Deletion-request records may be retained to document completion and prevent fraud.
  • Temporary backups may remain until normal backup-expiration processes complete.
  • Limited information may be retained where necessary for legal compliance, accounting obligations, security, fraud prevention, dispute resolution, or enforcement.
  • Retained information is not used for unrelated purposes.

HenBase does not promise immediate destruction of every backup copy.


9User Choices and Control

Users may:

  • Review supported account information
  • Edit account information where available
  • Add, update, archive, restore, or delete supported farm records
  • Request correction of inaccurate information
  • Request access to information where applicable
  • Request account deletion
  • Contact support with privacy questions
  • Manage optional device permissions through device settings where applicable
  • Export or save important business records where export features are available

Rights may vary depending on the user's location and applicable law.


10Account and Data Deletion

Users may submit an account deletion request:

  • From inside the HenBase mobile app
  • Through the public Account Deletion page
  • Through HenBase Support

Before requesting deletion, please note:

  • Users should export important records first.
  • Account ownership may need to be verified.
  • Deletion may remove user-controlled operational data.
  • Some limited records may be retained where legally or operationally necessary.
  • Temporary backups may require additional time to expire.
  • Deleting a HenBase account does not automatically cancel an Apple App Store or Google Play subscription.
Request Account Deletion

11Data Security

HenBase uses reasonable administrative, technical, and operational safeguards, including where configured:

  • Authentication
  • Database access rules
  • Encrypted network connections
  • Secure cloud hosting
  • Restricted administrative access
  • Input validation
  • Secure backend actions
  • Monitoring and error investigation
  • Account verification

No internet, cloud, device, or storage system can be guaranteed completely secure. Users should report suspected unauthorized access promptly.


12Children's Information

HenBase is intended for poultry farm owners, managers, workers, and people managing farm operations. HenBase is not designed for children under 13.

A parent or guardian who believes a child submitted information should contact HenBase Support.


13International Use

HenBase may be used in different countries, and data may be processed in locations where HenBase technology providers operate.

Privacy rights and legal requirements may vary by location. Users remain responsible for ensuring their use of HenBase complies with applicable local requirements.

HenBase does not claim specific international certifications that have not been verified.


14Data Accuracy Notice

Reports and Calculations Depend on User Data

HenBase dashboards, balances, totals, and reports depend on the information entered by users.

Missing, inaccurate, duplicated, outdated, or incorrectly assigned records may produce inaccurate results.

Users should review important records before relying on them for farm, payroll, tax, financial, veterinary, or regulatory decisions.


15Contact and Support

Contact HenBase regarding:

  • Privacy questions
  • Data access
  • Data correction
  • Security concerns
  • Support records
  • Account deletion
  • Data retention
  • Synchronization

HenBase Support

Contact HenBase regarding privacy, legal terms, data access, account deletion, billing, synchronization, or technical questions.

support@ssconsultingaccountingllc.com