Shoyer.Net Privacy Policy
Last updated: October 2, 2026
This policy explains how Shoyer.Net Inc. handles personal information when you use the Shoyer.Net mobile app, website (including its profile-deletion form), administration portal, business workspaces, and related services. It covers the information used to provide those services, who can receive it, and how to exercise your privacy choices.
1 Who we are
Shoyer.Net Inc. ("Shoyer.Net," "we," "us," or "our") operates the Service. Our mailing address is 570 Bay St., Toronto, Ontario M5G 0B2, Canada. Contact our Privacy Officer at admin@shoyer.net.
A business using Shoyer.Net has its own workspace, sometimes called a tenant. You may have a separate membership in more than one business workspace while using the same sign-in identity. The business decides how to manage its customer relationships, staff access, documents, bookings, and other business records.
We are responsible for information we use for our own platform operations. When we store or process a business's customer records on its behalf, the business is responsible for its purposes and instructions, subject to applicable law and our agreement with it. That business may provide an additional privacy notice. You can contact the business or us about information in its workspace.
2 Scope and eligibility
The Service is available to users across Canada and internationally. Features and sign-in methods depend on the business, your role, your device, and the services you choose to use. A category below is collected only when relevant to your use of the Service or information supplied by your business.
SMS and voice-call verification, video uploads, and video conferencing through a third-party provider are planned features. Recording or transcription may also be offered for conferences. The descriptions of these planned features apply when they become available and you use them. Additional notices will identify the providers and relevant choices before information is collected for those features.
The Service is intended for people aged 18 or older. We do not knowingly collect personal information from children using the Service. If you believe a child has provided information contrary to this policy, contact us so we can assess the information and take appropriate steps, including deletion where appropriate.
This policy covers our Service. Payment providers, sign-in providers, communications and conferencing providers, wallet services, and external websites may also process information under their own privacy notices.
3 Personal information we collect
We receive information from you, the business you interact with, other authorized users, providers you choose to use, and your device's interactions with the Service.
| Category | Information and source |
|---|---|
| Account and sign-in | Name, email address, profile image if supplied, account identifiers and status, password hash for password sign-in, and sign-in or verification records. Google or Apple sign-in provides the identity information authorized by the provider, such as a provider identifier, name, and email address. |
| Phone numbers and verification | Your telephone number and country code, supplied by you or the business as part of an account, customer record, or contact request. When SMS or voice verification is enabled, we and the delivery provider may process the destination number, verification message or call prompt, attempt and delivery timestamps, provider reference, and verification result. The provider may also process call connection, duration, and routing information. |
| Business membership | Your business memberships, roles, groups, linked customer or company account, access permissions, and related customer details supplied by you or the business. |
| Support and communications | Support subjects, messages, images, PDF files and other supported attachments, sender details, case status, and timestamps. We also receive information you send to our contact email. |
| Uploaded files and media | PDFs, images, and, when enabled, videos you select and submit; their contents, file names, types, sizes, and upload times. A submitted file can contain additional metadata, such as its author, capture time, or location, if that information is included in the file received by the Service. |
| Video conferences | When enabled, participant names and contact details, meeting identifiers, attendance and connection information, IP addresses and device details, and the audio, video, chat, or screen content you choose to share. If recording or transcription is offered and activated with the required notice and consent, this can also include recordings, transcripts, speaker labels, and related timestamps. |
| Documents and signatures | Document contents, assigned recipients, drawn signature images, signing consent, signing times, document versions, and audit and integrity records. Customer signing also records location information described in section 7. |
| Bookings | Selected services, staff or resources, booking locations and times, reservation status, and the user or customer associated with a reservation. |
| Projects and payments | Project and customer associations, invoice and subscription details, amounts, currency, payment status, transaction references, and external billing identifiers. Payment details submitted through Helcim checkout are processed by Helcim. |
| Posts and interactions | Posts or other content you submit where enabled, comments, likes, author information, and related timestamps and visibility settings. |
| Devices and notifications | App-generated device identifiers, push registration tokens, device platform, manufacturer and model, operating-system and app versions, device name where supplied, notification preferences, and registration or activity timestamps. |
| Wallet passes | Where enabled, pass contents and identifiers, pass status and updates, and Apple Wallet device registration information, including a device library identifier and push token. Pass information depends on what the issuing business includes. |
| Choices and consent | Consent decisions, the type of choice made, when and how it was recorded, and the associated membership and app version. Document acknowledgements also identify the exact document version. With device permission, we record the location details described in section 7 when you agree. |
| Diagnostics and security | IP addresses, browser or device information, request and sign-in logs, error and crash reports, timestamps, and technical context used to troubleshoot problems and protect the Service. |
| Website profile deletion | The account email and sign-in information you provide or authorize through Google or Apple, the business profile involved, CAPTCHA verification information, email-code requests and verification results, your deletion confirmation, and temporary security and session identifiers. Google reCAPTCHA also processes technical information about your browser's interaction with the verification service, as explained in section 4. |
Documents, uploaded media, messages, and conference content can contain sensitive information about you or other people. Share information only when needed for the service and when you have authority to provide it. Review files and their metadata, and consider what your camera, microphone, or shared screen may reveal.
4 Authentication and local storage
For email and password sign-in, the account database stores a salted password hash to verify your password. Google and Apple sign-in use provider-issued identity credentials. The Service also uses session and refresh tokens to maintain authorized access.
If you enable biometric sign-in, your device performs the biometric check. We do not receive or store your fingerprint, facial scan, or biometric template. The app receives the authentication result. A drawn signature submitted for document signing is separate from device biometric authentication.
The app stores session credentials using device secure storage and keeps settings, cached business content, files, and notifications on your device to support normal operation. The administration portal uses cookies and browser storage for sign-in, security, and interface preferences. Clearing this storage may sign you out or reset preferences.
Website deletion, verification and cookies
The website profile-deletion form uses security and session cookies to protect form submissions, complete Google or Apple sign-in, and keep you signed in during deletion. Your authenticated deletion session expires within 20 minutes, or sooner if it ends or the underlying authorization expires. The website retains the session's account email and authorization credentials on its server; its session cookie contains a random identifier. Your password and the email verification code are not retained as part of that session. These session limits do not determine how long separate authentication, security or business records are retained.
If you choose password sign-in, the website passes your sign-in details to our authentication service. If you choose Google or Apple, you sign in on the provider's page and authorize it to return identity information to us; you do not enter that provider's password into our deletion form. The separate email-code step checks access to your account email before you confirm deletion.
We use Google reCAPTCHA to protect the website form against automated requests, fraud and abuse. Loading and using the verification service sends technical information, such as your IP address, browser information and verification interactions, to Google. reCAPTCHA uses a cookie for its security analysis, and we receive and validate a verification result. Google processes reCAPTCHA customer data on our behalf under the applicable Google Cloud Data Processing Addendum and service-specific terms. This security processing is separate from Google or Apple account sign-in.
Blocking the required cookies or scripts may prevent the online form from working. You can instead use Delete Profile in the mobile app or contact us for help or to make a privacy request. You do not need to complete the website CAPTCHA or sign in to send us an email request.
Website cookies and privacy choices
Our public website uses an opt-in choice for optional analytics and external media for all visitors, including visitors in Canada, the United States, the EEA, the United Kingdom and Switzerland. Browsing, scrolling or closing the preferences window is not permission. You can select Reject optional, accept optional services, or choose Google Analytics and Google Maps separately. Refusing does not prevent access to the website, contact information or privacy-request channels.
| Category | Purpose, provider and duration |
|---|---|
| Necessary preferences | The browser-local storage entry shoyernet.website.privacy records the categories you selected, whether you opted out, the notice revision, language, choice time and expiry time. It is not used as an analytics identifier. We remember accept and reject choices for 180 days and request a new choice after expiry or a change to the notice revision. This entry is stored in your browser; it is not a central server consent log. Choices are specific to a browser and device. |
| Requested-service security | Website sign-in and profile-deletion services may use temporary session, authentication-correlation and antiforgery cookies. Google reCAPTCHA protects requested forms against automated misuse, as described in section 4. These security functions are separate from optional Analytics and Maps preferences. |
| Optional analytics | With your permission, Google Analytics 4 receives cookie identifiers, public-page visit information, browser/device details and network information to measure website use. Google receives your IP address when contacted and processes it according to its Analytics practices. Its script is blocked until analytics is allowed; rejecting analytics does not send a cookieless consent ping to Google Analytics. Analytics cookies such as _ga and _ga_QN211R17JX are configured for a maximum of 180 days without extending their expiry on each visit. Website advertising storage, Google Signals and advertising personalization are disabled. Our explicit page-view events omit URL query strings and fragments, and our tag does not load on the profile-deletion/sign-in flow. See Google's Privacy Policy and Google Analytics data practices. |
| Optional external media | The Google Maps embedded office map stays blocked until external media is allowed, either in preferences or through the button on the map placeholder. Loading the map sends your IP address and browser information to Google. Google can use its own cookies, whose duration and handling follow its policies; third-party cookies cannot all be cleared by our website. Directions remain available through a separate external link, which opens Google Maps when you choose it. |
Change or withdraw your choice: use Cookie settings, available at the bottom of the website and in its footer. Turning analytics off stops the tag, removes accessible first-party Analytics cookies and reloads the page to unload the running library. Turning external media off removes the embedded map. Withdrawal affects future use; it does not erase information already sent to a provider. Contact our Privacy Officer for access or deletion requests, as described below.
US opt-outs and browser signals: the public website's advertising tags, advertising personalization and sale/sharing for targeted advertising are disabled. Do Not Sell or Share My Personal Information turns off both optional website categories in one action without requiring an account or identity verification. We recognize Global Privacy Control through the browser signal or the Sec-GPC: 1 request header and conservatively keep Analytics and external media off while the signal is present. Removing that signal does not automatically turn previously refused services back on. These controls concern website tracking; contact us for other privacy rights, including rights or appeals available under your applicable US state law. We will assess and respond under the applicable requirements.
Google may process Analytics and Maps information outside your province or country, including in the United States. Optional processing is based on your permission where consent is required. International-transfer obligations and provider arrangements also apply; see section 9 and contact our Privacy Officer for information about relevant safeguards. Browser cookie expiry is separate from provider retention of information already received.
Résumé en français — témoins et choix sur le site Web
Le stockage nécessaire mémorise votre choix de confidentialité et protège les services demandés. Google Analytics et la carte Google Maps sont facultatifs et restent bloqués jusqu’à votre autorisation. Analytics reçoit des identifiants de témoins et des renseignements sur les visites, le navigateur et l’appareil; Maps reçoit notamment l’adresse IP et des renseignements sur le navigateur. Google peut traiter ces données hors de votre province ou de votre pays, notamment aux États-Unis. Vous pouvez refuser les options, choisir chaque catégorie séparément ou modifier votre choix dans Préférences de témoins. Les choix sont mémorisés pendant 180 jours dans ce navigateur. Les signaux publicitaires et la personnalisation publicitaire sont désactivés. Le signal Global Privacy Control maintient les services facultatifs désactivés. Le retrait arrête les utilisations futures; il ne supprime pas les données déjà reçues par un fournisseur. Pour exercer vos droits ou obtenir des renseignements sur les transferts et la conservation, contactez notre responsable de la protection des renseignements personnels à admin@shoyer.net.
5 How we use personal information
We use personal information to provide account access and the features you or your business use, including customer support, document delivery and signing, bookings, projects, billing, content, and wallet passes. We also use it to send verification codes and service notices, manage permissions and consent, diagnose errors, protect accounts, and maintain records needed for business transactions or legal obligations.
When the planned features are enabled, we will use telephone numbers to deliver verification codes or calls for the process you are completing and to record the result. Uploaded files and media will support the transaction, document, or support interaction for which you submit them. Conference information will be used to arrange and conduct meetings, manage participation, and troubleshoot connections. Any recording or transcription will have a purpose explained before it begins, such as creating a meeting record or making the discussion accessible to authorized participants.
Where optional marketing communications are offered, the applicable choices are separate from operational communications such as verification codes, booking changes, and document notices. Turning off optional marketing does not prevent necessary service communications.
Providing a telephone number for verification does not by itself authorize unrelated marketing texts or calls. Any marketing use is subject to separate applicable choices and legal requirements.
Where a legal basis is required, the relevant basis depends on the purpose: providing a service you request and performing an applicable contract; consent for activities that require it; legitimate interests in operating, supporting, and securing the Service where permitted; or compliance with legal obligations. For business-controlled records, the business determines the appropriate basis for its processing. Section 13 explains additional rights where European or UK law applies.
6 Diagnostics and crash reporting
We use Sentry to receive error and crash reports and technical context that helps investigate problems. Reports may contain app and operating-system details, error messages, stack traces, network information, timestamps, and events leading up to an error. Depending on the event, diagnostic information may include identifiers or information appearing in an error.
Sentry crash reporting starts with the app and currently has no dedicated in-app opt-out. Notification settings do not control crash reporting. Contact us if you want information about diagnostic records associated with you or to exercise a right available under applicable law.
Our servers also keep operational and security records, including sign-in attempts and request information. These records help us detect misuse, investigate incidents, and maintain the Service.
7 Device permissions and notifications
Location when acknowledging legal documents
When you agree to a required document in the mobile app, we record the document version and acceptance time. If you allow location access and a current reading is available, we also record latitude, longitude, reported accuracy, and the location capture time as evidence associated with that acknowledgement. You can accept without coordinates if permission is denied or location is unavailable; we record that status instead. This does not enable continuous background tracking.
Precise location when signing
When you sign a document as a customer, the mobile app requests a current, precise location reading while you use the signing feature. The signing record includes latitude, longitude, reported accuracy, capture time, and related device location-status information. This supports evidence of where and when the signature was made. This signing feature does not require continuous background location tracking.
Location details are saved with the signature and embedded in the signed PDF. Authorized recipients and anyone to whom they provide a copy may be able to read those details. When the business enables address lookup, signing coordinates are sent to Google Maps Geocoding to obtain an address, which can also appear in the signing evidence. Company-side signatures can use the business's configured office location.
You can deny or revoke location permission through device settings. The current customer-signing workflow cannot complete a new signature without the required precise location reading. Other features remain available subject to their own requirements. Revoking permission does not remove location already recorded in a signed document or copies held by recipients.
Push notifications
We use Firebase Cloud Messaging and the relevant platform notification services to deliver business updates, support replies, document notices, and booking or other service notifications. A registration token and device information identify where to send them. You can manage notifications through the app where available and through device settings.
Notification previews may show message or business information on your lock screen. Your device settings control how previews appear. Disabling notifications does not delete your membership or prevent records from being available inside the Service.
SMS and voice-call verification
When offered, a verification flow may ask for your telephone number and let you request a text message or voice call containing a code or instructions. We will explain the process being verified when the number is requested. The number and information needed to deliver and confirm the verification will be shared with the selected communications provider and relevant telecommunications carriers.
You can decline to provide a number or request a verification message or call, but a process that requires phone verification may not be completed unless an alternative is offered. Notification permission does not control incoming SMS messages or ordinary telephone calls. Carrier charges may apply. Receiving a verification call is separate from enabling the app's microphone for a conference.
PDF files and image and video uploads
You can choose supported PDFs and images from your device; video uploads are planned. The app may open your device's file or media picker or request the relevant file, photo, or media permission. You choose the content to submit. This access is for selecting and uploading content and does not authorize remote control of your device or access to unrelated files, messages, or contacts.
You can cancel selection, decline a permission request, or change access in device settings. This may prevent an upload but does not automatically prevent use of unrelated features. Revoking access stops future access covered by that permission; it does not delete files already uploaded or copies received by others. Uploaded media may include embedded metadata as described in section 3.
Video conferencing and device permissions
When available, conferences will use a third-party conferencing service, which may open within the app or in a separate app or browser. The provider and a link to its privacy notice will be identified before you join. The provider processes the information needed to connect participants and deliver the features used in that meeting.
You may be asked to allow camera or microphone access to send live video or audio. You can decline or revoke that access, mute the microphone, or turn off the camera using the controls available in your device or meeting interface. Declining may limit participation or prevent joining, depending on the provider. Screen sharing, where offered, lets other participants and the provider receive the content you choose to share; check the selected window or screen before starting.
Conference recording and transcription
Recording or transcription may be offered. Before either starts, participants will receive notice of what will be captured, its purpose, who can access the result, and the applicable retention arrangements, and any consent required by law will be obtained. Permission to use a camera or microphone is separate from permission to record or transcribe a meeting. This privacy policy alone is not a request for recording consent.
A recording or transcript can include your voice, image, display name, shared content, and information about other people mentioned during the meeting. The business hosting the meeting and other authorized recipients identified in the meeting notice may receive it. You can decline recording or transcription and ask the host whether an alternative is available; an unrecorded alternative is not guaranteed. Revoking device permission or leaving a meeting does not erase content already captured. Requests about existing recordings or transcripts can be sent to the host or our Privacy Officer.
Wallet features
If you add a pass to Apple Wallet or Google Wallet, the pass and related technical information are processed by that wallet service. Wallet updates and registration are separate from the app's ordinary push notifications.
8 When we disclose personal information
We do not sell personal information. We disclose information as needed for the purposes described in this policy and where permitted or required by law.
Businesses and other authorized users
The relevant business's authorized administrators and staff can access information needed for their roles. A support conversation may be shared with other active users linked to the same customer or company account, as well as the business's support staff. It should not be treated as a private conversation with only one employee.
Posts, comments, likes, and author details are visible to the audience permitted by the business's access settings. Signing documents have their own access permissions; access to a support conversation does not by itself grant access to an attached signing document. A person who lawfully downloads or receives a document can retain a copy outside our Service.
Uploaded PDFs, images, and videos are available to the recipients authorized for the feature where you submit them. In a conference, participants can see or hear the information you share. The host and conferencing provider may receive attendance and connection details. Recordings and transcripts, if enabled, have the recipients described in the notice given for that meeting. Participants may retain information they receive outside the Service; use care when sharing sensitive content.
Providers used by the Service
- Google Cloud provides hosting, databases, file storage, and related infrastructure.
- Firebase Cloud Messaging and Apple notification services process registration and notification information for delivery.
- Google and Apple sign-in process authentication information when you choose those methods.
- Google reCAPTCHA processes website verification information to help us prevent automated misuse, fraud and abuse, as described in section 4.
- Google Analytics and Google Maps embedded media process optional public-website information only when the corresponding category is allowed, as described under website cookies and privacy choices.
- Sentry processes diagnostics and crash-report information.
- Elastic Email processes recipient details and email content for messages sent through that provider.
- Helcim processes checkout, customer billing, invoice, and subscription information when a business enables those features.
- Google Maps Geocoding processes location or address information when signing address lookup or office-location setup is enabled.
- Apple Wallet and Google Wallet process pass information when a business offers wallet features and you use them.
- SMS and voice verification providers and telecommunications carriers will process phone numbers, verification messages or call prompts, and delivery or call information when those planned features are enabled.
- Video conferencing and transcription providers will process meeting and participant information and the content shared through the conferencing features used. This includes recordings or transcripts only where those features are enabled with the applicable notice and consent.
The providers used for a particular business or feature depend on its configuration. Providers may have independent obligations and purposes under their own privacy notices, especially when you use your own provider account.
The SMS, voice verification, and conferencing providers have not yet been selected. We will identify the relevant providers and update the applicable notices before those features collect information. Their inclusion here describes the planned service, not an active integration.
Other disclosures
We may disclose information when you direct us to do so, to comply with a lawful request or legal obligation, to investigate fraud or security incidents, or to protect rights and safety where permitted by law. Information may also be transferred in a business transaction, such as a merger or sale, subject to applicable confidentiality and privacy requirements.
Opening an external link or loading media hosted by another provider can disclose your IP address and device or browser information to that provider. Its handling of those interactions is governed by its own privacy notice.
9 International processing
Shoyer.Net is based in Canada. Information may be processed in Canada, the United States, and other countries where our providers operate. We do not promise that all information remains in your province or country. Processing locations can differ by service, including hosting, email delivery, diagnostics, authentication, and payments, and, when enabled, SMS, voice verification, conferencing, recording, and transcription.
Information processed abroad may be subject to different laws and lawful access by courts or public authorities in those jurisdictions. We remain accountable for information under our control as required by applicable law. International processing is subject to the protections and transfer requirements that apply to the information. Contact us for information about the locations and safeguards relevant to your use of the Service.
10 Retention and profile deletion
Retention of records
Retention depends on the information, the business relationship, the purpose for which a record is needed, and applicable obligations. Relevant factors include operating an active account, fulfilling a transaction or support request, preserving signed-document evidence, accounting requirements, security investigations, and resolving disputes.
There is no single automatic deletion period covering all records. Business records can remain after a membership ends. Logs, diagnostic reports, provider-held records, and backups may have different retention arrangements. Contact us or the relevant business about a particular record or to request deletion; we will assess whether it still needs to be retained under applicable requirements.
Phone numbers and uploaded files may be retained as part of the relevant account, customer record, or business interaction. For the planned verification and conferencing features, the relevant notice will describe retention of verification records, meeting information, and any recordings or transcripts before the feature is used. Leaving a meeting or revoking a file, camera, or microphone permission does not erase records already held by the Service, the business, or a provider.
Deleting a business profile in the app or on the website
Delete Profile removes your membership in one business, rather than your shared Shoyer.Net account. In the mobile app, use Settings → Delete profile for the currently selected business. You can also use the website profile-deletion form to remove your profile with Shoyer.Net Inc., the business identified on that form, without reinstalling the app.
On the website, complete reCAPTCHA and sign in with your existing email and password, Google account or Apple account using the same method you use for Shoyer.Net. Then request the email verification code, review the stated effects, and enter the code and explicit deletion confirmation. Opening the page, signing in or requesting a code does not itself delete your profile. An administrator or employee may need to have a protected role reassigned before removal can proceed. If you cannot use the form or access your account email, contact admin@shoyer.net for assistance.
When removal succeeds through either route, the Service removes that membership and its recorded consent entries, revokes its refresh tokens, and disables its app device registrations and push opt-in. The device-registration records are marked inactive; the records and stored push tokens are not immediately erased. Deletion completed in the app also clears its local sign-in state and local profile content as part of the reset. Website deletion ends the website deletion session but cannot clear content already stored on your phone or other devices.
Your shared sign-in identity and memberships with other businesses remain. Historical business records, including support messages and attachments, signed documents and signing evidence, invoices, subscriptions, and reservation records, are not automatically erased by this action. Certain links to your removed membership or user account are detached, but retained records may still contain your name or other personal information.
Deleting a profile does not cancel a booking, payment obligation, or recurring subscription. Manage these separately with the relevant business or through the available cancellation controls. Wallet passes and their registrations are also separate; removing an app membership does not automatically remove a pass already saved to your wallet.
Rejoining creates a new business membership and may require the device to register for notifications again. It does not automatically restore access to all earlier documents or reservations.
Requesting broader account or data deletion
To request deletion of your shared account, information across multiple businesses, or retained personal information, follow the whole-account and data-deletion request process or email admin@shoyer.net with the subject "Privacy deletion request." You can send this request without signing into the app or website, completing CAPTCHA, or deleting each business profile first. Identify your account email, relevant business, and the scope of your request. Do not send passwords, verification codes or unnecessary identity documents.
We may verify your identity and work with the business responsible for its records. We will explain the result, including any information retained and the reason, subject to applicable law. There is no promise of immediate erasure of all data through the app, the website profile-deletion form or an email request. Copies previously downloaded by others and information independently controlled by providers may require a separate request to their holder.
A business may enable removal of inactive memberships. If enabled, its configured inactivity period and advance reminders apply. The applicable period is described in the notices sent by that business.
11 Security
Safeguards in the Service include password hashing, authenticated access, business and role-based access controls, protected credential storage, and restrictions on access to stored files. Access to support content and signing records is checked against the relevant business and user permissions.
No system can guarantee absolute security. Keep your device and sign-in details secure, use the device's screen-lock controls, and avoid sharing sensitive information unnecessarily. If a privacy breach occurs, we will investigate and provide notices where required by applicable law.
12 Your choices and rights
You can manage device permissions, notification settings, and available in-app choices. You can also contact us to request access to your personal information, corrections, information about its use or disclosure, or deletion. Depending on applicable law, you may have additional rights to receive information in a portable format, restrict or object to processing, withdraw consent, or challenge a privacy decision.
In Canada, applicable rights and responsibilities may arise under federal or provincial privacy laws, including the laws of Quebec, Alberta, and British Columbia where they apply. Rights and exceptions depend on the information and circumstances. This policy does not limit rights provided by law.
Send requests to admin@shoyer.net. We may need enough information to verify your identity and locate the relevant records. We will respond within the period required by applicable law and explain any applicable limits, extensions, or refusal. Where another business controls the records, we may refer the request to that business or assist it in responding.
You may withdraw consent for processing that relies on consent. Withdrawal does not undo earlier lawful processing, and some requested features may no longer be available. For example, denying precise location prevents completion of a new customer signature in the current signing flow. Withdrawing notification permission does not erase earlier notifications or signing records.
When phone verification or conferencing is available, you may also request correction or deletion of a phone number or associated verification records, meeting information, recordings, or transcripts, subject to applicable requirements. To stop sharing live audio, video, or screen content, use the meeting controls or leave the meeting. To request deletion of material already captured or uploaded, contact us or the business responsible for the record.
13 Users in the EEA and United Kingdom
Where European Economic Area or UK data-protection law applies, Shoyer.Net Inc. acts as controller for processing it determines for its own platform operations. A business normally acts as controller for its customer records and the purposes it determines; we process those records on its behalf to the extent set out in our agreement and applicable law.
Subject to the conditions and exceptions in applicable law, you may request access, correction, erasure, restriction, or portability, and object to processing based on legitimate interests. You may withdraw consent at any time for processing based on consent. You may object to direct marketing and complain to the relevant supervisory authority, including where you live or work.
Contact our Privacy Officer for the legal basis applicable to a particular use, information about a relevant legitimate-interest assessment, or the safeguards applicable to an international transfer. Supplying information required for a requested service is necessary to provide that service; optional permissions and choices have the effects explained in this policy.
14 Changes to this policy
We may update this policy as the Service or our practices change. We will publish the revised policy with a new "Last updated" date and provide additional notice or obtain consent where required by law. A revised policy does not replace any consent required for a new use of personal information.
15 Contact and complaints
Privacy OfficerShoyer.Net Inc.
570 Bay St.
Toronto, Ontario M5G 0B2
Canada
Email: admin@shoyer.net
Please identify the business workspace and your account email when relevant to a request. We will review privacy questions and complaints and respond as required by applicable law. You may also contact the Office of the Privacy Commissioner of Canada, the applicable provincial privacy regulator, or the privacy authority in your jurisdiction.
