Provider and contact
From Artur provides Tab Scheduler. For questions about extension data or to make a privacy request, email artur@fromartur.com.
Information stored in your Chrome profile
Tab Scheduler stores routine names, website addresses, schedules, preferences, saved templates, activity records and technical records used to prevent duplicate openings in the extension’s IndexedDB database in your Chrome profile. It also creates a random installation identifier and, after Pro activation, stores a signed license receipt locally.
The Free version requires no account. Routine content and scheduled addresses are not sent to From Artur. The extension does not read destination-page content, collect browsing history, or use advertising or analytics services. When you choose “Use this page”, the activeTab permission lets the popup read the address of the active page so it can be added to a routine.
Local retention, deletion and backups
Completed activity is limited to the most recent 500 attempts and entries from the previous 90 days. Technical occurrence records may remain for up to 180 days to prevent duplicate openings, and short-lived command records are kept for up to seven days. Current or unfinished records may be kept longer until they are resolved.
You can delete routines and clear completed activity in the extension. Clearing activity does not remove the technical records needed for duplicate protection or an opening already in progress. Uninstalling the extension normally removes its local data from that Chrome profile.
An exported backup is a plaintext JSON file containing routines, website addresses, preferences and saved templates. It does not include activity history or license secrets. You choose where the file is stored and when it is deleted.
Pro purchase and information sent to the licensing service
Pro purchase and activation are available only in a build configured with a licensing service. Applying for the initial manual-purchase offer sends your email address and your affirmative consent to be contacted. Applying does not take a payment or guarantee availability. The first ten paid licenses are issued only after the seller manually confirms a direct transfer.
Activation sends the redemption key and the random installation identifier. Validation and deactivation send the signed license receipt, installation identifier and a one-time request value. Routine names, scheduled addresses, templates, activity and browser history are not included in these requests.
This information is used to answer the purchase request, provide and restore the licensed service, bind one license to one Chrome profile, prevent unauthorized use and administer revocation or device resets.
Information stored by the licensing service
The service database stores the purchase-application email and consent, application and order state, offer and price, customer email, a SHA-256 hash of the redemption key, license state, installation binding, issue and status timestamps, a manually entered payment reference, aggregate service counters, and administrative events containing an action, time and license identifier. The plaintext redemption key is shown once when issued and is not stored by the service.
Pending applications and administrative audit entries older than 90 days are removed when the service starts. Paid application and purchased-license records are retained as needed to provide license support and restoration, handle privacy requests and meet applicable record-keeping obligations. Backups of the license database would contain customer emails and the same license records and must be protected by the operator.
Security, service providers and request metadata
Configured license requests use HTTPS. The application server disables its own request logger and does not enable request-body logging. It applies rate limits in memory, which requires processing the requesting IP address while the service is running.
The license service runs on an OVHcloud VPS behind a Caddy reverse proxy at licenses.fromartur.com. The service and this route do not enable request access logs or request-body logs. The database and signing keys are kept in restricted storage on that VPS; restricted backups may contain customer emails and license records. OVHcloud supplies the server and existing mailbox. Its processing and any international transfers are governed by its applicable data-processing terms. Network providers necessarily process connection metadata such as IP address and request time to deliver traffic. We do not intentionally record license keys, receipts, authorization headers or request bodies in access logs.
Legal basis, rights and service availability
Purchase-request processing is used to take steps at your request before a contract. License delivery and validation are used to perform the purchased service, while security and abuse prevention rely on the legitimate interest in protecting the service. Records may also be kept where necessary to meet a legal obligation or establish, exercise or defend legal claims.
You may request access, correction, deletion, restriction or objection by emailing artur@fromartur.com. A request to delete information may not apply to processing that must continue to perform a contract, comply with law or handle legal claims. You may also complain to Portugal’s data-protection authority, CNPD.
A permanent Pro purchase uses a periodically refreshed signed receipt. A valid receipt supports at most seven days of offline Pro access between successful validations. This validation does not transmit routine content or scheduled addresses.
Read the general From Artur Privacy Policy