Aquarian Delicacies privacy notice
Reading this page or signing in does not accept these draft terms. Existing agreements and recorded consents remain unchanged.
This draft describes the observed data flows of the Aquarian Delicacies platform operated by Pacific Alaskan Delicacies Inc. It is available for review and has no effective date. Existing recorded consents and signed commitments are preserved.
Information used by the platform
Account and organization information includes names, contact details, membership, role and permission records. Operational information can include vessels, permits and supporting evidence, schedules, catch estimates, certified weights, rates, agreements, signatures, workforce activity, inventory, custody and delivery records.
Messages, uploaded documents and authorized support actions are retained in their relevant workspaces. Location and map information may be recorded when you use a supported location feature. Exact vessel locations and private operation details are restricted by the applicable permissions.
Authentication, security and delivery systems process technical information needed to sign you in, maintain sessions, diagnose errors and record delivery status. This draft does not claim that advertising analytics, medical records, passport records or unrelated tracking are routinely collected.
Why information is processed
Information supports account security, authorized collaboration, sourcing and service coordination, evidence and document generation, participant communications, support, audit history and retention obligations. Public profiles and published opportunities are intentionally separate from private operation records.
We do not infer consent for a new optional use from your use of an unrelated feature. Any additional processing basis or location-specific rights must be evaluated for the actual services and jurisdictions involved before an effective notice is adopted.
Who receives information
Authorized organization members and operation participants see the information needed for their approved work. Providers receive applicable service information; another buyer’s private bids, unrelated customer lists and private banking instructions are not public marketplace information.
Cloudflare supports application hosting, data and document storage and supported email delivery. Auth0 supports sign-in. Supported messaging uses Twilio within configured pilot and consent limits. Some SMS assistance and quote-extraction features use the OpenAI API. Artemis connects to PAD’s separately operated AI service when available. The active provider inventory and applicable processing agreements require confirmation before this draft becomes effective.
Information may also need to be provided in response to a valid legal obligation or to protect the service against abuse. Any business-transfer handling must preserve applicable confidentiality and legal duties.
Banking and sensitive documents
Supported reusable banking instructions and contract snapshots use application encryption and restricted access. Ordinary records show masked values. Complete instructions are available only through authorized owner or assigned escrow workflows; ordinary administration and represented support sessions are denied that access.
Access restrictions and encryption reduce risk but are not a promise of end-to-end encryption or absolute security. Do not send complete banking instructions through ordinary chat, public fields or AI assistance.
Artemis conversations and memory
Artemis has a separate versioned utilization policy and requires acceptance for the selected person/profile. Supported capture stores accepted text, speech transcriptions, responses and delivery state. Microphone audio is processed temporarily and discarded under the current transcript policy. Cancelled dictation is not saved as conversation history.
Pinned conversations, learned memories, corrections and deletion have distinct controls. Private conversations are not made available to another person merely because that person has an organization role. Optional improvement sharing and model training require separate choices and must not be described as automatically active.
Nightly transcript processing, failure retention and provider recovery limits are explained in the Artemis policy. Withdrawing acceptance stops further Artemis use in that scope; deletion remains a separate available action. Service availability depends on the AI gateway being running.
Retention and your records
Retention depends on record class, operation status, signed commitments, accounting needs and legal holds. The platform includes document schedules, advance notices and hold controls. Finalized financial statements, preserved revisions and their supporting evidence are retained for seven years from the latest financial finalization, extended by applicable holds. This is the platform financial-record retention rule; ordinary operational documents retain their separate schedules. Statements support recordkeeping and do not imply a tax filing or completed payment.
You can export available documents and request correction or review through the contact below. Signed history is preserved through attributable revisions rather than rewritten. Account closure and deletion requests may not remove records another participant is entitled or required to keep.
Provider recovery copies may persist after a deletion. We do not promise instantaneous erasure from backups. An effective notice will confirm the other record-class retention periods and rights-request procedures; the reference document’s generic retention promises are not adopted here.
Cookies and messages
Essential session and security cookies support sign-in and authorized access. Interface preferences may be stored to restore your workspace. This draft does not establish an advertising-cookie program.
SMS/MMS enrollment requires the separate disclosure and consent flow. Supported STOP/revocation controls remain available. Your use of the portal or viewing this notice does not constitute text-message consent. Existing SMS program disclosures and consent records are unchanged.
Questions and corrections
Contact mark@pacificalaskandelicacies.com about access, correction, export, deletion or privacy concerns. We may need to verify the requester’s identity and authority. Pacific Alaskan Delicacies Inc’s proposed notice address is 821 N St Ste 102, Anchorage, AK 99501.
No appointed data protection officer, certification, regular penetration-testing program or specific international-transfer mechanism is claimed by this draft. International service coverage, children’s access and applicable rights must be reviewed before broader rollout. An effective notice will be versioned and announced without silently changing existing consent.
Professional pages, applications and member Community
Publishing a professional person or organization page shares the selected biography, photo, experience, declared work areas, availability and voluntarily selected completed AD trip history with authorized members. Private permits, compensation, banking instructions, precise vessel movements and other trip documents are not added to that page automatically.
An application captures the profile version the applicant reviewed and explicitly agreed to share. Its introduction, resume and preserved application photo are restricted to the applicant and authorized hiring-organization reviewers. Availability and geographic filters assist discovery; they do not make an employment decision.
Community stores text, up to four uploaded photos per post, comments, attributable edits, follows, mutes, blocks, reports and moderation decisions. Removed content and closed reports remain in a private archive. Mutes and blocks are private member preferences. In-app notices inform relevant members; publishing or reporting does not enroll a phone number or send an external email.
Cloudflare D1 stores the structured network records, and protected Cloudflare R2 storage holds profile photos, application evidence and Community media. Auth0 provides sign-in. Community and recruitment do not introduce a new external messaging provider or send resumes to an AI hiring service. The existing optional AI and messaging disclosures remain separate.
Network archive periods and financial protection
The initial recruitment, employment, Community and moderation archive schedules use 24 calendar months after an application closes, employment ends, content is removed or a moderation case closes, respectively. Record-class durations and supported triggers are versioned administrative settings. Administrators may choose the actual closure/removal or the last preserved business record revision; views, downloads, holds and notices do not restart a clock. Changes apply to future closures; changing an existing schedule requires explicit human review and a recorded reason.
Archive schedules, due-review notices and active holds preserve records for review. A notice or acknowledgment does not delete a record. Automatic purge remains disabled pending the separate deletion-policy approval. Closure, removal or Community suspension does not erase signed commitments or financial evidence.
Linked finalized financial statements, preserved revisions, signed agreements, actual travel receipts, approvals and recorded external recovery or return evidence retain their separate seven-year financial protection from the latest financial finalization, extended by applicable holds. Recorded actual employment travel evidence receives a seven-year support floor from its latest financial evidence record while settlement remains unresolved. Reading or downloading a provisional settlement preview does not finalize it or create a retention timestamp. Network periods cannot shorten financial protection. A statement offset, recorded payment or work status does not itself prove funds moved or a tax return was filed.
Permanent voyage reputation and private review evidence
The dedicated voyage-history record is derived from preserved AD participation rather than voluntary profile selection. Unpublishing a biography, hiding a showcase trip, muting or blocking a member does not erase or suppress this professional record. Live and demonstration contexts remain separate, and demonstration feedback is excluded from real rating averages. Unpublished biographies, photos, pay, catch, private rosters, credentials, documents and precise vessel locations are not automatically published with reputation.
Private PDFs and images supplied for attendance reports, disputes or flags are stored in protected Cloudflare R2, with authority checked before storage and retrieval. AD oversight may review case evidence and preserved versions; ordinary members, including the author of moderated wording, cannot retrieve previous moderated versions through history, search, exports or attachments. Restricted Community posting does not remove access to private disputes, employment or financial records.
Voyage participation, reputation entries, replies, revision history, review cases and their supporting evidence use the permanent voyage_history retention mode. They have no deletion date or purge eligibility. Removing or correcting public wording restricts its visibility while preserving the private archive. Existing two-year nonfinancial classes, financial seven-year floors and applicable holds retain their separate rules. This new review draft is not adopted by continued use and does not activate deletion.