Privacy Notice

Information used by the service

The service processes account identity and sign-in information, application and business details, authorized properties and manager grants, scopes, invitations, quotes, approvals, notes, photos, activity history, self-reported direct payments, vendor customer-job records, and information you submit through the contact form. Necessary technical and abuse-prevention records may include network information and timestamps.

Why information is processed

Information is used to authenticate accounts, approve access, enforce permissions, organize requested work, preserve decisions, maintain software subscriptions, answer inquiries, prevent abuse, and operate or recover the service. Avoid placing unnecessary tenant, resident, or other sensitive personal information in scopes or photographs.

Who can see work records

Private property records are limited to the owner's authorized relationships and relevant platform administration. Vendors receive only their invited or assigned Nectar work and their own quotes, not competing quotes. A vendor's outside-customer jobs and photos are private to that vendor and omitted from ordinary administrator snapshots. Necessary operator-level database or recovery access is separate from ordinary application permissions and must be controlled operationally.

Service providers and payment details

Manus provides the current hosting and managed database. Nectar-branded email/password login uses application-owned credential and session records; passwords are stored as salted Argon2id hashes, not plaintext. Existing users have a limited validated Manus sign-in transfer path until they verify a Nectar password; matching an email address alone cannot transfer an account or grant authority. Namecheap Private Email is configured for authentication verification and recovery messages when its mailbox connection is verified. Separately gated owner approval/report email preparation uses this business mailbox only for a native owner's currently verified, expressly selected recipient and their own property events. Sending remains disabled until release and delivery verification. Vendor invitations remain in-app only; no vendor invitation email/SMS, production Luna integration or marketing analytics is provided.

Stripe processes software subscription checkout when configured. The app stores necessary subscription identifiers, verified status, amounts, history and consent records, not card numbers, security codes, raw payment callbacks, or processor secrets. Job photos are held in private database records and served after authentication and record authorization. Necessary encrypted operator recovery snapshots can include private credential, session and token hashes; these are excluded from ordinary account exports. Provider-operated infrastructure and linked websites have their own notices.

Owner operational email preferences

Native owners can request approval notices and completion/project reports at their own current verified Nectar email, or disable those categories in Owner emails. Managers and administrators cannot change an owner's recipient or consent. The service retains preference version, dates and a contact-identity digest plus minimal scoped event and handoff status records, not copies of private photos, scope, card details or authentication links in the email queue. A changed contact or withdrawn consent cancels queued old-version messages rather than retargeting them.

These are operational messages, not marketing. Links require normal sign-in and never themselves approve work. A message accepted by the mail provider is not proof of inbox receipt; accepted or uncertain handoffs cannot be recalled or blindly resent. Non-login owner agreements, actual delivery/sender DNS and ongoing dispatch operations remain separate launch requirements. No owner receives another client's report.

Cookies and browser storage

Necessary session and sign-in cookies support authentication and login protection. Session storage can remember the workspace role you chose during onboarding. The current implementation does not include advertising pixels or features for selling personal information. These statements describe this implementation, not every possible provider activity or a legal classification of all processing.

Retention, export, and requests

Current business records are retained without an automatic purge. The selected project-record periods below are proposed for paid launch, not implemented expiry or deletion processes. An authenticated account export provides only the records within that account's current permissions. Trial-only accounts now have a selected project-record period; other record categories still require separate reviewed retention rules.

Owner-selected proposed paid-service rule: cancelled customers' authorized project records are retained for 12 calendar months after their verified paid period ends. Cancellation does not itself delete records, and this choice does not authorize automatic deletion.

Owner-selected proposed trial-service rule: never-paid trial customers' authorized project records are retained for 90 calendar days after the original verified trial ends. Trial expiry does not itself delete records, and this choice does not authorize automatic deletion.

This period applies only to never-paid trial project records, not paid customers' records or every account, shared property record or backup. It does not extend or restart a trial, renew paid editing, grant access or change current role, property and company permissions. Valid requests, legal holds and other authorized parties' rights require separate reviewed handling; remaining record categories and operational disposal stay unresolved. No expiry/purge engine or guaranteed-availability promise is activated.

Owner-selected proposed vendor-record rule: vendors' own private outside-customer job records use the same periods: 12 calendar months after verified paid-period end for cancelled paid vendors, or 90 calendar days after the original verified trial ends for never-paid trial vendors. No automatic deletion is authorized.

This rule covers only the vendor's own private outside-customer job records. A vendor without a verified paid-period or trial end has no invented expiry date. The vendor's clock does not expire another owner's or company's records or shared Nectar work, reveal competing quotes, grant access, extend/restart a trial, renew editing, change backup retention or activate vendor payments. Valid requests, legal holds, legally required financial or other records and other parties' rights require separate reviewed handling. Other category schedules and operational disposal remain unresolved; no expiry/purge engine or availability guarantee is activated.

Read access and export remain subject to current role, property and company permissions and security restrictions; retaining a record does not grant new access or renew paid editing. Valid requests, legal holds, overlapping authorized parties' rights and the reviewed disposal process must be finalized before paid launch. The period's end does not automatically erase or revoke records, and this choice is not a guaranteed-availability promise. Backup copies follow their separate approved custody and retention rules and may be subject to lawful preservation requirements.

Owner-selected privacy/account assistance contact: admin@nectarprooperations.com. Nectar's business owner is the selected initial review contact. Identity and appropriate authority must be verified before private data is disclosed or changed.

Selecting this contact does not grant application permissions or authorize automatic disclosure, correction or deletion. It does not add a payment or new-account requirement to exercise applicable rights, require owner review before an otherwise authorized self-service export, or promise a response time. Applicable rights and current owner, property, company and vendor boundaries remain in force; private case/deadline handling and safe fulfillment/disposal operations still require review and verification.

The in-app inquiry form is an alternative intake route, not identity verification or automatic fulfillment. Applicable rights depend on the circumstances and jurisdiction; this draft does not claim a nationwide privacy certification.

Security and changes

Authentication, server-side permissions, bounded private uploads, and private/no-store responses are implemented. No system is guaranteed secure and no independent security certification is claimed. Final incident procedures and backup/retention arrangements remain launch gates. Material changes to this notice should receive a revised version and an effective date before use.