Rasta Privacy Policy
Last updated: October 26, 2026
Applies to: Rasta – Persian Experience for Jira & Confluence, version 1.2.16
1. About Rasta
Rasta is an independent browser extension that improves Persian and right-to-left (RTL) presentation in Jira and Confluence, including Persian fonts, date display, and optional Jalali date input. Rasta is not affiliated with or endorsed by Atlassian.
2. Site access and on-page processing
Rasta operates on a Jira or Confluence site only after you explicitly add or activate its domain and approve the browser's site-access permission. Because users may host Jira or Confluence on their own domains, Rasta can request access to a user-selected HTTP or HTTPS domain. It does not automatically activate on unrelated websites.
On approved sites, Rasta reads and processes the portions of page content needed for its features—for example, visible text, text direction, issue/table labels and dates, page elements, and date input values. This content may incidentally contain names, issue details, or other information present in your Jira or Confluence instance. Processing occurs in the browser to adjust presentation or help you select and enter Jalali dates; Rasta does not build a database of that page content or send it to the Rasta developer.
When you use a date-input feature, Rasta may update date fields and dispatch the normal events expected by Jira. Any resulting save or submission is handled by your Jira instance under its own policies; Rasta does not separately upload those form values.
3. Information stored by Rasta
Rasta stores the following information using Chrome's extension storage:
- Chrome storage sync (
chrome.storage.sync): the site domains you choose to enable; whether each site is Jira or Confluence; and your selected feature settings, such as RTL/mixed-text display, Persian fonts, date display and picker, interface theme, and colors. Settings from older versions may be migrated to the current format. - Local extension storage (
chrome.storage.local): a temporary pending site activation record (selected domain, site type, timestamp, and a random request identifier), used to complete permission requests even if the popup closes. It is removed when activation is completed or canceled, or treated as expired after a short interval.
Rasta does not intentionally store page bodies, issue descriptions, messages, credentials, cookies, browser history, or entered date values in its extension storage.
4. Data sharing and network activity
The reviewed version of Rasta has no built-in analytics, advertising trackers, or developer-operated data collection endpoint and does not send page contents or saved settings to a Rasta-operated server. Its scripts, fonts, and date-picker library are bundled with the extension rather than fetched as executable code from an external service.
Because Rasta uses chrome.storage.sync, Chrome may synchronize your saved settings and approved site domains through Google's browser synchronization infrastructure, depending on your Chrome configuration. Google's handling of that synchronization is governed by its own terms and privacy policies. Rasta does not control that service.
Rasta works within Jira and Confluence sites you choose. Those websites may themselves send or store information as you use them; their operators' policies, not this policy, govern that activity. Rasta does not sell user data or share page data with advertisers or data brokers.
5. Permissions
storage: save your preferences and explicitly configured sites, and temporarily record pending activation.activeTab: inspect the current tab's URL after you open the popup so you can select the site to enable.scripting: apply bundled layout and date scripts on approved Jira/Confluence domains.offscreen: detect the browser's light/dark color preference for the toolbar icon.- Optional site access (
*://*/*): support user-specified Jira/Confluence hostnames. Access for an individual hostname is requested when you choose to enable it; the wildcard is not automatically granted for every website.
6. Your choices and deletion
You may disable individual features in Rasta's popup or settings. You can remove an approved domain in the extension's Options page; Rasta attempts to revoke its no-longer-needed site permission and unregister its scripts. You can also manage site permissions in Chrome or uninstall Rasta. Removing a domain does not automatically erase unrelated preferences, and Chrome-synced settings may remain subject to Chrome's own synchronization and retention behavior.
7. Security and retention
Rasta limits its functionality to configured sites and uses Chrome's permission and extension storage APIs. Site configuration and preferences remain stored until you change or remove them, reset the relevant browser/extension storage, or uninstall the extension, subject to Chrome Sync behavior. Rasta does not maintain a developer-controlled user-data repository or retention schedule for page content.
8. Children, policy updates, and contact
Rasta is a productivity/accessibility enhancement, not a service directed at children. We may update this policy when the extension's functionality or data practices change, and will update the date above. For privacy questions, contact reza.roohafza1998@gmail.com.
9. Chrome Web Store Limited Use
Rasta's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. User data is used only to provide or improve the extension's disclosed functionality and is not sold or used for personalized advertising or creditworthiness decisions.