1. Who we are
saidweekly is operated by Martin Miller Software Consulting LLC, doing business as saidweekly, located at 8428 Wiese Rd, Brecksville, OH 44141 (“saidweekly,” “we,” “us,” or “our”).
This Privacy Policy explains how we collect, use, disclose, retain, and protect personal information when you visit our website, purchase or use saidweekly, enroll a WordPress website, or contact us.
saidweekly provides a WordPress plugin supported by cloud services that research and plan editorial content and generate articles for an enrolled website. Our Terms of Service separately govern use of the service.
2. Your website’s content
Your website’s content belongs to you. Your WordPress installation is the persistent store for the content and editorial configuration used by saidweekly.
To perform research, create an editorial calendar, or generate an article, our cloud service temporarily processes information obtained from your website. Relevant information is also sent to the providers involved in that operation.
Our generation service does not persist the following in databases, object storage, caches, queue payloads, retry records, logs, traces, analytics, error reports, backups, or model stores that we control:
- Your brand profile and confirmed business facts.
- Research findings, sources, and existing-content analysis.
- Topics, descriptions, keywords, and calendar entries.
- Publication dates, scheduling preferences, revisions, and topic locks.
- Generation inputs and outputs.
- Articles, titles, descriptions, metadata, and article-to-post mappings.
- Images, publication state, and content history.
We retain the limited account, billing, usage, and operational information described below. If you voluntarily include content in a support message, that content may remain in our support mailbox under the support retention period.
Our providers have their own processing and retention practices. Content therefore leaves WordPress during processing, and provider-held copies may remain after an operation ends.
We do not maintain a recoverable archive of your articles, research, or calendar. If your website loses that material, we cannot restore it from our systems. You are responsible for backing up your WordPress installation.
3. Information we collect
Account and installation information
We collect and retain information needed to establish your account and connect your website, including:
- Your name, business name, and email address.
- The address of your enrolled website.
- Customer, license, subscription, and installation identifiers.
- Account and installation status.
- Authentication information needed to communicate securely with your installation.
- Records of administrative changes affecting your account.
License keys are stored in our account systems as one-way hashes rather than recoverable plaintext. A license key is also delivered by email and may remain in the email systems involved in that delivery.
Billing and subscription information
Payments are processed by Stripe. We do not receive or store your payment-card number, security code, or bank-account details.
From Stripe, we receive and retain:
- Your email address and the name and business name you enter at checkout.
- Stripe identifiers for your customer account and subscription.
- Your plan, subscription status, billing-period dates, and automatic-renewal status.
- The amount before tax associated with purchases, renewals, upgrades, top-ups, and refunds.
We use these records to administer subscriptions, calculate credits and refunds, and reconcile transactions.
Your billing address, tax information, payment method, and invoices remain with Stripe. Authorized staff may view invoices and payment status in Stripe when assisting you, but we do not copy those documents into our application database. For staff-assisted orders, billing details are entered directly into Stripe.
If you include billing information in a support message, that message is handled under the support practices described in this policy.
Usage and operational information
We retain limited information needed to operate and account for the service, including:
- Numeric credit grants, reservations, balances, adjustments, and expiration dates.
- Research and calendar quota counters.
- Counts of articles and other operations.
- Opaque operation identifiers, timestamps, statuses, and error codes.
- Token usage and cost measurements.
- Connection and authentication status.
- Records of administrative actions affecting accounts, licenses, subscriptions, or credits.
These records do not contain article bodies, topics, research findings, or brand profiles.
Network and security information
When a browser or website connects to our cloud service, Google Cloud records standard request information, including IP address, browser or software identifier, requested address, request time, and response status.
Our application logs identify websites and operations by internal identifiers rather than by customer name or content. Email-delivery log entries record the domain portion of the recipient’s email address rather than the complete address.
We can access these logs and use them to operate, secure, and troubleshoot the service. Request and application logs are automatically deleted after 30 days.
IP addresses are also used temporarily in memory to limit repeated requests and are not persistently stored for that purpose.
Cloudflare and Resend process connection, security, or delivery information under their applicable policies. We do not collect or export Cloudflare’s request logs into our own systems.
Support communications
When you contact support, we receive your message, contact information, and our correspondence with you. Messages submitted through the support form also include your IP address and approximate country, which we use to help identify and address abuse.
Please do not send passwords, complete license keys, payment-card details, sensitive personal information, or unnecessary copies of articles or brand profiles. We ordinarily investigate technical issues using operation identifiers, error codes, timestamps, and counts.
4. Information processed temporarily
Depending on the operation, saidweekly may temporarily process your business profile, website content, research sources, topics, keywords, editorial instructions, calendar information, generated drafts, metadata, and image-search terms.
This material may contain personal information if you include it in your website, business profile, instructions, or other inputs.
You are responsible for having the necessary rights and permissions to provide information about other people. Avoid providing sensitive personal information or confidential material that is unnecessary for the requested operation.
5. How we use information
We use information to:
- Establish and administer accounts and enroll websites.
- Authenticate installations and communicate securely with them.
- Provide research, calendar planning, article generation, and delivery.
- Process purchases and administer subscriptions, credits, quotas, cancellations, and refunds.
- Send licenses and service, billing, and account notices.
- Send occasional marketing email about saidweekly, only to people who ticked the box asking for it when starting the free plan or checking out, and only until they tell us to stop.
- Respond to support and privacy requests.
- Diagnose failures and maintain service reliability.
- Detect and investigate misuse, fraud, unauthorized access, and security incidents.
- Maintain financial and administrative records.
- Comply with legal obligations and establish, exercise, or defend legal claims.
We do not maintain customer content as a training dataset for our own models.
We do not sell personal information. We will not share your personal information for cross-context behavioral advertising or use it for targeted advertising without your prior, affirmative consent. Any request for consent will explain what information would be shared, with whom, and for what purpose. You may withdraw your consent at any time through our support form.
6. Providers and disclosures
We disclose information to providers as needed to perform their functions.
| Provider | Function |
|---|---|
| Google Cloud | Hosts our cloud services, temporarily processes generation material, and stores limited account, billing-reference, usage, and operational records. Our configured database storage is in the United States. |
| Anthropic | Processes material needed for AI-assisted research, calendar planning, and article generation. Its published standard API policy generally provides for deletion of inputs and outputs within 30 days, subject to exceptions, including safety and legal requirements. saidweekly does not currently have a zero-data-retention agreement with Anthropic. |
| Pexels | Receives image-search terms and related requests used to select featured images. |
| Stripe | Processes payments and supports billing, tax, and subscription administration. |
| Resend | Delivers transactional emails, including license and account messages, and processes recipient addresses, message contents, and delivery information. |
| Google Workspace | Hosts our support mailbox and correspondence. |
| Cloudflare | Delivers and protects our website and processes relevant connection and security information. |
Providers process information under their applicable agreements and policies. Their retention periods may differ from ours, and they may have independent legal obligations.
We may also disclose information:
- At your direction.
- To legal, accounting, and other professional advisers who need it and are subject to appropriate confidentiality obligations.
- When required by applicable law or valid legal process.
- When reasonably necessary to protect rights, safety, or security or investigate suspected unlawful activity.
- In connection with a merger, acquisition, financing, reorganization, or sale of the business, subject to applicable law and appropriate confidentiality protections.
7. Cookies, analytics, and browser storage
The public saidweekly website does not use advertising trackers or audience analytics. It sets no cookies of its own and does not store information in your browser’s local or session storage.
Cloudflare’s security features may set necessary cookies to distinguish legitimate visitors from automated traffic. These are not used by saidweekly for advertising.
Checkout and subscription-management pages hosted by Stripe use cookies and similar technologies under Stripe’s policies.
8. Retention
We retain information according to its purpose and the following schedule.
| Category | Retention period |
|---|---|
| Customer content processed by the generation service | Only during processing; no persistent saidweekly copy. Provider retention is described separately in Section 6. |
| Account profile and website-enrollment records | While the account remains open and for 12 months after closure, except for limited information retained with financial or audit records. |
| Installation credentials | While needed for an authorized installation. Credentials are revoked and removed promptly when the installation is retired or the account closes. |
| Retained payment, refund, and financial transaction records | Seven years after the end of the fiscal year in which the transaction occurred. |
| Credit, entitlement, and subscription history needed to explain transactions | While the account remains open and for seven years after closure. |
| Routine job and failure records | Up to 90 days after completion or final resolution, unless removed sooner under an applicable expiration policy. |
| Detailed token and cost measurements | Up to 12 months after recording. |
| Request and application logs | 30 days. |
| Separately retained security-event records | Up to 90 days, with relevant evidence retained longer for an actual incident or investigation. |
| Support correspondence, including associated IP address and country | 24 months after the issue closes. |
| Administrative account-action audit records | While the account remains open and for seven years after closure. |
| Privacy requests and our responses | Three years after resolution. |
| Routine database recovery backups | Up to 28 days under normal backup rotation. |
For this schedule, account closure means that the account has no active service or remaining entitlement and has been recorded as closed. Canceling automatic renewal alone does not close an account. The expiration of a credit does not necessarily delete the record documenting that credit.
We may retain particular records longer where required by law or subject to a documented preservation hold for a dispute, investigation, or legal claim. Such holds apply to relevant records rather than automatically extending retention for the entire account.
We may retain aggregate statistics longer if they have been de-identified so they cannot reasonably be used to identify an individual or customer account.
Recovery backups and separate records archives
Routine recovery backups rotate out under our normal backup schedule. Information deleted from active systems may remain in those backups until they expire. If a backup is restored, applicable deletion instructions are reapplied.
Records subject to a seven-year retention period may be moved to a separate, secure records archive maintained by Martin Miller Software Consulting LLC. That archive may remain for the applicable retention period even if saidweekly stops operating.
The archive is limited to records needed for the stated retention purposes. It does not contain customer articles, brand profiles, or other content processed temporarily by the generation service.
Archived records are deleted after their retention period and any applicable preservation hold end. Expired records are removed through scheduled deletion processes.
9. Your privacy requests and choices
You may contact us to ask what personal information we hold about you, request a correction, or request deletion.
Depending on your location and applicable law, you may also have rights to obtain a copy of your information, receive it in a portable format, restrict or object to processing, withdraw consent where processing relies on consent, or appeal a decision concerning a privacy request.
Submit requests through our support form or by mail to the address in Section 14. Please identify your message as a privacy request.
We may request information reasonably necessary to verify your identity or authority. We will respond within the period required by applicable law and explain any applicable exception or limitation. Where applicable law provides these rights, we will not unlawfully discriminate against you for exercising them.
Deleting information needed for account administration or authentication may prevent continued use of the service. Limited financial, audit, or other records may remain for the periods described in Section 8.
Canceling a subscription does not automatically delete account records. Deleting account records does not delete articles or other material stored in your WordPress installation.
License, billing, security, and other necessary service notices are account communications. Marketing email is sent only with your consent, given by a checkbox when you start the free plan or check out; you can withdraw it at any time through the support form or the unsubscribe link in any such email, and we record your answer with your account.
10. Information about visitors to customer websites
Customers control their WordPress websites and are responsible for their own privacy notices, information collection, and publication practices.
saidweekly is not intended to collect visitors’ form submissions, customer lists, or private account information as part of article generation. Public website content may be processed when relevant to research or generation.
If your request concerns information held by a customer’s website, contact that website’s operator. You may also contact us about saidweekly’s processing of that information.
11. Security
We use administrative and technical measures designed to protect information, including authentication controls, restricted access, secure communications, and limits on persistent storage of customer content.
Separate records archives are encrypted and access is restricted. We maintain recovery arrangements intended to keep retained records readable throughout their retention periods.
No system can guarantee absolute security. You are responsible for protecting your WordPress installation, administrator accounts, license credentials, and backups.
We will provide notices concerning security incidents where required by applicable law.
12. International processing and children
saidweekly is operated from the United States. Information may be processed in the United States and in other locations used by our providers.
Where applicable law requires safeguards for international transfers, those safeguards must be established through the applicable agreements and processing arrangements. Use of saidweekly does not itself replace a legally required transfer mechanism.
saidweekly is intended for business use and is not directed to children under 13. We do not knowingly collect personal information directly from children under 13. Contact us if you believe a child has provided personal information to us.
13. Changes to this policy
We may update this policy to reflect changes in the service, our practices, or applicable law. We will post the updated policy and revise its effective date.
Where applicable law requires additional notice or consent for a material change, we will provide that notice or obtain that consent as required.
14. Contact us
For privacy questions or requests, use the saidweekly support form, or write to:
Martin Miller Software Consulting LLC
Doing business as saidweekly
Attn: Privacy
8428 Wiese Rd
Brecksville, OH 44141
United States