App Privacy Policy
Last updated: November 7, 2026
This policy applies to the InterSesh application and early-access product used by clinicians and clients. It explains the information involved in using the application and how to contact us about privacy.
InterSesh is operated by Jamieson D. Cobbs, carrying on business as InterSesh, a sole proprietor. You can contact us at support@getintersesh.com about this website, the application or privacy questions. The Website Privacy Policy covers the public marketing website; the App Privacy Policy covers application accounts and information handled through application features. The Website Terms and App Terms apply to their respective services.
Scope of this policy
InterSesh supports between-session information gathering and clinical workflow. This policy covers application accounts, information entered through application features, and related support communications. The public marketing website, its early-access interest form, and website analytics are covered separately by the Website Privacy Policy. Application use is also subject to the App Terms of Use.
Adult eligibility and current testing access
InterSesh is intended for adult clients. We are preparing an initial paid Canadian release for eligible practitioners and adult clients in British Columbia, Alberta, Saskatchewan, Manitoba, Ontario, New Brunswick, Nova Scotia, Prince Edward Island, Newfoundland and Labrador, Yukon, the Northwest Territories, and Nunavut. Québec is excluded from this initial release. United States clinical use is a separate future initiative requiring its own authorization and applicable safeguards. The initial launch does not support minor or guardian-mediated accounts. Clients must truthfully complete any adult/self-account declaration requested by the application. Clinicians must determine and confirm the age, consent, capacity and authority requirements applicable to the client and their care. These declarations do not independently establish a person's age, capacity or professional registration.
Current GCP staging access is restricted to authorized operators using fictional identities and synthetic client information. Real clinician/client accounts, identifiable client information and external pilot use are not permitted in that environment. Joining the public interest list does not authorize application access. Real-data use requires a separately approved production environment and completed applicable privacy, security, contractual and operating arrangements. Wider international availability will be reviewed as the service expands.
Information users provide
Information may be provided when you create or use an account, set up a practice or test client, enter information through available features, or contact us for help. The information involved depends on the features you use. Please limit support messages to what is needed to explain the issue and do not send passwords or identifiable client information.
Clinician and client account information
Account and profile information may include names, email addresses, professional roles, practice or organization details, account identifiers, organization memberships, and clinician-client assignments. These details support account administration and determine which practice, client, or clinician experience an account can access. All staging account and profile details must remain fictional during current testing.
Clinical and between-session information
Application features can hold client context, Agreements and their schedules, reported outcomes and barriers, check-ins, journal entries, clinical signals and clinician reviews. Reviewed clinical-intelligence functions organize reported evidence deterministically for clinician review; they do not diagnose or replace professional judgment. All current staging identities and client-related content must be fictional.
Access follows organization, assignment and client boundaries. Administrative or billing authority does not automatically grant clinical access. If separately enabled and authorized, Passport allows a client to grant a named receiving practice continuing access to eligible client-level between-session history, including qualifying records created before the connection and under earlier practice relationships. A share does not currently select individual record categories, dates or source practices. Eligible shared goals, homework, Agreements and follow-through events may be changed by appropriately authorized connected clinicians and those changes may be visible to other authorized connections. Another practice's clinician-private notes, treatment plans and practice-scoped private summaries are not automatically transferred. A share link normally expires seven days after creation, but this does not itself terminate a connection already redeemed. A client may revoke ongoing connection access; lawful copies or records previously obtained by a receiving practice are not automatically erased. These features remain subject to release authorization and actual access-scope verification. Clinical content is not used for advertising, cross-organization learning or third-party model training.
Authentication and security information
The authentication service processes the sign-in and session information needed to authenticate accounts and maintain access. The application also uses account identifiers, role information, memberships, and assignments to apply access permissions. Keep credentials private and contact us if you suspect that someone else has accessed your account.
Technical and logging information
Operating the application can involve technical information such as IP addresses, browser or device information, request timestamps, service errors, and account or request identifiers associated with an event. This information may be processed by the application platform to deliver the service, troubleshoot faults, and investigate security issues. The separate Website Privacy Policy describes analytics on the public website; its analytics choices should not be taken as a description of application logging.
Purposes for processing information
Information is processed to provide account access, organize practice and client workflows, store and display information supplied through application features, and produce the summaries and views those features support. It is also used to administer early access, respond to support and privacy requests, diagnose problems, assess feedback, protect the service, and meet applicable legal obligations. The current testing phase is for evaluating the product with fictional client information.
Service providers and subprocessors
The current staging application uses Google Cloud for application hosting, stored information, authentication, secrets and security operations. Identity Platform handles sign-in. Stripe processes practice billing and subscription information in test mode in staging; that flow uses billing-owner and business/subscription metadata and excludes clinical record content. The public marketing website and its ordinary interest form use Netlify. Titan Email processes ordinary correspondence sent to our published contact address. Do not send passwords, patient identifiers, clinical records or full privacy responses through ordinary email or the marketing form; we will arrange restricted follow-up where needed.
Cross-border processing
The verified staging runtime and the main production Cloud SQL database are hosted in Google's Toronto region. Production Cloud SQL automated backups are stored in Google's US multi-region, while a separately created on-demand backup was stored in Toronto. InterSesh has chosen to retain the existing automated backup location, subject to specific applicable legal, professional and customer-contract requirements. Other authentication, billing, email, support and supplier operations can also involve processing outside Canada. Actual production service scope, locations, safeguards and applicable agreements must be verified before real-data use. The current application does not send clinical content to a third-party generative-model service. Additional delivery, push, analytics, support or model flows require review and appropriate disclosure before activation. The current invitation API supplies a link and does not itself send invitation email.
Passport sharing requires the client's recipient-specific choice and independently verified authority for participating practices. Cross-jurisdiction sharing can create additional privacy, professional and contractual duties. InterSesh remains responsible for its own applicable provider obligations, while source and receiving practices remain responsible for the duties applicable to their clinical roles and data. Client consent is not a substitute for mandatory custodian or professional safeguards. A jurisdictional difference alone is not an automatic ban on sharing; applicable authorization and service controls must be verified first.
Security safeguards
The application uses authentication and role- and assignment-based access controls intended to restrict access to authorized users. Privacy and security safeguards are being evaluated during early access. No online service or storage method can be guaranteed completely secure. Users should protect their credentials, sign out on shared devices, and report suspected access problems.
This policy does not assert healthcare compliance or regulatory certification. Production use with identifiable client information depends on completion of the applicable safeguards and arrangements described above.
Retention, account closure and temporary response copies
Retention depends on the information category, purpose, responsible record holder, applicable duties and any justified hold. Practice records, client-controlled Passport information, account references and security/rights evidence can have different requirements. A backup setting does not determine a clinical-record retention period. The applicable production/customer schedules and disposal procedures must be established before real information is accepted.
Settings supports an account-closure request; an unapplied pending request can be cancelled. Fulfillment revokes affected application access and connections, minimizes account/email references and resolves the authentication identity. If a provider step remains unresolved, the request is not marked completed and the access denial remains in place while that step is retried. Billing ownership or sole practice administration must be transferred where those blockers apply. Account closure does not automatically cancel a practice subscription.
Shared clinical and practice records, client profiles and necessary operational, audit or billing references can be retained after closure. Stable identifiers and retained records can still identify a person. A closure outcome records identity/access closure; broader deletion requires its own lawful scope and retention review. Protected backups can retain earlier copies until their applicable expiry, and a restore must apply later closures, revocations, delivery restrictions, holds and cleanup facts before affected access resumes.
Temporary reviewed-response copies are restricted and removed through the controlled cleanup process when eligible. Holds can suspend removal of the affected copy. Cleanup records removal of the active application response copy; it does not establish deletion of primary clinical records, recipient downloads or every backup copy. Necessary minimal request, review, receipt and denial evidence is retained under its own applicable schedule.
Access, correction and retained-record review
The Privacy requests panel lets a signed-in person submit an access request, correction request or retained-record review and check its progress. It initially collects the request type and reference information rather than clinical attachments. The separate self-service account download contains selected eligible information; its technical scope does not determine your legal right to other records or provide a complete practice record set.
We record receipt and review identity, authority, the responsible record holder, requested information, the applicable response deadline and any permitted extension/notice. Practice information, private material, other people's information and applicable access exceptions require appropriate review. Corrections or annotations preserve relevant original history. The response can explain the approved scope, correction, refusal or retention decision and the applicable follow-up or complaint route.
Reviewed application responses are restricted to the verified recipient's sign-in identity and have an availability period. Downloading a response is separate from selecting “I received the response.” Availability can end through expiry, revocation or a hold. If a response is unavailable or another delivery is needed, contact us for a fresh verified review. Expiry or removal of our temporary response copy does not erase a copy already downloaded to your device. Keep downloaded information on a device and in a location you are authorized to use.
If you have closed an account or cannot use its sign-in, contact us with a brief general description that excludes clinical details and credentials. We will arrange identity/authority checks and an appropriate restricted response. A separately verified delivery identity does not recreate the closed application account, relink its client record or restore earlier clinical access.
Incident and breach handling
If we become aware of suspected unauthorized access, loss, or disclosure, we will assess the issue, take appropriate steps to contain and address it, and work with relevant service providers where needed. We will notify affected people, practices, or authorities when required by applicable law. To report a suspected incident, contact us promptly with a description of the issue, without including passwords or identifiable client information.
Changes to this policy
We may update this policy as the application and its information practices develop. The date above identifies the latest revision. We will provide additional notice or seek consent for material changes where required. Publication of an updated policy alone does not lift the synthetic-data restriction; production use with identifiable client information must be explicitly enabled.
Contact
For application privacy questions, access or correction requests, account deletion requests, or suspected privacy incidents, contact InterSesh at support@getintersesh.com.