Privacy Policy
Delta Sierra Inc.
Last updated: October 29, 2026
Privacy contact: Privacy Officer
Your privacy at a glance
Information and purposes. We handle account and business profile information, funding interests and saved activity, information you submit, and technical usage information to provide, personalize, secure, administer, and support Delta Sierra.
Romeo and AI. Using Romeo can send your question, recent conversation, relevant saved profile information, and portal research context to OpenAI and the systems supporting the service. Saved profile context can include your name and email even when you do not type them into the question. Optional sharing of chat content for additional quality review is a separate choice and is off by default.
Providers and locations. Softr, Airtable, OpenAI, and the hosting infrastructure supporting Romeo process information for relevant service functions. Information may be processed outside Canada, including in the United States. We do not sell personal information.
Your choices and rights. You can manage available profile, alert, browser, and Romeo controls and contact our Privacy Officer about access, correction, consent, deletion, or a complaint. Stopping optional quality sharing, clearing research context, cancelling a subscription, and deleting an account are different actions. The details below explain the distinction.
1. Who we are, scope, and applicable law
1.1 Operator. Delta Sierra Inc. (“Delta Sierra”, “Company”, “we”, “us”, or “our”) operates the Delta Sierra funding intelligence portal at app.deltasierra.co and the related websites, applications, and services that link to or expressly adopt this Policy (“Services”). This Policy describes our handling of personal information in connection with those Services and related customer communications.
1.2 Canadian privacy framework. Our handling of personal information is subject to applicable law, including British Columbia's Personal Information Protection Act (“PIPA”) and the federal Personal Information Protection and Electronic Documents Act (“PIPEDA”) where it applies. Their application depends on the information, activity, and jurisdiction, including relevant interprovincial or international commercial processing. Nothing in this Policy removes a protection, remedy, or duty that the law does not permit us to exclude.
1.3 Personal and business information. Personal information is information about an identifiable individual. A person's account activity, opinions, inferred preferences, or sole-proprietor business details may be personal information even when connected with work. Corporate information, genuinely non-identifying statistics, and business contact information used solely for an exempt business-contact purpose may be treated differently under applicable law. Public accessibility, a coded identifier, or removal of a name does not automatically make information anonymous or unrestricted.
1.4 Other relationships. This Policy does not replace a specific privacy notice or a separately agreed data-processing arrangement that applies to your relationship with us. It does not govern a third party's independent website, professional engagement, or service merely because we link to it. The responsible party's actual role and applicable law determine its obligations.
2. Accountability and privacy contact
2.1 Company responsibility. The Company remains responsible for personal information under its control, including information processed by service providers on its behalf. Using a provider does not transfer away obligations that applicable law places on us. We limit handling to appropriate, identified purposes and apply the safeguards and accountability measures the law requires.
2.2 Contact. Direct privacy questions, requests, incident reports, and complaints to the Privacy Officer, Delta Sierra Inc. at info@deltasierra.co. We can provide information about our privacy practices and complaint process on request. You do not need an active paid subscription to make a privacy request.
3. Information we handle and its sources
3.1 Account and access information. We handle information needed to register, identify, authenticate, and administer users, such as name, email, account identifiers, sign-in and session information, account status, plan, role, access permissions, and verification status where relevant. Authentication information is handled through the sign-in systems used for your account. Do not send passwords or authentication codes through support messages or Romeo.
3.2 Business and Organization profiles. Information may include your title, role, optional telephone number or profile image, Organization name and abbreviation, type, website, city, province or state, country, and relationships with an Organization, advisory firm, or funder. Team features may involve membership, administrator, and permission information. We obtain this information from you, an authorized Organization representative, or the account systems connected to the Services.
3.3 Funding interests and activity. We handle the criteria and activity you provide or generate, including sectors, topics, locations, applicant or business-stage information, project needs, searches, filters, comparisons, saved programs, watchlists, matching results, alert choices, and other available personalization settings. Selecting a topic or a program aimed at a particular group does not, by itself, establish your personal characteristics or eligibility.
3.4 Submitted content and communications. We handle messages, support requests, feedback, notes, documents or attachments where a feature accepts them, and information supplied in a privacy or billing request. Content can contain personal information about you or others depending on what you include. A feature's presence does not authorize submission of information prohibited by Section 17 or the Terms and Conditions.
3.5 AI interactions. When you use Romeo, the service handles questions, responses, relevant conversation history, selected mode, cited sources and suggested actions, current-page context, recent research context where enabled, and any research goal you provide or that is derived from the conversation. It also handles request identifiers, timing, usage and error information, optional ratings and reasons, and optional quality-review content as described in Sections 6 and 7.
3.6 Billing information. Where you purchase Paid Services, we handle the plan, order, subscription, invoice, payment status, transaction references, and billing or tax information needed for the transaction. A payment processor identified in the checkout handles payment credentials through its payment form. Do not put card or bank credentials into ordinary portal fields, uploads, or AI prompts. The specific payment flow determines what the processor and the Company each receive.
3.7 Technical and usage information. The Services and their infrastructure may generate connection and device information, such as IP address, browser or device characteristics, timestamps, page or feature requests, referring information, session identifiers, and diagnostic, security, or performance records. Approximate location may be inferred from connection information. This is different from a promise to collect precise device location; a feature needing additional device permissions must identify that use.
3.8 Public and connected sources. Program, policy, funder, news, and other reference information comes from public or licensed sources and the Company's research. Public reference material can include identifiable individuals' professional details. We handle such personal information under the applicable legal rules rather than treating everything online as freely reusable. If you choose an external sign-in or integration, we receive the information that the feature and your authorization make available.
4. Identified purposes
4.1 Delivering the Services. We use relevant information to create and administer accounts, verify access and plans, maintain profiles and Organization relationships, provide searches and saved activity, generate matches and analytics, deliver requested alerts, respond to inquiries, and perform other functions you request within the available Services.
4.2 Romeo responses. We use the information described in Section 6 to interpret your question, retrieve relevant evidence, personalize an answer, maintain a useful conversation, and suggest relevant portal pages or actions. We also apply usage limits, prevent duplicate or abusive requests, and preserve the history made available to your account.
4.3 Reliability, security, and defined quality work. We use necessary operational information to diagnose errors, measure latency and reliability, enforce access controls, prevent fraud and unauthorized extraction, investigate incidents, and maintain service integrity. Optional ratings help identify answer, retrieval, navigation, and performance problems. Additional review of shared chat content follows the separate choice in Section 7.
4.4 Administration and legal obligations. We use necessary information for orders, payments, accounting, tax and contractual records, consent and preference records, privacy requests, dispute handling, legal compliance, and the establishment, exercise, or defence of lawful rights. These purposes do not authorize unrelated or excessive collection or indefinite retention.
4.5 Communications. We use contact information for requested support, relevant account and service notices, and optional communications on the lawful basis described in Section 13. Account registration alone is not blanket consent to optional marketing or unrelated data uses.
5. Consent, necessity, and choices
5.1 Appropriate basis. Where consent is required, we obtain it in the form appropriate to the information, context, reasonable expectations, and risks. Express consent is used where required, including for sensitive or unexpected processing. Implied or deemed consent is relied on only where the governing law permits it. We may handle information without consent only where a specific legal permission or requirement applies; this Policy is not itself such an exception.
5.2 Necessary and optional processing. Some information is needed for a feature you request, such as an email address for account administration or a question for an AI response. You may decline optional information and uses, although the related optional feature may then be unavailable. We do not require consent to handling beyond what is necessary to supply a product or service as a condition of receiving it where law prohibits that condition.
5.3 Withdrawal. You may withdraw consent on reasonable notice, subject to lawful restrictions, through an available control or by contacting the Privacy Officer. We will explain material consequences, such as loss of the feature that requires the information. Withdrawal does not invalidate prior lawful processing or prevent necessary retention or handling that the law permits independently of consent. It does not authorize us to keep using information for an abandoned purpose.
5.4 Specific choices. Available controls include updating profile information, choosing alerts and optional communications, managing browser storage and permissions, controlling Romeo's recent research context, and choosing optional quality sharing. Where no self-service control addresses your request, contact us. Changing one setting does not automatically change every other purpose or record described in this Policy.
5.5 No blanket or retrospective consent. Reading this Policy, visiting a page, remaining silent, or continuing to use the Services does not supply a consent that the law requires us to obtain separately. We identify materially different purposes and obtain any required new consent before using information for them.
6. Romeo, personalization, and AI processing
6.1 What goes into an AI answer. Romeo uses OpenAI's API and the systems supporting the Delta Sierra service. For an AI-generated response, information sent for processing can include your question, relevant recent questions and answers, retrieved program or other evidence, and saved profile context. In the current implementation, saved profile context can automatically include name, email, title, user role, Organization name or abbreviation, type, website, city, province, and country where available. You need not repeat those details in a prompt for them to be included. Ordinary AI request content is not necessarily redacted before processing.
6.2 Account checks. Romeo checks the authenticated account and relevant access or subscription information to provide the appropriate features, protect conversations, and enforce usage limits. The sign-in systems and chat service handle account and session identifiers for those purposes. Asking a question does not give Romeo authority to share your account with another user or act for you before a funder.
6.3 Current-page and recent research context. Romeo can use the current portal page, selected record identifiers, visible reference text on supported research pages, active tabs, search terms, filters, and selected comparison programs to understand your request. Recent research context is enabled by default and can remember a limited sequence of recently viewed portal detail pages and a research goal. A goal can be inferred from clearly stated project needs in the chat and can be reviewed or corrected in Context & privacy → Research context.
6.4 Meaning of the research controls. The recent-research switch controls the use of prior-page research memory in that browser tab. Turning it off does not, by itself, disable current-page context, the processing of your new question, saved profile context, or existing conversation history. Clearing research context removes that context from the active research session; starting a new conversation or clearing a browser session does not necessarily erase previously stored chat records. Section 14 explains the different retention windows.
6.5 Web research. Where a question calls for external research, Romeo may generate a public search query and use an external search capability through OpenAI. The service applies controls intended to limit identifying information in public search queries, but screening and redaction are not infallible. Do not include confidential information or unnecessary personal details in a request for public web research. Opening an outside source also engages that website's own privacy practices.
6.6 Training and provider retention. We do not use private User Content for unrelated general-purpose model training or fine-tuning without a separate lawful basis and any required consent. Optional quality review under Section 7 evaluates responses; it is not, by itself, permission for unrelated model training. OpenAI states that API data is not used to train its models by default unless the customer opts in. Our current Romeo API requests disable storage of response application state. That setting does not establish Zero Data Retention: provider security, abuse-monitoring, legal, or other applicable retention may still apply, including to content and metadata. Consumer ChatGPT settings are not the controls for this API service.
6.7 Automated results and accuracy. Matches, ranks, eligibility indicators, summaries, and AI responses can involve automated processing and inferences. They support research and planning; they do not constitute a funder's funding decision or an official eligibility determination. Inferences about an identifiable person may themselves be personal information. Review information before relying on it, correct inaccurate profile details, and contact us about inaccurate personal information we hold. AI responses can be wrong even when they contain a citation.
7. Quality review, ratings, and administrator access
7.1 Operational quality information. Romeo records performance and diagnostic information, including request status, mode or intent category, timing, model and tool usage, references to retrieved sources and navigation, and coded identifiers that link records to the relevant account or interaction. It can also record optional ratings and selected reasons. A coded or pseudonymous record is not necessarily anonymous. These records help detect and diagnose specific service problems and evaluate proposed improvements.
7.2 Optional content sharing. The control to share redacted questions, answers, and feedback comments for private AI and administrator quality review is off by default. If you enable it, selected content, related source snapshots, and associated feedback can be processed by automated evaluators, OpenAI, and authorized Company reviewers for that quality purpose. We may derive review findings and proposed improvement or regression examples. Removing identifying details is a best-effort process; do not assume shared text is fully anonymous or include sensitive information unnecessarily.
7.3 Turning sharing off and deleting quality data. In Context & privacy → Privacy & improvement, you can stop optional content sharing and use Delete my quality data. Turning sharing off stops future optional review copies and removes existing review copies and comments handled by that control. The quality deletion control removes the associated ratings, quality metrics, and stored review data and turns content sharing off. New service use can create new necessary operational metrics.
7.4 Separate records. These quality controls do not automatically delete saved conversation history, account or billing records, required security or legal records, or information already processed under a provider's applicable retention rules. Contact us for a broader request. Authorized personnel may separately need limited access to service information for support, security, privacy requests, or legal compliance; optional quality sharing is not blanket permission for unrelated access.
8. Service providers and processing roles
8.1 Current core systems. Relevant providers include Softr for the portal and related account or application functions; Airtable for connected account, profile, Organization, and funding-related records; OpenAI for Romeo's AI and external research capabilities; and OpenAI Sites and Cloudflare infrastructure supporting Romeo's hosting, server processing, and storage. The information each receives depends on the function being used. These names identify the relevant services, not a claim that each receives every category of information.
8.2 Other necessary providers. Relevant functions can also involve website hosting, email delivery and support, workflow automation, security and diagnostics, professional advisors, and a checkout's identified payment processor where payments are offered. We limit information made available for the particular purpose. An optional integration or feature may identify additional recipients when you use it; merely connecting a vendor to a workspace does not mean every user's information is sent to it.
8.3 Protection and independent purposes. For providers acting on our behalf, we require appropriate confidentiality, use restrictions, and safeguards and remain accountable as applicable law requires. Some providers also handle limited information for their own lawful payment, security, fraud-prevention, or account-administration purposes under their applicable notices and obligations. Their independent activities do not excuse our own duties. Contact the Privacy Officer for information about providers relevant to your data or a proposed special use.
9. Organization accounts, advisors, and funders
9.1 Organization visibility. Where team or Organization features are available, authorized administrators and members may see account details, membership, roles, shared activity, or content according to the actual permissions and sharing settings. Confirm what is shared before adding material. Organizations are responsible for the instructions and access they lawfully control; we remain responsible for our own handling and safeguards. Organization membership alone does not create unlimited access to another person's information.
9.2 Advisors and other connections. If you request a referral, introduction, or enabled marketplace connection, we may provide the contact and project information needed for that request as disclosed at the time. The independent advisor or recipient is responsible for its own engagement and privacy practices. We do not treat a directory listing or your interest in a topic as permission to circulate your private profile or project to unrelated providers.
9.3 Funder relationships. Saving, matching, comparing, or asking Romeo about a program does not itself submit an application or notify the funder of your interest. If you choose to visit a funder's website, send an application, or contact another organization, the information you disclose there is handled under that relationship and its notices. We do not control an independent recipient's subsequent lawful obligations or decisions.
10. Legally permitted disclosures and business transfers
10.1 Legal and protective purposes. We may disclose information when required by law, a binding legal process, or a lawful authority, and where a specific legal permission supports matters such as obtaining legal advice, investigating fraud or unlawful conduct, protecting individuals in an emergency, or establishing or defending rights. A request by another person or organization does not, by itself, create a right to receive your information. We assess the applicable basis and limit disclosure accordingly.
10.2 Corporate transactions. A genuine proposed or completed financing, merger, restructuring, or transfer of the relevant business may involve information to the extent applicable law permits. We apply the confidentiality, necessity, use, return or destruction, notice, and consent requirements that govern the transaction. This paragraph is not advance permission to sell personal information as a separate commercial product or to use it for materially unrelated purposes.
11. Cross-border processing and public-sector limits
11.1 Processing locations. The Company is based in British Columbia, Canada. Providers and their authorized support or infrastructure operations may process or store information outside your province or Canada, including in the United States and other jurisdictions used for the applicable service. We do not represent that ordinary portal or Romeo use is Canada-only storage or processing. Ask about the current arrangements before providing information with a binding residency restriction.
11.2 Foreign legal access. Information processed in another country may be subject to that country's laws and lawful access by courts, law-enforcement, or national-security authorities. Contractual safeguards cannot override those laws. We consider the applicable transfer risks and use the protections required for information under our control; cross-border processing does not remove our accountability.
11.3 Special requirements. A public body, regulated organization, or professional user must confirm that its proposed use is authorized under its own privacy, confidentiality, records, security, and procurement requirements. This Policy is not approval for protected or classified government information, a particular certification, or a special data-residency arrangement. Such requirements need an appropriate, expressly agreed arrangement before the information is supplied.
12. Cookies, browser storage, and device choices
12.1 Service functions. The portal uses browser technologies for functions such as sign-in and session security, navigation, preferences, and supported research context. These can include cookies and local or session storage. Romeo's recent research context is held in the browser session and used with the service as described in Section 6. Infrastructure providers may also process technical information needed to deliver and secure a page.
12.2 Optional tracking. Any optional analytics, advertising, recording, or similar tracking that we introduce must be identified with the required information and choices, and obtain consent where required before use. General acceptance of this Policy does not authorize undisclosed tracking. A third-party page or embedded optional service may have its own technology and notices when you choose to use it.
12.3 Browser controls. You can manage cookies, stored site data, and device permissions through your browser or device settings and any relevant service control. Blocking required storage may affect sign-in or other functions. Clearing browser storage does not necessarily delete records already held by the Company or a provider. Browser controls do not replace any consent the Company must obtain or prevent you from contacting us about your rights.
13. Alerts, support, and marketing communications
13.1 Service and requested messages. We use contact information for support you request and relevant account, security, billing, or contractual notices. A message's actual content and the applicable law determine the requirements; calling it a service message does not create an exemption from Canada's anti-spam legislation.
13.2 Optional messages and unsubscribe. Funding alerts, newsletters, promotional updates, or other optional commercial messages are sent on the required consent or other lawful basis. Where required, messages identify the sender and include a readily usable unsubscribe method. You may also contact info@deltasierra.co. Applicable unsubscribe requests are processed without delay and within the legal time limit, including no later than 10 business days where that CASL requirement applies. Necessary lawful account communications may continue.
13.3 Preference records. We may keep the limited information needed to document your choices and respect an unsubscribe or suppression request. A request to stop marketing is not a request to cancel your subscription, and subscription cancellation does not automatically specify every privacy or communication preference.
14. Retention, deletion, and different record types
14.1 General criteria. We retain personal information for the identified purpose and lawful business or legal requirements, considering account activity, service delivery, the sensitivity of the information, accounting and tax duties, consent records, security needs, disputes, and legal preservation. We destroy or de-identify information when its purpose is no longer served and retention is no longer necessary or required. A preservation need must relate to an actual lawful purpose; it is not a blanket justification for indefinite retention.
14.2 Current Romeo history. Saved chat messages are subject to a 30-day rolling window from creation. Conversation listings use a 30-day window based on recent activity; older messages can expire even within an active thread. Expired history is excluded from ordinary retrieval and removed through routine service cleanup. Starting a new chat is different from deleting stored history.
14.3 Current quality records. Optional quality-review copies and feedback comments have a 30-day retention window, measured from the relevant record's creation or update. Associated quality metrics, ratings, and evaluation records generally have a 90-day window. The controls in Section 7 can remove the records they cover sooner. Routine cleanup implements the windows; they are not a promise that every physical backup disappears at an exact moment. Truly non-identifying aggregate insights may be retained for service improvement.
14.4 Recent browser research. The active recent-research context expires after 30 minutes of inactivity in the current implementation and can be cleared using the available research controls. This does not shorten saved chat retention or erase a project need already included in a conversation.
14.5 Records outside those windows. The Romeo periods apply to the specified history and quality datasets. Account and profile records, access and usage records, billing and tax documents, privacy requests, consent preferences, security or legal records, and a provider's own records can follow different lawful retention requirements. For example, where PIPA requires information used to make a decision directly affecting an individual to be kept for at least one year, that requirement takes priority over a shorter ordinary deletion window. Ask us about the records relevant to your request.
14.6 Closure and backups. Account closure, subscription cancellation, content removal, and withdrawal of consent do not all have the same effect. We will assess the scope of your request and applicable retention duties. Backup or recovery copies may persist until removed through the applicable retention process and remain subject to appropriate protection and legal limits. We do not promise immediate erasure of every copy held by an independent recipient or provider.
15. Safeguards and privacy incidents
15.1 Reasonable safeguards. We apply safeguards appropriate to the sensitivity, amount, context, and risks of information under our control, including relevant access restrictions, confidentiality measures, and technical protections. Romeo's stored conversation content and optional content-review payloads use application-level encryption in the current implementation. Encryption or a coded identifier is not a claim that all information is anonymous, inaccessible to authorized processing, or end-to-end encrypted.
15.2 Limits and user responsibilities. No method of transmission, storage, or processing can be guaranteed to prevent every loss or unauthorized access. Use available account security features, protect devices and credentials, check sharing permissions, and report suspected misuse promptly. These responsibilities do not release the Company from its own legal duties or make you automatically responsible for an incident attributable to us.
15.3 Incident handling. When we become aware of a suspected privacy incident, we assess it and take appropriate containment, investigation, mitigation, and response steps. We notify affected people, regulators, or other parties and keep incident records where applicable law requires. Where PIPEDA's breach rules apply, this includes assessing the real risk of significant harm and making required reports and notices as soon as feasible. We do not condition a legally required notice on your acceptance of a release.
16. Access, correction, withdrawal, and complaints
16.1 Request process. Contact the Privacy Officer at info@deltasierra.co, identify the relevant account or relationship, and explain the information or action sought. An authorized representative may act with appropriate authority. We may request proportionate information to verify identity or authority and locate the records. Do not send identification documents, passwords, or unnecessary sensitive details unless a secure and justified method has been arranged.
16.2 Available rights. Subject to the governing law and its exceptions, you may request access to personal information under our control, information about its use and disclosure, correction of inaccurate or incomplete personal information, withdrawal of consent, and deletion or de-identification where appropriate. A deletion request is not an unconditional right to override lawful preservation, another person's rights, or an applicable retention duty. If a correction is not made, we will follow any applicable annotation and explanation requirements.
16.3 Timing and fees. We assist with requests and respond within the applicable statutory period. Access deadlines are generally 30 days calculated under the governing law: PIPA's calculation excludes weekends and statutory holidays, while PIPEDA ordinarily uses calendar days. Lawful extensions or other statutory adjustments may apply, with the required notice. Any legally permitted access fee will be explained and estimated in advance; we do not charge for making a privacy complaint. Account closure or an unpaid invoice does not remove a statutory right.
16.4 Limits and reasons. Applicable law may require or permit withholding particular information, for example to protect another person's information, privilege, security, or an authorized investigation. We apply the actual legal exception, separate releasable information where required, and provide the explanations and review information the law requires. We do not create additional refusal grounds merely by listing them in this Policy.
16.5 Escalation. Raise a concern with our Privacy Officer so we can investigate and respond. You may also seek guidance, review, or a complaint process from the Office of the Information and Privacy Commissioner for British Columbia or the Office of the Privacy Commissioner of Canada, as applicable. Each regulator determines its own jurisdiction and procedures. This Policy does not add a contractual waiting period, require arbitration, prevent a lawful complaint, or take away a legal remedy.
17. Confidential, sensitive, and third-party information
17.1 Minimize what you submit. Provide only information needed for the feature and that you are authorized to have processed. Do not submit government identification numbers, payment credentials, health or biometric information, classified or protected government material, privileged communications, or another person's confidential information unless a feature expressly permits the information and the necessary authority and arrangements are in place. A prompt, support message, or ordinary upload is not a secure channel for every category of information.
17.2 Information about others. If you provide information about colleagues, clients, staff, partners, or another person, give the necessary notices and obtain the authority or consent required for that purpose. An employment, advisory, or government role does not itself authorize disclosure. Your duties supplement, and do not replace, the Company's independent legal responsibilities.
17.3 Confidential business content. We handle non-public User Content consistently with the confidentiality and limited processing provisions of the Terms and Conditions and any applicable signed agreement. Do not assume an AI prompt establishes professional privilege or a separate confidentiality engagement with a third party.
18. Intended users and jurisdictional availability
18.1 Adult business and professional use. Accounts are intended for people with legal capacity who meet the age-of-majority requirement in the Terms and Conditions. The Services are not directed at children. If you believe a child has supplied personal information through the Services, contact the Privacy Officer so we can assess appropriate action under the circumstances and applicable law.
18.2 Availability restrictions. The Terms currently restrict accounts and subscriptions for Quebec residents and Organizations whose head office or principal place of business is in Quebec. That restriction does not erase privacy rights if we nevertheless handle information to which a law applies. Describing a service as business or professional does not, by itself, remove an individual's privacy rights.
19. Changes, contracts, and legal protections
19.1 Policy updates. We may update this Policy as the Services, law, or disclosed practices change and identify the revision date. We provide additional notice of material changes as appropriate and obtain any new consent that the law requires before materially different handling begins. A posted revision is not retroactive consent to an earlier undisclosed use.
19.2 Relationship with the Terms. Our Terms and Conditions address service use, confidentiality, intellectual property, and contractual risk allocation. Any contractual disclaimer or liability limitation applies only where validly agreed and legally effective. It does not authorize unlawful processing, reduce a mandatory privacy duty, limit a regulator's authority, or eliminate a non-waivable remedy. This Policy does not promise perfect security, absolute anonymity, or deletion beyond what it actually describes.
20. Contact the Privacy Officer
Privacy Officer
Delta Sierra Inc.
British Columbia, Canada
For a request or concern, briefly describe the issue, the account or service involved, and the action you seek. We will explain any further information reasonably needed to address it. Any request or notice method required or permitted by applicable law remains available.