Your real story deserves clear boundaries.

1. Who is responsible

Within Integration Companion is responsible for the personal information described here. Privacy questions and requests can be sent to admin@withinintegration.com.

2. What we collect

• Account and access information, including an access-code record, chosen name, consent records, dates, package, and any linked provider.
• Information you choose to enter: life-story responses, intentions, preparation choices, notes, journey journal, integration reflections, edits, and requests.
• Optional audio sent for transcription. Within stores the resulting transcript when you choose to save it, not the original audio recording.
• AI-organized drafts, suggestions, meaning possibilities, plans, and generated artwork.
• Optional spoken rehearsal audio generated from relevant confirmed preparation information. Personalized audio is held in the open page for replay and is not added to the saved journey.
• Email and checkout details if you request an invitation or use demo checkout; demo checkout does not charge a card.
• Basic technical and security information produced by the hosting platform. We do not intentionally use journey text for advertising.

3. Why we use it

We use information to provide and secure the one-journey workspace; save and restore progress; personalize prompts; operate optional AI, transcription, spoken rehearsal, illustration, export, provider-booking, and support features; respond to privacy and correction requests; investigate errors or misuse; and meet legal obligations.

We do not use an AI-generated interpretation to make an employment, insurance, credit, medical, or other high-impact decision about you.

4. AI and processing outside Canada

When you use an AI-assisted feature, the relevant content is sent to OpenAI through its API. OpenAI states that API data is not used to train its models by default. Its standard abuse-monitoring process may retain input and output content for up to 30 days, unless different approved controls apply. Processing may occur outside Canada, where information can be subject to local law.

AI can misunderstand, omit, or invent details. Review every organized account or suggestion before relying on it. Memory-like or symbolic material is not proof that an event occurred.

5. Who can access or receive information

• You: through the access code connected to this journey.
• Within operators: only when reasonably needed for support, security, legal duties, or a privacy request. Direct database administrators can technically access stored information.
• Technology providers: hosting, storage, AI, image, transcription, and email providers as needed to operate the selected feature.
• Linked service providers: their portal shows limited account or booking information, not your story, journal, or integration reflections. Sharing an exported summary is your separate choice.
• Legal or safety disclosures: when required or permitted by law.

6. Protecting other people

Please avoid entering another person’s full name, address, workplace, phone number, email, or other identifying details. Use roles or initials such as “my sibling” or “J.” If you include information about someone else, you are responsible for having a reasonable basis to do so.

7. Retention and deletion

Within aims to retain journey content for no longer than 12 months from activation, then place it into a deletion process. A requested deletion may take up to 30 days to complete. Backups, security records, consent records, or transaction records may be kept longer where reasonably necessary or legally required, but should be minimized and separated from journey content.

This pilot currently uses an administrator-reviewed deletion queue. Automated retention enforcement and independent backup verification remain launch-readiness work.

8. Your choices and rights

After signing in, open Privacy & my data to download a copy, request access, request correction, withdraw consent, or request deletion. Withdrawing consent closes access immediately and queues the journey for deletion review. You may also email the privacy contact. Identity may need to be verified before a request is fulfilled.

9. Security and important limits

Within uses secure browser cookies, hashed access codes, encrypted recovery copies of codes, and access controls. Journey content is stored in the hosted database and is not end-to-end encrypted. Anyone with your access code may be able to enter your workspace, so keep it private. No online service can promise zero risk.

10. Consent and changes

Separate consent is requested for storing the sensitive information you enter and for AI processing. Marketing consent is not bundled with entry. If this notice changes in a meaningful way, Within will require a new acknowledgement before further collection or AI processing.

11. Concerns

Contact admin@withinintegration.com first so we can respond. In British Columbia, you may also contact the Office of the Information and Privacy Commissioner for British Columbia ↗.