About
AI Ethics & Safety Policy
Rubber City AI helps organizations use AI responsibly, practically, and with human judgment still visible.
AI tools can be useful, but they can also be wrong, biased, incomplete, or inappropriate for sensitive decisions. Our work emphasizes guardrails, human review, approved-use boundaries, and clear expectations before AI is scaled across an organization.
Method
How the work moves forward
Rubber City AI: Built on Trust, Not Just Tech
At Rubber City AI, we do not treat “responsible by default” as a tagline. It is the foundation of how we work — guiding our advice to clients, shaping how we build tools, and anchoring every decision we make about future models. We are grounded in the practical mindset that comes with being built for Akron-area organizations. That means focusing less on flashy promises and more on doing the right thing — every time. We take the best lessons from responsible AI practice and shape them into six working principles that guide our team: #### Follow the Law Every AI solution we deliver respects data privacy, security, and the laws that govern them — from HIPAA and GDPR to emerging AI regulations such as the EU AI Act. Compliance is not optional. #### Build It Safe Before anything goes live, we test models, prompts, and workflows for weak spots — hallucinations, jailbreaks, edge-case breakdowns, and unsafe outputs. If the stakes are high, we add extra layers of protection. #### Keep It Fair We check available data, workflows, and outputs for bias or unfair treatment. If something seems off, we correct it. The goal is to make AI that supports people — not marginalizes them. #### Be Clear With Clients No black boxes. Every project includes plain-English documentation that explains how the system works, what the risks are, what its limits are, and where humans remain in control. #### People Make the Final Call There is always a named decision-maker on the client side — someone who can pause, review, override, or reject AI-supported outputs. Machines never have the last word. #### Own the Responsibility We document who did what, what decisions were made, and what happens if something goes wrong. Edward Jacak, Founder of Rubber City AI, acts as AI Ethics Officer and leads our response when issues arise. We think of AI as a practical capacity tool — helping small teams reclaim time, improve decisions, serve customers better, and reduce repetitive work. But none of that matters if it is not safe. Ethics is not a checkbox here. It is the promise that we are building tools people can trust.
Rubber City AI — AI Ethics and Safety Policy
Rubber City AI — AI Ethics and Safety Policy
Effective Date: 12 May 2026
Rubber City AI is a service brand of Sixth City Technologies, LLC. This AI Ethics and Safety Policy applies to AI-related advisory, training, implementation, automation, and support work delivered through Rubber City AI.
1. Purpose
This policy sets out how Sixth City Technologies, LLC, operating through Rubber City AI, designs, advises on, builds, deploys, and maintains artificial-intelligence solutions in a manner that is technically sound, legally compliant, and respectful of the people who use — or are affected by — our work.
2. Scope
This policy applies to all AI-related activity conducted by Rubber City AI, including:
\- Advisory, training, and implementation projects delivered to clients.
\- Internal automations, research prototypes, and proofs of concept.
\- AI workflow mapping, data-readiness support, prompt systems, agent workflows, and business process automation.
\- Any future first-party or co-developed models, agents, tools, or AI-supported systems.
3. Guiding Principles
Our approach is inspired by the public commitments of leading AI providers, but tailored to the needs of small and mid-sized organizations that need clear, practical, and responsible guidance.
|Principle|What It Means in Practice|
\|---|---|
|Lawfulness|Every solution is designed to comply with applicable privacy, security, and sector-specific regulations, including GDPR, HIPAA, CCPA/CPRA, and relevant EU AI Act requirements where applicable.|
|Robustness and Safety|Models, prompts, workflows, and automation patterns are reviewed and tested before launch. High-risk use cases trigger additional safeguards.|
|Fairness and Non-Discrimination|We check accessible data, workflows, and outputs for harmful bias and apply mitigation strategies or guardrails when needed.|
|Transparency to Clients|For each engagement, we provide plain-language documentation explaining system purpose, data sources, limitations, risks, and oversight duties.|
|Human Oversight|A named client contact retains authority to review, accept, reject, pause, or override AI-supported decisions. Fully autonomous operation is delivered only with explicit sign-off.|
|Accountability|Roles, escalation paths, and audit trails are documented so issues can be traced, understood, and corrected quickly.|
4. Governance Structure
AI Ethics Officer — Edward Jacak, Founder of Sixth City Technologies, LLC, is the single point of responsibility for interpreting this policy, granting risk exceptions, and resolving ethics inquiries.
Delivery Leads — Every client project is assigned a responsible lead who owns day-to-day compliance with this policy and reports issues to the AI Ethics Officer.
Domain Reviewers — Technical, operational, and subject-matter reviewers may be used when a project involves sensitive data, regulated workflows, high-impact decisions, or specialized business processes.
5. Development and Review Lifecycle
Rubber City AI uses a practical lifecycle for responsible AI work:
1\. Concept Brief
Document the intended purpose, user groups, success metrics, data needs, and potential risks.
2\. Risk Triage
Classify the project as Low, Medium, or High risk based on data sensitivity, autonomy level, business impact, and potential harm.
3\. Design Controls
Choose models, data pipelines, prompts, access rules, human review steps, and guardrails appropriate to the risk class.
4\. Internal Testing
Stress-test prompts, workflows, and automation behavior for hallucinations, misuse, jailbreaks, unsafe outputs, and edge-case failures.
5\. Client Documentation and Sign-Off
Provide a plain-language system brief covering purpose, limitations, monitoring obligations, fallback mechanisms, and required human oversight.
6\. Deployment and Monitoring
Where appropriate, enable logging, access controls, rate-limiting, performance monitoring, and anomaly review.
7\. Post-Launch Review
Collect feedback, measure performance, review risks, and schedule updates as part of ongoing support when applicable.
6. Compliance Alignment
Rubber City AI does not currently claim formal AI governance certification. However, our controls are designed to align with the spirit and major provisions of:
\- GDPR and UK GDPR for data privacy.
\- CCPA/CPRA for California privacy requirements where applicable.
\- HIPAA when handling Protected Health Information.
\- SOC 2 principles for security, availability, confidentiality, and operational control.
\- EU AI Act concepts related to risk classification, transparency, documentation, and human oversight.
7. Transparency and NDA-Bound Disclosures
Because much of our work is bespoke and commercially sensitive, Rubber City AI does not generally publish public model cards for client-specific systems.
Instead, where appropriate, clients receive:
\- A System Fact Sheet covering purpose, inputs, outputs, known limits, and human-in-the-loop checkpoints.
\- A Compliance Appendix mapping relevant legal or operational requirements to the controls in place.
\- Engagement-specific documentation covering risks, responsibilities, and escalation paths.
These documents may be provided under NDA or other confidentiality terms and may be updated during the engagement.
8. Incident Response
Rubber City AI uses the following incident response process for material AI safety, reliability, or compliance concerns:
1\. Detection
Abnormal outputs, usage deviations, complaints, workflow failures, or other risk signals are reviewed.
2\. Initial Containment
The Delivery Lead may pause, disable, rate-limit, or isolate the affected component if user safety, business continuity, or legal exposure is suspected.
3\. Notification
Material incidents are reported to the client project owner and the AI Ethics Officer within 24 hours of confirmation.
4\. Root-Cause Analysis
A structured review determines whether the issue involved model behavior, prompt design, data quality, workflow logic, user misuse, access control, or system integration.
5\. Remediation and Documentation
Fixes are implemented, tested, and logged. Incident records are retained for seven years where appropriate.
9. Training and Awareness
Rubber City AI team members and project participants involved in AI work are expected to understand:
\- Responsible AI principles.
\- Bias, fairness, and human oversight concerns.
\- Data privacy and security obligations.
\- Safe prompt, workflow, and automation design.
\- Escalation paths for ethics, safety, or compliance concerns.
10. Policy Maintenance
The AI Ethics Officer reviews this document at least once per year, or sooner if relevant legal, technical, or operational requirements change.
Material changes affecting active client work may trigger client notification within 15 days.
11. Questions and Reporting
To raise a concern, ask a question, or report a potential AI ethics or safety issue, contact:
Edward Jacak
AI Ethics Officer
Rubber City AI and Sixth City Technologies, LLC
8954 Albion Road
North Royalton, OH 44133, USA
ethics\@rubbercityai.com
+1 (234) 349-5150
Start with a practical next step
Start a ConversationAnswer Engine Summary
How does Rubber City AI approach responsible AI?
Rubber City AI treats responsible AI as practical guardrails, not slogans: human review of sensitive decisions, approved-use boundaries, attention to data handling, and honesty about what AI should and should not do. We do not make legal, compliance, or guaranteed-outcome promises.