Privacy Policy — Portal17 Studio

This policy covers the Portal17 Studio desktop application and portal17studio.com, including its demos and practice sandbox. It applies to all interface languages. “We” refers to the publisher of Portal17 Studio. Services you connect to, the Microsoft Store and this website's hosting provider also have their own privacy policies.

Data stored on your computer

Portal17 Studio processes your automation locally. It does not require a Portal17 account or provide a publisher-operated cloud service for storing your projects.

Projects and data: .portal files contain the nodes, connections, properties, constants and tables you save. Variables are used during execution; exports, downloaded files and other outputs are written to the locations you configure. These files can contain personal or business information handled by your flows.
Preferences and history: the app saves settings, workspace and open-file paths, trigger configuration and execution history in .portal17studio within your Windows user folder. Logs and history can include flow names, paths, timestamps, status and error details.
Browser sessions: automation uses a browser on your computer. If you enable the persistent browser profile, cookies, sign-in sessions and website storage can remain in the local browser-profile folder between runs.

Ordinary project files, settings, exports and logs are not all encrypted by the app. A folder synchronized by OneDrive, another backup service or a shared drive is subject to the access and synchronization settings of that service.

Browser and Windows recording

When you start recording, the enabled browser and/or Windows recorder captures interactions to create editable nodes. Depending on the action, this can include clicks, keystrokes, entered text, selected values, page addresses, application and window names, and control selectors.

Desktop recording can read clipboard content used in recorded copy-and-paste actions and save control image snapshots for selector repair. Screen capture, image extraction and OCR actions also process the content you target. Text and images saved in a flow or output file may contain information visible in the source application.

Recognized password fields are stored through the local Secrets feature and referenced by name in recorded nodes. Other sensitive text, unrecognized password fields and visible information in images are not guaranteed to be concealed. Review recorded flows and images before sharing them.

Passwords, tokens and Secrets

The Secrets feature stores values in the local secrets.dat file using AES-GCM encryption with a randomly generated 256-bit key. The key is stored separately in secret.key in the same user configuration folder. A flow can use a reference such as [secret:name] instead of embedding the value in its .portal file.

The app also uses this store for credentials such as IMAP passwords, webhook signing secrets and Cloudflare tunnel tokens. Secrets are resolved locally when the configured action or service needs them; authentication can then send them to the service you selected.

This storage protects secret values from appearing directly in shared flows when references are used. Someone with access to both the encrypted file and its key can decrypt them. Credentials entered directly into ordinary node properties, constants or exported files may be saved as plain text. Protect access to your Windows account and configuration folder.

Connections you configure

Local execution does not mean that every workflow is offline. Your nodes can send and receive information through the connections you choose:

Websites and APIs: navigation, form entry, file uploads and API calls exchange the addresses, request data, files and authentication information needed for those actions with the destination service.
Databases: SQL actions connect to the database you specify and exchange authentication information, queries and results. That database may be on your computer, on your network or hosted remotely.
Email: Send Email uses your configured SMTP provider. Sender and recipient addresses, message contents and attachments are sent to that provider and the intended recipients.
Files and other programs: flows can read, write or launch resources you select, including shared folders and programs with their own network connections.

These exchanges are part of your automation, not uploads to the Portal17 Studio publisher. The destination's privacy policy, access rules and the connection settings you choose apply to that information.

Triggers, webhooks and background execution

Enabled triggers can monitor the folders, files, applications or email accounts you configure. Outlook and IMAP email triggers can make sender and recipient details, subjects, message bodies and attachment information available to your flow. Trigger settings, checkpoints and execution logs are kept locally.

The webhook listener accepts requests on your own computer. It listens on the local loopback address by default; allowing access from your network is optional. Incoming request bodies, headers and query values can be passed to the flow and handled by its actions.

If you enable a public Cloudflare tunnel, webhook requests travel through Cloudflare to your local listener. This can involve request content, IP addresses and traffic metadata. Both temporary tunnels and tunnels configured through your own Cloudflare account use that provider's infrastructure. See the Cloudflare Privacy Policy.

Optional background execution can keep enabled triggers running after the editor closes. Scheduled flows run through Windows Task Scheduler. Their data handling is the same as when you run the flow manually; closing the editor alone does not disable a background service or a scheduled task.

Diagnostics, screenshots and error reports

The app does not automatically send diagnostic or failure reports to us. Diagnostic tests and execution logs are generated on your computer. A saved diagnostic report can include the app and Windows versions, display and keyboard information, test results and error details. The web connectivity diagnostic makes a request to this website's sandbox.

When an action exhausts its failure handling, the app can create a local report in .portal17studio/reports. It can contain a screenshot of the full desktop across your monitors, a screenshot of the current automated browser page, the page address and title, node properties, error information and details of visible Windows controls.

Some recognized credential property names are masked in the text report. Screenshots and arbitrary text are not guaranteed to be redacted and may include personal or confidential information. Review and redact reports before sending them to anyone. Reports reach us only if you choose to share them, for example with a support request.

Retention and your control

Your saved projects and outputs remain in their chosen locations until you remove them. The local execution history retains up to 300 entries and can be cleared in the app. The app attempts to retain the 20 most recent failure-report folders; separately saved diagnostic reports and other logs may remain until you delete them.

You can stop recording, disable triggers and public tunnels, turn off background execution, remove scheduled Windows tasks, clear execution history, remove saved Secrets, and delete projects, exports, browser-profile data and reports. Close the app and stop its background service before removing its configuration files. Removing a secret's key also prevents the app from decrypting the remaining secrets.

Uninstalling the app should not be relied on to delete every project, output or user configuration file. Deleting local files does not remove copies in backups or data already delivered to a website, database, email recipient or other service; those copies follow the destination's rules.

Microsoft Store and Windows

Microsoft handles Store installation, purchases, updates and related account information. Windows and the Store may also process diagnostic information according to your Microsoft settings. This is separate from the app's local workflow data. See the Microsoft Privacy Statement.

This website, demos and sandbox

portal17studio.com is a static website hosted on GitHub Pages. It has no Portal17 user accounts, advertising trackers or analytics scripts, and its own pages do not set cookies. GitHub logs visitors' IP addresses for security purposes when serving GitHub Pages sites, including visits without a GitHub account. See GitHub Pages data collection and the GitHub Privacy Statement.

The interactive demos, playground and practice sandbox run in your browser. Their practice forms do not submit entered values or selected files to a server; their state resets when you reload. Use sample information for practice. Loading pages, images and the demo video still makes normal requests to the hosting provider.

Links to the Microsoft Store, connected services or other external websites take you to services governed by their own policies.

Contact and information you share

If you email us, we receive your email address, message and any attachments you choose to send. We use that information to respond to your request and handle the related support or privacy issue. Do not include passwords, API keys or unredacted confidential reports.

For questions about this policy or information you have shared directly with us, contact contact@portal17studio.com. You can use the same address to request access to, correction of or deletion of information you have sent us, subject to applicable obligations. We cannot delete data held independently by services you connect to.

Children's privacy

Portal17 Studio is not directed at children under 13. We do not knowingly solicit personal information from children. If you believe a child has sent us personal information, contact us so we can address it.

Changes to this policy

We will update this page when the app's data handling or the website's services change and revise the date above. The current policy describes local storage and the optional connected features available in Portal17 Studio.